yarn start leads to TypeError

[flosse]

That's what I did:

git clone https://github.com/MartinKavik/seed-quickstart-webpack
cd seed-quickstart-webpack
yarn
yarn start

That's the error msg:

[flosse]

...the funny thing is, I try to move from JS/NPM to Rust just because of this kind of problems ;-)

[MartinKavik]

It seems that they were playing with fs.promises - jprichardson/node-fs-extra#551 (comment).

And it's probably the reason why your promises are undefined - https://github.com/wasm-tool/wasm-pack-plugin/blob/872af9ec5f57837c2234a488a76a407ff227b40f/plugin.js#L120.

So it's possible that I (and CI) have a little bit different NodeJS version..
And you know the JS drill.. what's your NodeJS version and OS, please?

[flosse]

what's your NodeJS version and OS, please?

• node v10.15.3
• npm 6.4.1
• yarn 1.13.0
• nixos 19.03

[MartinKavik]

Issue in wasm-pack-plugin: wasm-tool/wasm-pack-plugin#69

Temporary workaround: Just copy https://raw.githubusercontent.com/wasm-tool/wasm-pack-plugin/2d74352d703526508e2de95d6b1cacbca1b2101f/plugin.js to /node_modules/@wasm-tool/wasm-pack-plugin/plugin.js

[fattenap]

This looks like it may have been resolved in the current version on wasm-pack-plugin@1.3.1

[MartinKavik]

This looks like it may have been resolved in the current version on wasm-pack-plugin@1.3.1

@fattenap Are you sure? My PR hasn't been merged to wasm-pack and the bug is specific to only some OSs and NodeJS versions - it's not super easy to reproduce it.

Also there is still wasm-pack-plugin v. 1.0.1 in our package.json because newer versions brake our CI (I don't remember the error).

[fattenap]

Oh, I didn't realise it was for specific Node versions. Reopening.