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 building an app that targets only new browsers but when I import JSBI from 'jsbi' Webpack uses the UMD bundle because the browser field from package.json takes precedence over module field. My understanding was that the browser field was used only for packages that implement browser-specific code (using browser APIs). Is there a reason why an UMD build is needed these days given how widely used code bundlers are?
This is not a big deal now since the UMD version is only slightly bigger but will become more relevant if #22 gets resolved (UMD build won't work with tree-shaking).
The text was updated successfully, but these errors were encountered:
Tangential to this (but also not relevant until this is resolved), it would be great if non-UMD versions were not minified. I'm trying to debug something right now and all I see in the profiler are single-letter function names. I know I can just copy the JSBI source over to my project but it's slightly less convenient :)
I'm building an app that targets only new browsers but when I
import JSBI from 'jsbi'
Webpack uses the UMD bundle because thebrowser
field frompackage.json
takes precedence overmodule
field. My understanding was that thebrowser
field was used only for packages that implement browser-specific code (using browser APIs). Is there a reason why an UMD build is needed these days given how widely used code bundlers are?This is not a big deal now since the UMD version is only slightly bigger but will become more relevant if #22 gets resolved (UMD build won't work with tree-shaking).
The text was updated successfully, but these errors were encountered: