Rename package to scoped @sahinur/forgedata; bump CI action/toolchain versions

npm's anti-typosquatting policy blocks the unscoped "forgedata" name as too
similar to "form-data", so the package now publishes as @sahinur/forgedata.
The forgedata CLI command name is unaffected by the scope change.

Also: fix the bin path / typesVersions formatting flagged by `npm pkg fix`,
bump @typescript-eslint to v8 (clears a TS 5.9 support warning), and bump
actions/checkout, actions/setup-node, and actions/upload-artifact to their
current majors to clear GitHub's Node 20 runtime deprecation warning.

Author: SahinurDEV

.github/workflows/ci.yml

@@ -12,12 +12,12 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        node-version: [18.x, 20.x, 22.x]
+        node-version: [18.x, 20.x, 22.x, 24.x]
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v7
 
       - name: Setup Node ${{ matrix.node-version }}
-        uses: actions/setup-node@v4
+        uses: actions/setup-node@v6
         with:
           node-version: ${{ matrix.node-version }}
           cache: "npm"
@@ -38,8 +38,8 @@ jobs:
         run: npm run build
 
       - name: Upload coverage
-        if: matrix.node-version == '20.x'
-        uses: actions/upload-artifact@v4
+        if: matrix.node-version == '22.x'
+        uses: actions/upload-artifact@v7
         with:
           name: coverage
           path: coverage

.github/workflows/release.yml

@@ -23,14 +23,14 @@ jobs:
       pull-requests: write
       id-token: write
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v7
         with:
           fetch-depth: 0
 
       - name: Setup Node
-        uses: actions/setup-node@v4
+        uses: actions/setup-node@v6
         with:
-          node-version: 20.x
+          node-version: 22.x
           cache: "npm"
           registry-url: "https://registry.npmjs.org"
 

CHANGELOG.md

@@ -13,7 +13,10 @@ this line by CI; do not hand-edit past releases.
 
 ## [0.1.0] - Unreleased
 
-Initial release.
+Initial release. Published as the scoped package `@sahinur/forgedata` — the
+unscoped `forgedata` name is blocked by npm's anti-typosquatting policy
+(flagged as too similar to the popular `form-data` package). The CLI command
+itself is still the short `forgedata` regardless of package scope.
 
 ### Added
 
@@ -30,14 +33,14 @@ Initial release.
   `weighted`, `probability`, `randomArray`, `randomObjectKey/Value`.
 - Generator introspection: `forge.listGenerators()` / `forge.invoke()`, built
   by walking the real module classes rather than a hand-maintained registry.
-- React integration at the `forgedata/react` subpath: `ForgeDataProvider`,
+- React integration at the `@sahinur/forgedata/react` subpath: `ForgeDataProvider`,
   `useForgeData()`, `useGenerator()`. `react` is an optional peer dependency.
 - CLI (`forgedata` bin): `list` and `generate` commands with
   `--seed`/`--locale`/`--count`/`--json` flags.
 - ESM + CommonJS builds with full TypeScript declarations for the main entry,
-  `forgedata/react`, and the CLI.
+  `@sahinur/forgedata/react`, and the CLI.
 - 100% statement/branch/function/line test coverage (enforced in CI).
 - Zero runtime dependencies; only web-standard APIs (`btoa`, etc.) so the
   package runs unmodified on Node.js 18+, Bun, Deno, and in browsers.
 
-[0.1.0]: https://github.com/forgedata/forgedata/releases/tag/v0.1.0
+[0.1.0]: https://github.com/devSahinur/ForgeData/releases/tag/v0.1.0

README.md

@@ -11,20 +11,20 @@ A modern, modular, tree-shakable, zero-runtime-dependency fake data generator fo
 - **Seedable** — deterministic output for tests and snapshots
 - **9 built-in locales**, plus a custom locale API
 - **Custom generators** via `forge.define(...)`
-- **React integration** (`forgedata/react`): a provider + two hooks
+- **React integration** (`@sahinur/forgedata/react`): a provider + two hooks
 - **CLI** (`forgedata`): generate fake data from your terminal or scripts
 - **100% test coverage** (statements/branches/functions/lines)
 
 ## Install
 
 ```bash
-npm install forgedata
+npm install @sahinur/forgedata
 ```
 
 ## Quick start
 
 ```ts
-import { ForgeData } from "forgedata";
+import { ForgeData } from "@sahinur/forgedata";
 
 const forge = new ForgeData();
 
@@ -39,7 +39,7 @@ forge.ai.prompt();                // "Explain quantum computing to a beginner...
 Or use the ready-made default instance for quick scripts:
 
 ```ts
-import { forge } from "forgedata";
+import { forge } from "@sahinur/forgedata";
 
 console.log(forge.person.fullName());
 ```
@@ -141,7 +141,7 @@ This is what the CLI is built on.
 ## React integration
 
 ```tsx
-import { ForgeDataProvider, useForgeData, useGenerator } from "forgedata/react";
+import { ForgeDataProvider, useForgeData, useGenerator } from "@sahinur/forgedata/react";
 
 function App() {
   return (
@@ -161,19 +161,19 @@ function UserCard() {
 }
 ```
 
-`useForgeData()` works even without a `ForgeDataProvider` (it falls back to a shared default instance) — wrap your tree in a provider whenever you need a specific seed/locale or per-instance isolation. `react` is an optional peer dependency; the main `forgedata` entry point never imports it.
+`useForgeData()` works even without a `ForgeDataProvider` (it falls back to a shared default instance) — wrap your tree in a provider whenever you need a specific seed/locale or per-instance isolation. `react` is an optional peer dependency; the main `@sahinur/forgedata` entry point never imports it.
 
 ## CLI
 
 ```bash
-npx forgedata list                                  # every generator id
-npx forgedata list --module person                  # filtered to one module
-npx forgedata generate person.fullName               # one value
-npx forgedata generate internet.email --count 5 --seed 42
-npx forgedata generate location.country --locale ja --json
+npx --package=@sahinur/forgedata forgedata list                     # every generator id
+npx --package=@sahinur/forgedata forgedata list --module person     # filtered to one module
+npx --package=@sahinur/forgedata forgedata generate person.fullName # one value
+npx --package=@sahinur/forgedata forgedata generate internet.email --count 5 --seed 42
+npx --package=@sahinur/forgedata forgedata generate location.country --locale ja --json
 ```
 
-Install it globally or use `npx`; see [docs/cli.md](./docs/cli.md) for the full flag reference.
+Install it globally (`npm install -g @sahinur/forgedata`) to just run `forgedata ...` directly; see [docs/cli.md](./docs/cli.md) for the full flag reference.
 
 ## Modules
 
@@ -204,8 +204,8 @@ ForgeData avoids Node-only APIs in `src/` — it uses only `btoa`, `Math`/`Date`
 
 - **Node.js**: `import`/`require` both work out of the box.
 - **Bun**: works via the same ESM/CJS builds.
-- **Deno**: `import { ForgeData } from "npm:forgedata";`
-- **Browsers**: `import { ForgeData } from "forgedata";` through any bundler, or `examples/browser.html` for a zero-bundler example.
+- **Deno**: `import { ForgeData } from "npm:@sahinur/forgedata";`
+- **Browsers**: `import { ForgeData } from "@sahinur/forgedata";` through any bundler, or `examples/browser.html` for a zero-bundler example.
 
 ## Development
 

RELEASE_NOTES.md

@@ -26,7 +26,7 @@ alternative to Faker.js with React integration and a CLI built in.
   plus a custom locale API.
 - **Custom generators** (`forge.define()`) and a **unique-value generator**
   (`forge.unique.email()`, etc.).
-- **React integration** at `forgedata/react`: `ForgeDataProvider`,
+- **React integration** at `@sahinur/forgedata/react`: `ForgeDataProvider`,
   `useForgeData()`, `useGenerator()`. `react` is an optional peer dependency —
   the main entry point never imports it.
 - **CLI** (`forgedata`): `forgedata generate person.fullName --seed 42`,
@@ -36,13 +36,17 @@ alternative to Faker.js with React integration and a CLI built in.
 ## Install
 
 ```bash
-npm install forgedata
+npm install @sahinur/forgedata
 ```
 
+Published under the `@sahinur` scope because npm's anti-typosquatting policy
+blocks the unscoped `forgedata` name (too similar to the popular `form-data`
+package). The CLI command is still just `forgedata`.
+
 ## Quick start
 
 ```ts
-import { ForgeData } from "forgedata";
+import { ForgeData } from "@sahinur/forgedata";
 
 const forge = new ForgeData({ seed: 42 });
 forge.person.fullName();
@@ -54,6 +58,6 @@ reference, React guide, CLI reference, and migration notes from Faker.js.
 
 ## Links
 
-- npm: https://www.npmjs.com/package/forgedata
+- npm: https://www.npmjs.com/package/@sahinur/forgedata
 - Docs: [docs/getting-started.md](./docs/getting-started.md)
 - Changelog: [CHANGELOG.md](./CHANGELOG.md)

docs/api-reference.md

@@ -60,7 +60,7 @@ Every module below is a plain class instantiated once per `ForgeData`. Full meth
 
 Built-in codes: `en`, `bn`, `hi`, `ar`, `ja`, `fr`, `de`, `es`, `zh`. Register additional ones with `forge.defineLocale(data)`.
 
-## React (`forgedata/react`)
+## React (`@sahinur/forgedata/react`)
 
 See [react.md](./react.md).
 

docs/cli.md

@@ -1,9 +1,11 @@
 # CLI Reference
 
 ```bash
-npx forgedata --help
+npx --package=@sahinur/forgedata forgedata --help
 ```
 
+(The package is published as `@sahinur/forgedata`, but its bin command is the shorter `forgedata` — `npx` needs `--package` whenever the command name doesn't match the package name. Once installed — globally or as a project dependency — just run `forgedata ...` directly, as in every example below.)
+
 ```
 forgedata v0.1.0 — fake data from the command line
 
@@ -51,14 +53,14 @@ Non-string results (objects, e.g. `location.airport`) are printed as JSON even w
 ## Installing globally
 
 ```bash
-npm install -g forgedata
+npm install -g @sahinur/forgedata
 forgedata list
 ```
 
 Or invoke it without installing:
 
 ```bash
-npx forgedata generate person.fullName
+npx --package=@sahinur/forgedata forgedata generate person.fullName
 ```
 
 ## Scripting example

docs/contributing.md

@@ -40,7 +40,7 @@ Core argument parsing/dispatch logic lives in `src/cli-core.ts` (fully unit test
 
 ## Working on the React integration
 
-`src/react/index.tsx` is a separate tsup entry (`forgedata/react`) with `react` as an external peer dependency — never import it from `src/index.ts`. Test with `@testing-library/react` + jsdom (`// @vitest-environment jsdom` at the top of the test file).
+`src/react/index.tsx` is a separate tsup entry (`@sahinur/forgedata/react`) with `react` as an external peer dependency — never import it from `src/index.ts`. Test with `@testing-library/react` + jsdom (`// @vitest-environment jsdom` at the top of the test file).
 
 ## Code style
 

docs/getting-started.md

@@ -3,13 +3,13 @@
 ## Install
 
 ```bash
-npm install forgedata
+npm install @sahinur/forgedata
 ```
 
 ## Your first generator
 
 ```ts
-import { ForgeData } from "forgedata";
+import { ForgeData } from "@sahinur/forgedata";
 
 const forge = new ForgeData();
 
@@ -22,7 +22,7 @@ console.log(forge.internet.email());
 ## Seeding for deterministic tests
 
 ```ts
-import { ForgeData } from "forgedata";
+import { ForgeData } from "@sahinur/forgedata";
 
 const forge = new ForgeData({ seed: "my-test-suite" });
 

docs/migration-guide.md

@@ -23,12 +23,12 @@ ForgeData follows a similar module-and-method shape to `@faker-js/faker`, but wi
 
 ## Key differences
 
-1. **Instance-based, not a global singleton.** `new ForgeData()` gives you an isolated random stream. ForgeData also exports a ready-made singleton (`import { forge } from "forgedata"`), but construct your own per test file/suite when you need isolation.
+1. **Instance-based, not a global singleton.** `new ForgeData()` gives you an isolated random stream. ForgeData also exports a ready-made singleton (`import { forge } from "@sahinur/forgedata"`), but construct your own per test file/suite when you need isolation.
 2. **Seeding is constructor-first.** Prefer `new ForgeData({ seed })` over calling `.seed()` after the fact, though both work.
 3. **Locale data shape is simpler.** ForgeData locales cover names, places, lorem words, and company phrasing — not every Faker.js locale category. Extend via `forge.defineLocale(...)`.
 4. **No module-specific singletons** like `faker.fakerEN`, `faker.fakerDE`, etc. — pass `locale` to the constructor or call `forge.locale(code)`.
 5. **Unique generator is per-instance and explicit** (`forge.unique.email()`), not a global unique-tracking layer.
-6. **Built-in React integration and CLI** — Faker.js has neither out of the box; ForgeData ships `forgedata/react` and the `forgedata` CLI.
+6. **Built-in React integration and CLI** — Faker.js has neither out of the box; ForgeData ships `@sahinur/forgedata/react` and the `forgedata` CLI.
 7. **Generator discovery is programmatic.** `forge.listGenerators()` walks the real classes instead of requiring a hand-maintained catalogue — useful for building your own tooling (it's what the CLI is built on).
 
 ## Things ForgeData intentionally does not replicate