Closed abhinavrastogi-harness closed 1 year ago
What bundler are you using? A couple of them are broken with how they respect the browser field.
The size isn’t a concern; it’s the smallest size that can correctly address the problem it’s solving.
I faced this issue while bundling using Rollup.
the same question too
If rollup is unable to bundle this package, please file an issue on rollup.
has any update? it still happened when I use yarn2 & vite to compile it
any updates here?
I believe this remains an issue with specific bundlers.
If there's something actionable here, i'd be happy to reopen.
I'm getting a JS exception after upgrading to the latest version:
yarn.lock
entry for my dependency:Another concern is that the bundle size increased by 30kb (because of
qs
's new dependencyside-channel
probably) with this upgrade. This one is not a blocker, but definitely a concern.