fix typescript typing reference in package.json

[Goobles]

it seems that the types property was removed from the package.json here:
3afdfaf#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519L23

[fregante]

What is this for? Types already work without it. What config are you using that's causing issues?

[sindresorhus]

This is a problem with your tsconfig, not this package.

https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c#how-can-i-make-my-typescript-project-output-esm

[Goobles]

@sindresorhus In that case I will not be able to import this package into an non-pure-ESM angular library project. I've switched over to the commonjs compatible moize instead.

Pure ESM is just not always an option, since all downstream dependencies then need to be patched as well, all imports refactored to include a '.js' extension, kind of sad how this causes a schism in the package ecosystem.

[paul-vd]

This is a problem with your tsconfig, not this package.

https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c#how-can-i-make-my-typescript-project-output-esm

@sindresorhus Why does npm not detect types?

[fregante]

Why does npm not detect types?

That's a question you can ask npm. exports.types is what Node suggests here: https://nodejs.org/api/packages.html#community-conditions-definitions

[perry-mitchell]

Sure, but why avoid the defacto root types property? What would it cost to support it?

Not sure what moral ground is gained by dismissing it.