esbuild is not strong in splitting chunks. some related issues (#16, #207, #1781, #2208, #2227, #2419)
if the onResolve hook would have the entire import information a plugin could implement much better splitting strategy based on native imports.
The idea is, if a plugin can collect all the imported named symbols from a specific import-statement request, it could externalize the request and generate a esm bundle (with correct exports) from a cjs/umd module like react.
my goal is to optimize large code base watch mode by externalizing modules to separate builds.
esbuild is not strong in splitting chunks. some related issues (#16, #207, #1781, #2208, #2227, #2419)
if the
onResolvehook would have the entire import information a plugin could implement much better splitting strategy based on native imports.The idea is, if a plugin can collect all the imported named symbols from a specific
import-statementrequest, it could externalize the request and generate aesmbundle (with correct exports) from acjs/umdmodule like react.my goal is to optimize large code base watch mode by externalizing modules to separate builds.