export Types for typescript & npm

[KrakenTyio]

@types/y18n are 5 years old.

I see your project is already in typescript, but you are not exporting *.d.ts to npm

also in deno.ts you have build/lib/index.d.ts but by npm this file is missing

[dopry]

@types/y18n is out of date and causing confusion on our team.

[peterblazejewicz]

Hey folks,
I think there is a proper NPM package distribution missing. Everything else is in place IMO (there is a proper
reference in the package.json to allow TypeScript tsc use automatic types resolution properly):
https://github.com/yargs/y18n/blob/v5.0.0/package.json#L11
what's missing is publishing this file to NPM registry:

npm pack y18n
npm notice
npm notice package: y18n@5.0.8
npm notice === Tarball Contents ===
npm notice 731B  LICENSE
npm notice 6.8kB build/index.cjs
npm notice 192B  build/lib/cjs.js
npm notice 6.3kB build/lib/index.js
npm notice 377B  build/lib/platform-shims/node.js
npm notice 1.8kB package.json
npm notice 3.9kB CHANGELOG.md
npm notice 3.2kB README.md
npm notice 183B  index.mjs

thanks!

[shadowspawn]

At the time the main yargs package was converted to TypeScript, it was decided to have users continue to use@types/yargs which was more sophisticated and opinionated than the internal typings, and well established.. The same pattern was followed for the yargs libraries including y18n that the project typings were not exported (with some accidental exceptions!).

It looks like the stale y18n types were removed for v5 (thanks @peterblazejewicz): https://github.com/DefinitelyTyped/DefinitelyTyped/pull/53972/files

The longterm fix is probably to export types as part of this package, since there won't be conflicting usage in the wild.