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
Note: this will be a major milestone for nanobundle v2
Bundling is for the application, bundling in NPM libraries is of no value (since we don't support UMD bundle)
Another problem with bundling is that it is incompatible with some Node.js semantics, such as subpath pattern exports. This is a blocker for some issues (#45, #48)
But building a library without bundling is not trivial today. Bundlers like esbuild and webpack don't support it. So it requires to use a transpiler like Babel or TypeScript separately with complex config.
nanobundle will v2 provides a no-bundle esbuild configuration. And will promotes it to default behavior later. May include rebranding as it is no longer "bundle".
The text was updated successfully, but these errors were encountered:
I have an strategy for this and have done some PoCs. I have to investigate more for compatibility with watch mode, but I believe I can begin late this month.
Note: this will be a major milestone for nanobundle v2
Bundling is for the application, bundling in NPM libraries is of no value (since we don't support UMD bundle)
Another problem with bundling is that it is incompatible with some Node.js semantics, such as subpath pattern exports. This is a blocker for some issues (#45, #48)
But building a library without bundling is not trivial today. Bundlers like esbuild and webpack don't support it. So it requires to use a transpiler like Babel or TypeScript separately with complex config.
nanobundle will v2 provides a no-bundle esbuild configuration. And will promotes it to default behavior later. May include rebranding as it is no longer "bundle".
The text was updated successfully, but these errors were encountered: