Module not found: Can't resolve 'fs/promises'

[mrdrogdrog]

Hello,

I try to use the latest version (1.15.4) in a next.js project but if I try to create a build then I get this error:

./node_modules/@hpcc-js/wasm/dist/index.js
Module not found: Can't resolve 'fs/promises' in 'node_modules/@hpcc-js/wasm/dist'

Using the workaround from vercel/next.js#7755 doesn't work because, even if it compiles then, the browser tries to use the fs package which doesn't exist obviously.

I don't know which version introduced this bug because I upgraded from 1.12.8

[GordonSmith]

@mrdrogdrog I was unable to test against next.js, but I did add tests for "esbuild" which is probably as strict when it comes to bundling "require" statements.

Can you test with latest and report back?

[mrdrogdrog]

@GordonSmith

Nope. Didn't work. Sorry :/
I guess the environment detection isn't correct.

[mrdrogdrog]

Seems like just checking the existence of process isn't enough.
https://github.com/flexdinesh/browser-or-node/blob/master/src/index.js

[GordonSmith]

Hmm the env checking is coming from emscripten...

Quick sanity check - you are building for a browser and not for Node or Deno?

[GordonSmith]

Ok I have just tagged a new build (should be in the NPM repo shortly), can you retest and report back?

[GordonSmith]

v1.15.6 is released.

[mrdrogdrog]

I just nextjs which uses webpack and esbuild to create the browser bundle.

I'll test the version as soon as I have time.