fix(types): add typesVersions to support CommonJS imports in TypeScript

[jbrun-hulo]

Pull Request

What does this do?

Add typesVersions field to package.json to map type definitions, enabling proper CommonJS module resolution in TypeScript projects such as NestJS v10.

Without this, TypeScript fails to resolve types when importing n2words via require() or with moduleResolution set to Node.

Related Issue

Checklist

• Tests pass (npm test)
• Linting passes (npm run lint)

---

Adding a new language? (click to expand)

Recommended: Use the scaffolding tool to generate all files automatically:

npm run lang:add -- <code>

Manual setup: If not using the scaffolding tool, ensure you have:

• Language module in src/<code>.js exporting toCardinal(), toOrdinal(), and/or toCurrency()
• Test fixture in test/fixtures/<code>.js with matching exports
• Tests pass (npm test)

Breaking change? (click to expand)

Describe what breaks and how users should update:

[TylerVigario]

Confirmed the fix solves a real problem — reproduced the TS2307: Cannot find module 'n2words/en-US' error in a sandbox TS project with moduleResolution: "node" against main, and verified this patch clears it.

One thing worth tightening before merge: the catch-all "*": ["./src/*.d.ts"] mapping also makes n2words/utils/* type-check, even though exports explicitly walls it off with "./utils/*": null. At runtime the import still fails with ERR_PACKAGE_PATH_NOT_EXPORTED, so consumers get phantom types — TS green-lights an import that explodes when the code runs.

Suggested tighter pattern that preserves the existing privacy boundary:

"typesVersions": {
  "*": {
    "utils/*": [],
    "*": ["./src/*.d.ts"]
  }
}

The more-specific utils/* key matches first; an empty array means no candidates, so TS falls through and errors — matching the exports behavior. I verified locally that:

• n2words/en-US → resolves (catch-all * matches)
• n2words/utils/parse-cardinal → TS error (matches the runtime block)