./pkg created by default when wasm is located in a different folder

[carlosouro]

If you have a crateDirectory located elsewhere in your filesystem, the plugin will still create an empty ./<outDir> folder locally to the main build process root.

Example:

new WasmPackPlugin({
  crateDirectory: path.resolve(__dirname, "./myRustPlugin")
})

This would create an empty pkg subfolder in ./pkg, and not in ./myRustPlugin/pkg as expected (and according to wasm-pack build).

Note that currently it is possible to workaround this issue by enforcing a full qualified path outDir to the destination pkg location, like so:

new WasmPackPlugin({
  crateDirectory: path.resolve(__dirname, "./myRustPlugin"),
  outDir: path.resolve(__dirname, "./myRustPlugin/pkg")
})

But if you simply use outDir: "build" or leave outDir to the "pkg" default, the problem arises.

The problem appears to be here:

wasm-pack-plugin/plugin.js

Line 98 in a0b20c0

fs.mkdirSync(this.outDir);

[kopotp]

same for me

[Directory]

The issue with this workaround for me at least is that the pkg directory isnt empty. it contains a single empty index.js. when forcing it to use the same pkg directory as where the rust code really is supposed to compile to it overwrites the ledgitamate index.js file with an empty one. and now it cant be imported.

[wleslie]

This issue may overlap with a few other open issues: #74, #81, #87