Nuffed the callback args for error handling

Author: aaronpowell

ReleaseNotes.md

@@ -1 +1 @@
-* Trying to work around [this issue](https://github.com/Microsoft/azure-pipelines-tasks/issues/4958) in publishing releases
+Helps when your error handling is looking at the error argument to the callback...

package.json

@@ -1,6 +1,6 @@
 {
   "name": "golang-wasm-async-loader",
-  "version": "0.2.6",
+  "version": "0.3.0",
   "description": "Golang WebAssembly loader for webpack that generates an async pattern for working with Go's WebAssembly output",
   "main": "dist/index.js",
   "scripts": {

src/index.ts

@@ -79,9 +79,9 @@ function loader(this: webpack.loader.LoaderContext, contents: string) {
   const outFile = `${this.resourcePath}.wasm`;
   const args = ["build", "-o", outFile, this.resourcePath];
 
-  execFile(goBin, args, opts, (_, err) => {
+  execFile(goBin, args, opts, (err) => {
     if (err) {
-      cb(new Error(err));
+      cb(err);
       return;
     }