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
Subpath patterns, as documented here, allow specifying patterns of files that can be imported in other packages. This is especially useful for packaging TypeScript. The exports object could look like this, for example:
If I import foo/bar.js in a package depending on this one, TypeScript will correctly look up the type information in out/bar.d.ts. esbuild, however, fails to resolve the import and exits with a message along the lines of "foo/bar.js" is not exported.
I think this issue is a request for this feature: nodejs/node#39635. That PR changed node's path resolution algorithm after esbuild implemented it, and esbuild's implementation now needs to be updated.
Subpath patterns, as documented here, allow specifying patterns of files that can be imported in other packages. This is especially useful for packaging TypeScript. The exports object could look like this, for example:
If I import
foo/bar.js
in a package depending on this one, TypeScript will correctly look up the type information inout/bar.d.ts
. esbuild, however, fails to resolve the import and exits with a message along the lines of"foo/bar.js" is not exported
.I've created a hopefully understandable minimal reproduction of this issue at https://github.com/sybereal/esbuild-export-pattern-repro.
The text was updated successfully, but these errors were encountered: