Welcome to Aariya Tech Native Chatbot

This is a IP of aariyatech. All rights reserved

Get started

1. Install dependencies

   npm install

2. Start the app

    npm start

Understanding Semantic Versioning (SemVer) in npm

Semantic Versioning (SemVer) is a versioning system used in npm that employs a three-part version number:

MAJOR.MINOR.PATCH

• MAJOR version: Incremented for incompatible API changes
• MINOR version: Incremented for adding functionality in a backwards-compatible manner
• PATCH version: Incremented for backwards-compatible bug fixes

For example, in the version number 1.4.1:

• 1 is the MAJOR version
• 4 is the MINOR version
• 1 is the PATCH version

Version Constraints in npm

When you specify a dependency version like "at-chatbot-native": "^1.3.5", the ^ symbol tells npm that it can update to any compatible version. In SemVer, this means any version with the same major number and an equal or higher minor or patch number.

So ^1.3.5 allows updates to:

• 1.3.6, 1.3.7, etc. (patch updates)
• 1.4.0, 1.4.1, 1.5.0, etc. (minor updates)

But it would not allow updates to 2.0.0 or higher, as that's a major update which might include breaking changes.

Defining Version Constraints

| Constraint | Example | Meaning | | ------------- | ------------------- | -------------------------------------------------- | | Exact version | "1.3.5" | Only this exact version | | Patch updates | "~1.3.5" | Allows 1.3.6, 1.3.7, but not 1.4.0 | | Minor updates | "^1.3.5" | Allows 1.3.6, 1.4.0, 1.5.0, but not 2.0.0 | | Any version | "*" or "latest" | Always gets the latest version | | Greater than | ">1.3.5" | Any version higher than 1.3.5 | | Range | "1.3.5 - 1.5.0" | Any version between 1.3.5 and 1.5.0, inclusive |

Note: When "^1.3.5" is specified, npm considers it safe to update to 1.4.1 as it's a minor update and should be backwards compatible according to SemVer principles.

Publishing Instructions

• Check the BE url in config file
• Check the dev dependencies and peer dependencies in package.json
• Check the import for package json in the SplashScreen.tsx
• Run npm whoami to check your logged in user
• Run npm run build
• Push your changes git push origin <branch>
• Run npm version <patch|minor|major>
• Push your changes with tags now git push origin <branch> --tags
• Run npm publish
• If you made a mistake when publishing, then you can unpublish within 72 hrs, run npm unpublish <your-package@version>