Issues on using rxing-wasm in nextjs

[borracciaBlu]

rxing-wasm/pkg/package.json

Line 37 in db14d1c

"default": "./node-esm.js"

As because of this, the default is the node runtime and it will break used in a PWA.

Possible workaround in nextjs:

// next.config.js

const nextConfig = {
      .
      .
      .
     webpack: function(config, options) {
          config.resolve.alias["rxing-wasm] = path.resolve(__dirname, "./node_modules/rxing-wasm/rxing_wasm.js");
          
          return config;
     }
};

[hschimke]

Thank you, I'll look into this.

[hschimke]

Background: I'm not familiar with how PWAs work, so it may require a little research on my part to make sure I'm not breaking something else when I make this fix. I might also try to build some small testing tools to verify that I'm not adding regressions when I do stuff like this. Thanks again for the bug report.

A question: does the previous version on NPM work in a PWA?

[borracciaBlu]

Yes, previous version 0.3.1 was working because package.json didn't have exports in it.
Now that we have a node version and a browser webpack has to decide which one of them to use and as nextjs has a server side of the things it uses the node version.

I guess my point here is that before the default was browser and now it's node.

[hschimke]

So, this issue would persist if I were to make this change:

"exports": {
    ".": {
      "types": "./rxing_wasm.d.ts",
      "browser": "./rxing_wasm.js",
      "node": "./node-esm.js",
      "default": "./rxing_wasm.js"
    }
  }

My thought was that this would remove the default component and force it into picking node or browser, but from what you say that might not help since nextjs is sort of both.

I checked this version and it doesn't seem to have any impact on ESM loading, but I'm not sure on nextjs.

[borracciaBlu]

I've done some tests with nextjs, and it seems the issue is on their side as when I run the build it's assuming is a node solution by default. Even changing the default to browser and adding node it doesn't fix.

So the solution is the next config change