nhb-toolbox 4.30.20 → 4.30.22

package/CHANGELOG.md

@@ -4,9 +4,10 @@
 
 All notable changes to the package will be documented here.
 
-## [4.30.20] - 2026-05-26
+## [4.30.20-22] - 2026-05-26
 
-- **Fixed** token audience(s) validation issue in `Signet` class.
+- **Fixed** token audience(s) validation issue in `Signet` class, previously it was returning `false` even for valid tokens.
+- **Removed** *github packages* support, only *npm registry* will be used for distribution.
 
 ## [4.30.16] - 2026-05-24
 

package/README.md

@@ -45,6 +45,15 @@
   </a>
 </p>
 
+>[!Info] Notice
+>`nhb-toolbox` is now split into 3 packages for better maintenance, organization and user experience.
+>It will not receive any new features, only critical bug fixes will be provided in the future updates.
+>
+>The new packages are:
+> <a target="_blank" href="https://toolbox-x.nazmul-nhb.dev"> <img src="https://img.shields.io/badge/Toolbox--X-toolbox--x-steelblue" alt="toolbox-x" /> </a>
+> <a target="_blank" href="https://chronos.nazmul-nhb.dev"> <img src="https://img.shields.io/badge/Chronos--Date-chronos--date-teal" alt="chronos-date" /> </a>
+> <a target="_blank" href="https://github.com/nazmul-nhb/bn-calendar"> <img src="https://img.shields.io/badge/Bangla_Calendar-bn--calendar-red" alt="bn-calendar" /> </a>
+
 ## JavaScript/TypeScript Utility Library
 
 **NHB Toolbox** provides battle-tested utilities for professional JavaScript/TypeScript development. Carefully crafted to solve common challenges with elegant, production-ready solutions:
@@ -60,17 +69,6 @@
 
 ## Installation
 
-`nhb-toolbox` is published to two package registries:
-
-- **NPM Registry** (default public registry)
-- **GitHub Packages** (GitHub’s package registry, scoped package)
-
----
-
-### Installing from NPM Registry (default)
-
-This is the simplest way to install and requires no additional setup.
-
 Choose your preferred package manager:
 
 ```shell
@@ -85,109 +83,6 @@ pnpm add nhb-toolbox
 yarn add nhb-toolbox
 ```
 
-> Use this if you want the stable public version without extra config.
-
----
-
-### Installing from GitHub Packages
-  
-GitHub Packages requires authentication and scoped package names.
-
-<details>
-
-  <summary>
-    <strong>Details</strong>
-  </summary>
-
-#### Step 1: Authenticate with GitHub Packages
-
-Create or use a **GitHub Personal Access Token (PAT)** with `read:packages` permission.
-
-Add the following to your project’s `.npmrc` file (create if it doesn’t exist):
-
-```ini
-@nazmul-nhb:registry=https://npm.pkg.github.com
-//npm.pkg.github.com/:_authToken=YOUR_GITHUB_PERSONAL_ACCESS_TOKEN
-```
-
-> Replace `YOUR_GITHUB_PERSONAL_ACCESS_TOKEN` with your actual token.
-
-#### Step 2: Install the package with scoped name
-
-Choose your preferred package manager:
-
-```shell
-npm i @nazmul-nhb/nhb-toolbox
-```
-
-```shell
-pnpm add @nazmul-nhb/nhb-toolbox
-```
-
-```shell
-yarn add @nazmul-nhb/nhb-toolbox
-```
-
----
-
-#### Where do consumers get the GitHub token?
-
-- **The token is personal and private** — *each consumer must create own*.
-
-- Your **GitHub Personal Access Token (PAT)** **should never be shared publicly or with consumers**.
-
----
-
-#### How consumers create own token
-
-1. **Go to GitHub account settings** → **Developer settings** → **Personal access tokens** → **Tokens (classic)**.
-
-2. Click **Generate new token**, then:
-
-   - Give it a name (e.g., `npm package read access`).
-
-   - Set expiration as prefer.
-
-   - **Enable only the `read:packages` permission** (to allow reading packages).
-
-3. Generate the token and **copy it immediately** — won't see it again.
-
----
-
-#### What should consumers do with the token?
-
-- Add it to `.npmrc` file (or environment) to authenticate with GitHub Packages.
-
-Example `.npmrc` snippet:
-
-```ini
-@nazmul-nhb:registry=https://npm.pkg.github.com
-//npm.pkg.github.com/:_authToken=PERSONAL_ACCESS_TOKEN_HERE
-```
-
-</details>
-
----
-
-### Summary
-
-| Registry        | Package Name              | Registry URL                                             | Requires Auth?                 |
-| --------------- | ------------------------- | -------------------------------------------------------- | ------------------------------ |
-| NPM Registry    | `nhb-toolbox`             | [https://registry.npmjs.org](https://registry.npmjs.org) | No                             |
-| GitHub Packages | `@nazmul-nhb/nhb-toolbox` | [https://npm.pkg.github.com](https://npm.pkg.github.com) | Yes (PAT with `read:packages`) |
-
----
-
-If you want to use both, just configure `.npmrc` accordingly and install the appropriate package name depending on your needs.
-
----
-
-### Notes
-
-- The GitHub Packages version may include pre-release or private builds.
-- NPM Registry version is the recommended default for most users.
-- You can safely use either registry depending on your environment.
-
 ---
 
 ## Changelog
@@ -523,6 +418,12 @@ debounceAction(fetchResults, 300);
   </a>
 </div>
 
+<div style={{ display: 'flex', alignItems: 'center', gap: '0.5rem' }}>
+  <a target="_blank" href="https://www.npmjs.com/package/chronos-date">
+    <img src="https://img.shields.io/badge/Chronos--Date-chronos--date-teal" alt="chronos-date" />
+  </a>
+</div>
+
 <div style={{ display: 'flex', alignItems: 'center', gap: '0.5rem' }}>
   <a target="_blank" href="https://www.npmjs.com/package/bn-calendar">
     <img src="https://img.shields.io/badge/Bangla_Calendar-bn--calendar-red" alt="bn-calendar" />

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "nhb-toolbox",
-  "version": "4.30.20",
+  "version": "4.30.22",
   "description": "A versatile collection of smart, efficient, and reusable utility functions, classes and types for everyday development needs.",
   "main": "dist/cjs/index.js",
   "module": "dist/esm/index.js",