You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When working with moduleResolution: nodeNext, the type definitions are interpreted by typescript as being commonjs. It doesn't seem to register the existence of the module property in the package.json.
So, the easiest way to resolve this to make TS happy is to add the exports property to the package.json and output a separate .d.ts file for the esmodule output.
When working with
moduleResolution: nodeNext
, the type definitions are interpreted by typescript as being commonjs. It doesn't seem to register the existence of themodule
property in the package.json.So, the easiest way to resolve this to make TS happy is to add the
exports
property to the package.json and output a separate .d.ts file for the esmodule output.The text was updated successfully, but these errors were encountered: