feat: Add support for Node JS

[GordonSmith]

Refactor tests so they can run from browser and NodeJS

Signed-off-by: Gordon Smith GordonJSmith@gmail.com

[meoyawn]

just tried pulling 1.0.0 and got

error - ./node_modules/@hpcc-js/wasm/dist/index.es6.js:2:0
Module not found: Can't resolve 'fs'
null

when trying to run this on Next.js

[GordonSmith]

Hmmm sounds like the es6 is leaking a conditional NodeJS requirement...

You can work around it with the following: vercel/next.js#7755 but I will investigate my end to see if I can clean it up as well...

[meoyawn]

also a weird thing on 0.3.15: importing a (supposedly) simple wasm wrapper pulls 425kB of JS. I'm very new to JS modules but maybe this includes webpack polyfilling node modules like fs...

[meoyawn]

though my editor plugin is probably wrong https://bundlephobia.com/result?p=@hpcc-js/wasm@1.0.0

[GordonSmith]

You can also see the individual file sizes here: https://cdn.jsdelivr.net/npm/@hpcc-js/wasm@1.0.0/dist/

The index.min.js is probably the most accurate.

[GordonSmith]

@meoyawn I just released 1.0.1 which should fix your issue (if you can verify that would be appreciated).

[meoyawn]

@GordonSmith can confirm 1.0.1 works with next.js, thanks!