Typescript issue with `moduleResolution: NodeNext`

Expected behavior

node_modules/.pnpm/chart.js@3.9.1/node_modules/chart.js/auto/auto.mts(1,23): error TS2307: Cannot find module '../types/index.esm' or its corresponding type declarations.

Current behavior

Cuurently chart.js 's declaration files can not work with moduleResolution: NodeNext when targeting esm.

(Both with chart.js and chart.js/auto)

I think that al least chart.js/auto should respect latest typescript requirements on esm.

See https://www.typescriptlang.org/docs/handbook/esm-node.html for more details. This is somthing ts adds support in 4.7

Reproducible sample

Not related to chart runtime code

Optional extra steps/info to reproduce

No response

Possible solution

1. Add .js externsion for all files in source code
2. Use tools like rollup=plugin-dts to bundle a .d.mts declaration file for auto.mts to avoid a relative import without extension instead of creating a declaration wrapper.

Context

No response

chart.js version

all chart.js version are having this issue

Browser name and version

No response

Link to your project

No response

[dangreen]

@kurkle @LeeLenaleee I will research this issue soon.

[Mister-Hope]

From the typescript docs its not obvious if imports pointing to a directory would read the index.d.(m|c)ts or does it need to be explicit too?

For the latest moduleResolution NodeNext, yes, because in esm package you do have to use

import a from './dir/index.js';

And import a from './dir' or import a from './dir/' do not work. So typescript is asking the samething in nodenext or node16 in source code and declaration files( because declaration files could be source code while using by outher files).

Since we are outputing esm bundle in 3.9, I was thinking we’d better to convert the exisiting code to a valid esm code in typescript.

But as you are mentioning v4, I looked at the main branch, if you are planing to release v4 very soon (I probably mean in 30 days) I think we can make the changes only in v4, and make a depercated message in 3.9 esm bundle to tell users it’s broken.

It’s not very hard to make a workaround though yarn patch or pnpm patch or patch-packages(for npm) for users like me.

If anyone meets the same issue and needs a workaround, I would be happy to leave some pieces here.