feat: Add exports.types to package.json

[andreavaccari]

This allows TypeScript to correctly resolve type imports when using Node's module resolution with:

• "moduleResolution": "NodeNext", or
• "moduleResolution": "Node16"

Refs:

• Typescript docs
• Node docs

[marijnh]

What problem does this address?

[andreavaccari]

Hi @marijnh, I just added a description to the PR. Apologies for not doing so when submitting.

[marijnh]

Nice. Will this work both for CommonJS and ES module resolution?

[andreavaccari]

The rest of the specifications were correct, and this change won't affect CJS and ESM resolution, so all resolution paths will work correctly. I like to run npx -y publint (see also the web tool) to make sure there aren't any errors in the exports specs, however this won't catch missing specifications like in this case. Getting these right is quite difficult! (ref).

[andreavaccari]

Hi @marijnh, anything I can do to help get this PR plus this and this merged? Thank you!

[marijnh]

I'm not seeing any problems when I import the ProseMirror modules from a TypeScript project that has moduleResolution set to node16, so I am still confused about what this adds.

[marijnh]

See also ProseMirror/prosemirror#1305 (comment)