webpack error migrating from 0.9.15 -> 0.9.16

[dbo]

I get the following error with the latest version:

ERROR in ../../node_modules/@undecaf/zbar-wasm/dist/main.js 15:653-669
Module not found: Error: Can't resolve 'module' in '/myprj/node_modules/@undecaf/zbar-wasm/dist'
resolve 'module' in '/myprj/node_modules/@undecaf/zbar-wasm/dist'
  Parsed request is a module
  using description file: /myprj/node_modules/@undecaf/zbar-wasm/package.json (relative path: ./dist)
    Field 'browser' doesn't contain a valid alias configuration
    resolve as module
      looking for modules in /myprj/packages/sub-project/node_modules
        single file module
          using description file: /myprj/packages/sub-project/package.json (relative path: ./node_modules/module)
            no extension
              Field 'browser' doesn't contain a valid alias configuration
              /myprj/packages/sub-project/node_modules/module doesn't exist
            .js
              Field 'browser' doesn't contain a valid alias configuration
              /myprj/packages/sub-project/node_modules/module.js doesn't exist
        /myprj/packages/sub-project/node_modules/module doesn't exist
      looking for modules in /myprj/node_modules
        single file module
          using description file: /myprj/package.json (relative path: ./node_modules/module)
            no extension
              Field 'browser' doesn't contain a valid alias configuration
              /myprj/node_modules/module doesn't exist
            .js
              Field 'browser' doesn't contain a valid alias configuration
              /myprj/node_modules/module.js doesn't exist
        /myprj/node_modules/module doesn't exist
 @ ./out/file.js 1:0-51 14:22-35 21:22-35

webpack 5.88.2 compiled with 1 error in 1608 ms

[undecaf]

As a response to #9, I removed the Node polyfills from the ES module of zbar-wasm in 0.9.16 beause e.g. require() was polyfilled with an empty method; this caused loading of zbar-wasm as an ES module to fail in Node.

On the other side, it appears that you intend to use zbar-wasm as an ES module in a browser. The build with 0.9.16 fails because module is no longer polyfilled.

As for now, including module in your Webpack externals should solve the problem. The next version of zbar-wasm (which I am preparing) will include separate ES modules for Node and for browsers.

[borracciaBlu]

Similar issue here using next.

with 0.9.15 worked like a charm.
After the update to 0.9.16 i've got the following error:

./node_modules/@undecaf/zbar-wasm/dist/main.js
Module not found: Can't resolve 'module'

Please consider i did use the import syntax

import { scanImageData } from '@undecaf/zbar-wasm';

instead if i use require:

const { scanImageData } = require('@undecaf/zbar-wasm');

i've got:

./node_modules/@undecaf/zbar-wasm/dist/main.cjs
Module not found: Can't resolve 'fs'

[undecaf]

@borracciaBlu This appears to be the same situation as above: main.js is the ESM build of zbar-wasm without polyfills for the Node dependencies such as module and fs. If targeting a browser with ESM, these dependencies cannot be resolved.

Declaring module and/or fs as external for your bundler should solve the problem for now. In a browser environment, the code referencing module and fs in zbar-wasm is dead code anyway.

I am sorry for this mess in 0.9.16, and I am working on cleaning up the package structure and providing more bundling hints in the docs.

[undecaf]

@dbo, @borracciaBlu zbar-wasm v0.10.0 should resolve this, although a different bundler configuration may be necessary.

Please feel free to re-open.

[borracciaBlu]

@undecaf working, thanks. I was able to get consistent results as in 0.9.15.