[Bug]: Not recognized as ES on pnpm

[MM294]

What happened?

⨯ unhandledRejection [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 'frontend/node_modules/.pnpm/react-onesignal@3.2.3/node_modules/react-onesignal/package.json' contains "type": "module". To treat it as a CommonJS script, rename it to use the '.cjs' file extension.] { type: 'ReferenceError' }

When using pnpm we get this error, we can fix this by renaming

mv node_modules/.pnpm/react-onesignal@3.2.3/node_modules/react-onesignal/dist/index.js node_modules/.pnpm/react-onesignal@3.2.3/node_modules/react-onesignal/dist/index.cjs

What browsers are you seeing the problem on?

Other

What operating system are you running?

macOS 15.5

Steps to reproduce?

Node 20.19.2
pnp 10.11
next 15.1.6
react 19.0.0
reacct-onesignal 3.2.3

pnpm install
next build

What did you expect to happen?

expected it to build

Relevant log output

[sherwinski]

Hi @MM294 and thanks for reporting this. Someone from the team will investigate and get back to you with next steps and/or further questions if needed.

[anargiris]

I have the same problem using yarn

[pavelescurazvan]

same problem using npm - 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!