Merge pull request #22 from NexGenStudioDev/dev

Dev

Author: abhishek-nexgen-dev

.github/workflows/publish.yml

@@ -5,7 +5,7 @@ on:
     branches:
       - master
     tags:
-      - 'v*' # optional: publish on version tags like v1.0.0
+      - 'v*'
 
 jobs:
   publish:
@@ -16,7 +16,7 @@ jobs:
       - name: Checkout code
         uses: actions/checkout@v4
 
-      - name: Setup Node.js 18
+      - name: Setup Node.js
         uses: actions/setup-node@v4
         with:
           node-version: 18
@@ -33,13 +33,15 @@ jobs:
       - name: Build package
         run: pnpm build
 
-      # - name: Run tests (optional)
-      #   run: pnpm test
-
       - name: Authenticate to npm
-        run: npm config set //registry.npmjs.org/:_authToken=${NPM_TOKEN}
         env:
+          # Required so setup-node writes correct .npmrc
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
           NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
+        run: |
+          echo "//registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}" >> ~/.npmrc
 
       - name: Publish to npm
-        run: pnpm publish --access public --no-git-checks
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+        run: pnpm publish --access public --no-git-checks

PACKAGE_MANAGERS.md

@@ -79,9 +79,45 @@ npm run version:major
 
 5. Publish package:
 
-```bash
-npm run publish:npm
-```
+# 📦 Publishing and Installing npm Packages with Custom Tags
+
+When you publish a package to npm, each version **must have a version number higher than all previously published versions**. This helps npm identify the newest version.
+
+If you try to publish a version that is **lower or the same** as a previously published version using the default `latest` tag, npm will throw an error.
+
+---
+
+## Using Custom Tags to Avoid Errors
+
+To avoid this error, you can publish your package using a **different tag** instead of `latest`. Tags let you label versions differently, such as `beta`, `next`, or `dev`.
+
+---
+
+## Example: Publishing a Beta Version
+
+If you're working on a new feature or a major update and want users to test it **without affecting the stable release**, you can publish it under a `beta` tag.
+
+### Steps:
+
+1. **Update the Version**  
+   Increment your package’s version number to indicate it’s a beta release.  
+   For example, if your current version is `1.0.0`, you might update it to `1.1.0-beta.0`.
+
+2. **Publish with a Custom Tag**  
+   Run the following command to publish your package under the `beta` tag:
+
+   ```bash
+   npm publish --tag beta
+   ```
+
+   Or if you use an npm script like publish:npm:
+
+   ```bash
+   npm run publish:npm -- --tag beta
+   ```
+   
+   This way, your beta version is available for testing, but users installing your package normally will still get the stable latest version.
+
 
 ### Using pnpm
 1. Make your changes
@@ -100,9 +136,9 @@ npm run publish:npm
 4. Bump version (choose one):
 
 ````bash
-npm run version:patch
-npm run version:minor
-npm run version:major
+npm run version:patch  # Small bugfixes, no new features
+npm run version:minor  # New features, no breaking changes
+npm run version:major  # 	Breaking changes, major updates
 ````
 
 5. Publish:

package.json

@@ -1,7 +1,7 @@
 {
   "name": "@nexgenstudiodev/fastkit",
   "type": "commonjs",
-  "version": "1.0.0",
+  "version": "1.0.2",
   "description": "A modular, class-based toolkit for fast API development with TypeScript and Express.",
   "main": "dist/FastKit.js",
   "types": "dist/FastKit.d.ts",