node failing due to unexpected character '#' about fetch-blob HOT 8 CLOSED

• https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Private_class_fields
• https://caniuse.com/mdn-javascript_classes_private_class_fields

from fetch-blob.

@pkieltyka which version of Node are you running? You need at least 12.20 or 14.13, as indicated here:

from fetch-blob.

Have the same problem with node 16.15.0 in a nuxt project. I suspect Webpack when importing from thenode_modules, seems to be missing Babel for the transpile.

I use the "Private Class Fields" in my project, so Babel Configuration works.

When I do the transpile via nuxt I still get these warnings:

from fetch-blob.

@ThornWalli are you packaging for the browser? The browser already has it's own Blob and File, this is for the Node.js runtime...

from fetch-blob.

I use the package ‘cross-blob‘.
https://www.npmjs.com/package/cross-blob

The background here is the client and server build.

from fetch-blob.

Do you actually get any errors, or are you just getting warnings about node:* imports? This issue is specifically about the Module parse failed: Unexpected character '#' error...

from fetch-blob.

Think you should rather do some code splitting, do some conditional loading to load fetch-blob only when needed.

from fetch-blob.

Got no more response...
just update your dependencies, all evergreen browser and backends all do support private class field right now...

from fetch-blob.