[Pkg-javascript-devel] Bug#960901: Bug#960901: Buffer is a built-in node function

[Jonas Smedegaard]

Quoting Pirate Praveen (2020-12-29 12:27:34)
> 
> 
> On Tue, Dec 29, 2020 at 20:02, Ben Finney <bignose at debian.org> wrote:
> > Control: found -1 webpack/4.43.0-6
> > 
> > On 16-Jun-2020, Ben Finney wrote:
> >>  On 18-May-2020, Pirate Praveen wrote:
> >>  > 
> >> https://salsa.debian.org/js-team/node-clone/-/blob/master/clone.js#L109
> >>  > I think we may need to embed older version of buffer module in
> >>  > node-libs-browser
> >> 
> >>  Okay. I assume that is information for the ‘node-libs-browser’
> >>  maintainer, I think as a user I can't affect that.
> > 
> > Pirate, can you open a new bug report if necessary? I don't understand
> > the above information enough to know even whether an additional bug
> > report is required, or what it would report.
> > 
> 
> As user of webpack, you need to configure it properly. You need to 
> specify how webpack should handle node builtins like buffer.
> 
> >>  > For this particular case you can try embedding buffer module
> >>  > version 4.x as browsers need an equivalent module to features
> >>  > present only in node.
> >> 
> >>  This looks like advice for me to work around the problem. What do I
> >>  need to do? How do I (as a user of Webpack) “embed buffer module
> >>  version 4.x”?
> > 
> > What does that suggestion mean, and who should take action to make it
> > happen?
> 
> That was not an exact assessment. It was a possibility I could think.
> 
> In case of rollup, there is a plugin rollup-plugin-node-polyfills that 
> resolves these builtins for rollup. I don't know what is the equivalent 
> of webpack here.
> 
> If you don't have a specific requirement to using webpack, I suggest 
> you try rollup and rollup-plugin-node-polyfills instead of webpack.
> 
> I don't think this is an issue specific to the debian package, but 
> something that decided by webpack upstream. So you need to check the 
> upstream documentation for webpack and figure out how to tell webpack 
> to resolve these builtins.

Above by Pirate Praveen seems confirmed by this: 
https://stackoverflow.com/questions/53566238/why-does-webpack-includes-a-buffer-polyfill-by-default

I.e. in previous releases of webpack a polyfill was included with 
webpack, but with newer releases the user needs to decide how to handle 
it.  So understably confusing, but not specific to the Debian package 
and not an upstream bug either but documented behavior: 
https://webpack.js.org/migrate/5/#test-webpack-5-compatibility.

That link was my first hit on the following DuckDuckGo search:

  +"webpack" +"buffer"


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-javascript-devel/attachments/20201229/89fe28d0/attachment.sig>