Skip to content

UMD version is used when bundled with Webpack #42

@jgonera

Description

@jgonera

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).

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions