Deploying the wasm through webpack

[damageboy]

The docs mention that:

Bundlers (RollupJS / WebPack) will ignore the WASM files, so you will need to manually ensure they are present in your final distribution (typically they are placed in the same folder as the bundled JS)

Is there some official guidelines for what needs to happen with webpack, for example to get the file pushed all the way from node_modules down to some static directory?

[GordonSmith]

I suspect WebPack has plugins which will handle this for you - but what I tend to do is treat the wasm file the same as I might any asset (like png or wav file) and copy it from the node_modules folder into my "dist" or "build" folder next to where webpack is outputting its files.

At which point it may "just work", but if not you will need to call wasmFolder with the location.

Alternatively you can set the following global variable: __hpcc_wasmFolder to the same URL your pulling your webpacked files from (before any page tries to load the wasm file).

[tuckergordon]

For anyone who stumbles across this thread, I was able to deploy the wasm through rollup with by using the rollup-plugin-copy module to move the necessary files into the build folder:

// rollup.config.js
import copy from 'rollup-plugin-copy';

...
  plugins: [
    copy({
      targets: [
        { 
          src: 'node_modules/@hpcc-js/wasm/dist/graphvizlib.wasm',
          dest: 'public/build'
        },
        { 
          src: 'node_modules/@hpcc-js/wasm/dist/graphvizlib.wasm',
          dest: 'public/build/@hpcc-js/wasm'
        },
        {
          src: 'node_modules/@hpcc-js/wasm/dist/index.min.js',
          dest: 'public/build/@hpcc-js/wasm'
        }
      ]
    }),
    ..
  ]