PhosphorIcon 2.0.9 - require() of ES modules is not supported

[cristiano-giacomi]

PhosphorIcon 2.0.9 - require() of ES modules is not supported

[BrandonFitzgibbon]

Just adding our voice that we rolled back to 2.0.9. This issue started in 2.0.10 after changes in PR #56.

[KenanYusuf]

I have just started seeing this error on v2.0.8 on a clean install of a project with @phosphor-icons/react

[rektdeckard]

Hey all, I am assuming this is Node >= 18 (think) strategy for Determining modules system, and will be pushing an update where artifacts are emitted with .cjs and .mjs extensions, as opposed to .umd.js and .es.js. Will update here when live.

[mountagency]

Can confirm this. Rolled back to 2.0.8.

[dolmios]

Interesting. 2.0.9 is my last working version, with 2.0.10 throwing that error.

unhandledRejection Error [ERR_REQUIRE_ESM]: require() of ES Module /app/node_modules/.pnpm/@[email protected][email protected][email protected]/node_modules/@phosphor-icons/react/dist/index.umd.js not supported.

index.umd.js is treated as an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which declares all .js files in that package scope as ES modules.

Instead rename index.umd.js to end in .cjs, change the requiring code to use dynamic import() which is available in all CommonJS modules, or change "type": "module" to "type": "commonjs" in app/node_modules/.pnpm/@[email protected][email protected][email protected]/node_modules/@phosphor-icons/react/package.json to treat all .js files as CommonJS (using .mjs for all ES modules instead).

[rektdeckard]

OK all, added the exports.require fields in package.json and renamed all the artifacts. There is a build published on NPM at version 2.1.3, which can be installed under the tag @phosphor-icons/react@next. Please give this a try and let me know if it fixes things for you.

[rektdeckard]

Live in stable >=2.0.13. Marking as resolved.