metronics-vue 1.0.4 → 1.0.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -31,3 +31,27 @@ module.exports = {
31
31
  content: ["./index.html", "node_modules/metronics-vue/src/components/**/*.vue"],
32
32
  };
33
33
  ```
34
+
35
+ PUBLISHING METRONICS-VUE TO NPM
36
+
37
+ Follow these steps carefully to publish the Metronics-Vue package to npm:
38
+
39
+ ### Prerequisites
40
+
41
+ * Ensure you have an npm account and are logged in via your terminal.
42
+
43
+ ### Publishing Steps
44
+
45
+ 1. **Sync with `main` Branch:** Before you begin, make sure your local `main` branch is fully up-to-date with the remote repository. This prevents publishing outdated code.
46
+ 2. **Build the Project:** Execute the command `"npm run build-only"` in your terminal. This command compiles and prepares your project for publishing.
47
+ 3. **Increment Version Number:** Open your `package.json` file and update the `version` field. **It's crucial to increment this version number incrementally** (e.g., if the current version is "1.0.0", change it to "1.0.1" or "1.1.0"). Using a plus sign like "1.0.0+" is generally not recommended for versioning; use standard semantic versioning (e.g., `major.minor.patch`).
48
+ 4. **Authenticate with npm:** If you're not already logged in, run `"npm login"` in your terminal and follow the prompts to authenticate your npm account.
49
+ 5. **Publish to npm:** Finally, after completing all the preceding steps, publish your package by running the command `"npm publish"`.
50
+
51
+ ---
52
+
53
+ ### Important Notes:
54
+
55
+ * Always ensure your `main` branch is clean and up-to-date before publishing.
56
+ * Double-check the version number in `package.json` to avoid publishing with a duplicate or incorrect version.
57
+ * Semantic Versioning (SemVer) is highly recommended for managing your package versions.