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
Presently, if an entry file matches of the external rules, the following error is raised:
[ERROR] The entry point "y.ts" cannot be marked as external
I created esrun, which is a Typescript runner that uses esbuild under the hood. For the sake of esm/cjs compatibility, dependencies are not bundled into the final executable. To achieve this, I mark the following files as externals:
"./node_modules/*"
"../node_modules/*"
"../../node_modules/*"
"../../../node_modules/*"
"../../../../node_modules/*"
btw, a better way to mark "all parent node_modules" would be great, but that's not the point of the issue
This works fine, until an esrun user tried to execute a file that is already inside a node_modules. The error is described in this issue. Then the entry file is also matching one of the external string so it raises the forementioned bug.
Two solutions come to me:
preventing one of the entry files to be marked as external even if they match (because it makes no sense to have an external entry file),
or add an "internal" parameter that takes strings / regexps / globs to describe files that should be treated as externals (even if they match).
The text was updated successfully, but these errors were encountered:
Presently, if an entry file matches of the
external
rules, the following error is raised:[ERROR] The entry point "y.ts" cannot be marked as external
I created esrun, which is a Typescript runner that uses esbuild under the hood. For the sake of esm/cjs compatibility, dependencies are not bundled into the final executable. To achieve this, I mark the following files as externals:
This works fine, until an
esrun
user tried to execute a file that is already inside anode_modules
. The error is described in this issue. Then the entry file is also matching one of theexternal
string so it raises the forementioned bug.Two solutions come to me:
The text was updated successfully, but these errors were encountered: