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
I'm using and importing a node module in multiple files like this import { Foo } from '@foo';. But when I build and say --external:@foo there are multiple import statements in the bundled out file like this: import { Foo as Foo2} from '@foo'.
I've seen this issue, but it does not make sense to me how this is the default behavior. This is a very common use case is it not? Importing node modules in multiple part of your code base and excluding them from the bundle because in production you load the node module through a <script> tag or something like that.
Is this something that is possible with esbuild?
The text was updated successfully, but these errors were encountered:
I'm using and importing a node module in multiple files like this
import { Foo } from '@foo';
. But when I build and say--external:@foo
there are multiple import statements in the bundled out file like this:import { Foo as Foo2} from '@foo'
.I've seen this issue, but it does not make sense to me how this is the default behavior. This is a very common use case is it not? Importing node modules in multiple part of your code base and excluding them from the bundle because in production you load the node module through a
<script>
tag or something like that.Is this something that is possible with esbuild?
The text was updated successfully, but these errors were encountered: