TypeScript not taking into account new exports field of package.json

[lcswillems]

Search Terms

typescript
package.json
exports field
package resolution

Suggestion

The version 13.2 of Node.js allows ESM modules and a new package.json field, called exports, to select and rewrite exported files.

However, TypeScript doesn't take it into account.

Use Cases

For example, I have a library with a dist folder. And I only want to export this folder.

Currently, I have to add a bunch of files at the root of the package to include those in the dist folder.

Examples

I add:

exports: {
    "./": "./dist/"
}

to my package.json and want to be able to import my scripts with:

import myscript from "mylibrary/myscript";

instead of:

import myscript from "mylibrary/dist/myscript";

Checklist

My suggestion meets these guidelines:

• This wouldn't be a breaking change in existing TypeScript/JavaScript code
• This wouldn't change the runtime behavior of existing JavaScript code
• This could be implemented without emitting different JS based on the types of the expressions
• This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
• This feature would agree with the rest of TypeScript's Design Goals.

[lcswillems]

This is a duplicate of #33079