[Bug]: no commonjs entry point

[hrdgit]

What happened?

Hi, as you can see on Yarn website, since version 3.1.1 the warning :

The package doesn't seem to have a commonjs entry point

-> https://yarnpkg.com/package?name=react-onesignal

I have error when I build the project.
When I add version 3.1.1 I don't have this error.

What browsers are you seeing the problem on?

Chrome (Chromium)

What operating system are you running?

Windows / Vercel / NextJs

Steps to reproduce?

yarn run build

What did you expect to happen?

Add the commonjs entry point because for some project its not possible to change builder config

Relevant log output

ReferenceError: module is not defined in ES module scope
This file is being treated as an ES module because it has a '.js' file extension and '/vercel/path0/node_modules/react-onesignal/package.json' contains "type": "module". To treat it as a CommonJS script, rename it to use the '.cjs' file extension.

[sherwinski]

Hi @hrdgit and thanks for reporting this. This issue looks possibly related to #180 -- someone from the team will investigate and follow up here.

[pavelescurazvan]

same problem - we're currently using version 3.0.1 which works, but when trying to update to latest it fails with that error

[EdwardNavarro]

Same problem using >= 3.2.0. Up to 3.1.1 works great.

[sherwinski]

Hey everyone, thanks for your patience as we investigate this issue. I've opened OneSignal/web-shim-codegen#122 to hopefully fix this.

[sherwinski]

This should now be fixed in https://github.com/OneSignal/react-onesignal/releases/tag/3.3.0 🚀
Please let us know if you are still experiencing issues with this -- thanks!