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
externalizing packages is needed because some modules may rely on a certain folder structure and may not work correctly when bundled.
Local dependencies in a monorepo get bundled with this, which is nice.
However you still need to install certain packages, but if you use the original package.json, you may have local dependencies there that can't be installed after bundling with esbuild.
Problem 2
When you just externalize some packages and bundle others, you still have a package.json that contains all dependencies.
Solution:
lowlevel: have an option to list all packages that have been externalized and/or bundled. With this, you could do further manipulate the package.json to include or remove just those packages
sophisticated: have an option to generate a stripped down package.json that only contains the prod-dependencies that are actually needed.
The text was updated successfully, but these errors were encountered:
Problem 1:
i am using esbuild with externalized packages:
externalizing packages is needed because some modules may rely on a certain folder structure and may not work correctly when bundled.
Local dependencies in a monorepo get bundled with this, which is nice.
However you still need to install certain packages, but if you use the original package.json, you may have local dependencies there that can't be installed after bundling with esbuild.
Problem 2
When you just externalize some packages and bundle others, you still have a package.json that contains all dependencies.
Solution:
The text was updated successfully, but these errors were encountered: