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
If I want to publish a package foo and allow people to import bar from 'foo/bar', it looks like that won't work with the way tsconfig-to-dual-package structures the output.
The default moduleResolution setting ignores export maps, so any export map entry for "./bar" won't work. The only way for a package to support this without any TS users running into issues, is to output all CJS and ESM files into the root of the package with different extensions, instead of using separate subdirectories.
The text was updated successfully, but these errors were encountered:
If I want to publish a package
foo
and allow people toimport bar from 'foo/bar'
, it looks like that won't work with the waytsconfig-to-dual-package
structures the output.The default
moduleResolution
setting ignores export maps, so any export map entry for"./bar"
won't work. The only way for a package to support this without any TS users running into issues, is to output all CJS and ESM files into the root of the package with different extensions, instead of using separate subdirectories.The text was updated successfully, but these errors were encountered: