@omniumretail/component-library 1.0.72 → 1.0.73

package/NPMPUBLISH.md

@@ -0,0 +1,29 @@
+## How to Publish a Package on npm
+
+Follow these steps to publish your package on npm:
+
+1. **Set up your package**
+
+   Navigate to your project directory in the terminal. If you don't have a `package.json` file, create one by running `npm init` and fill out the prompts. If you want to skip the prompts and use the default configuration, run `npm init -y`.
+
+2. **Create your package**
+
+   Write your package code and make sure it works as expected. Update the `main` entry in your `package.json` file to point to your package entry point (like `index.js`).
+
+3. **Login to npm**
+
+   If you're not logged into npm, login via the terminal using `npm login`. If you don't have an account, sign up on the npm website. You'll be prompted to enter your username, password, and email.
+
+4. **Version your package**
+
+   Decide your package version. npm uses semantic versioning, or `semver`. If you're publishing for the first time, it's likely already at version `1.0.0` or whatever you set during `npm init`. If you're updating, update the version number in `package.json` or use `npm version <update_type>`, replacing `<update_type>` with `patch`, `minor`, or `major` as appropriate.
+
+5. **Publish your package**
+
+   Publish your package using `npm publish`. Your package will then be publicly available on npm.
+
+6. **Verify your package**
+
+   Check that your package is available by going to `https://www.npmjs.com/package/<your-package-name>`, replacing `<your-package-name>` with the name of your package.
+
+Remember, to publish updates, update the version number in your `package.json` file or use the `npm version` command, then run `npm publish` again.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@omniumretail/component-library",
-  "version": "1.0.72",
+  "version": "1.0.73",
   "private": false,
   "main": "dist/bundle.js",
   "typings": "./dist/types/index",