-
Notifications
You must be signed in to change notification settings - Fork 79
Conversation
…RRAY_SUPPORT which doesnt exist anymore
This is a breaking change, see feross/buffer@5daca86#commitcomment-19698936. We will pull this in with the next major version bump. Users that still need to support IE9 and IE10 can use a polyfill. |
@jhnns thx for the reply! |
IMO this is the right time to upgrade buffer. Currently IE9 has a market share of 0.12% and IE10 0.11% (see https://caniuse.com/usage-table) Within six month or so, when next webpack, browserify versions are released, these browsers will be even more irrelevant giving the trend Postponing the upgrade can loose the opportunity to be shipped in bundlers next releases |
Buffer v4 fails at simple case |
Bump. This is the time to upgrade |
any plans when this will be merged? |
Hi, can we please integrate this? |
This library is deprecated and won't accept Pull Requests that include Breaking Changes or new Features. Only bugfixes are accepted. We can't add a breaking change to webpack 4. webpack 5 will no longer use |
Hi,
Sorry previous PR #67 contained wrong email. Is it possible to update ferros/buffer to version 5? Problem is that versions 4.X refers to global
which leads to #60 and #31
this patch has fixed this problem and version 5.X works just fine.
We used shrinkwrap to work it around, but would be better to have updated version of the node-libs-browser (npm-shrinkwrap.json):
Thanks in advance!