UnhandledRejection Error: Cannot Find React Package

Question

UnhandledRejection Error: Cannot Find React Package

IvanNavin opened this issue 4 months ago · comments

I'm encountering an unhandled rejection error with the following details:

64.64 unhandledRejection Error [ERR_MODULE_NOT_FOUND]: Cannot find package '/usr/src/app/node_modules/@phosphor-icons/react/dist/node_modules/.pnpm/react@18.2.0/node_modules/react/' imported from /usr/src/app/node_modules/@phosphor-icons/react/dist/node_modules/.pnpm/react@18.2.0/node_modules/react/cjs/react-jsx-runtime.production.min.mjs
64.64 Did you mean to import react/index.js?
64.64     at new NodeError (node:internal/errors:399:5)
64.64     at legacyMainResolve (node:internal/modules/esm/resolve:235:9)
64.64     at packageResolve (node:internal/modules/esm/resolve:876:14)
64.64     at moduleResolve (node:internal/modules/esm/resolve:938:20)
64.64     at defaultResolve (node:internal/modules/esm/resolve:1153:11)
64.64     at nextResolve (node:internal/modules/esm/loader:163:28)
64.64     at ESMLoader.resolve (node:internal/modules/esm/loader:838:30)
64.64     at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)
64.64     at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:77:40)
64.64     at link (node:internal/modules/esm/module_job:76:36) {
64.64   type: 'Error',
64.64   code: 'ERR_MODULE_NOT_FOUND'
64.64 }

It seems like the React package is not being found properly. The error suggests that it cannot locate the React package at a specific path. The message also includes a suggestion: "Did you mean to import react/index.js?"

OS: MacOs, Node.js, Docker
Stack:

@phosphor-icons/react version 2.1.4
Next.js version 13.4.7
React version 18.2.0
React-dom version 18.2.0

Global packages:

Node.js version 18.16.0
npm version 9.8.1

Any insights or guidance on resolving this issue would be greatly appreciated.

Omri commented 4 months ago

same here

Omri · Answer 1 · Wed Apr 03 2024 01:01:30 GMT+0800 (China Standard Time)

@rektdeckard
Could be related to this ?
2f22ef1
not sure though.
I assume some build issue since it is weird to ship "node_modules" inside of a dist directory.

oscadev · Answer 2 · Wed Apr 03 2024 12:02:37 GMT+0800 (China Standard Time)

Same here. Cannot use IconContext.Provider in _app.tsx in a Next JS (pages router) app, or I get the "Did you mean to import "react/index.js"?" crash

oscadev · Answer 3 · Wed Apr 03 2024 12:06:32 GMT+0800 (China Standard Time)

@IvanNavin I fixed it. It is because you are importing the ssr version instead of the normal react version. Change your ic import to "import { ArrowArcRight } from "@phosphor-icons/react";" instead of "import { ArrowRight } from "@phosphor-icons/react/dist/ssr";

Update: It was a fluke, or something. The problem is back.

Holovko Ivan · Answer 4 · Wed Apr 03 2024 12:13:49 GMT+0800 (China Standard Time)

@oscadev I would be very happy to fix this using that approach, but I don't have a path like '@phosphor-icons/react/dist/ssr' anywhere.

xwu-alterdomus · Answer 5 · Wed Apr 03 2024 13:57:29 GMT+0800 (China Standard Time)

Any update for this issue. it works as expected inprevious version, that is 2.0.15
here are my local env:

nextjs : 13.2.4
React: 18.2.0
react-dom:18.2.0
@phosphor-icons/react: 2.1.4
nodejs: 18.20.0
dockerimage: node:18-alpine

Andreas Halvorsen Tollånes · Answer 6 · Wed Apr 03 2024 16:50:39 GMT+0800 (China Standard Time)

Can confirm I am seeing the same issue on 2.0.14, building a docker image for production in node:20.10.0

Fred Besteman · Answer 7 · Thu Apr 04 2024 03:40:06 GMT+0800 (China Standard Time)

Same here. I updated to Nextjs 14 and React to 18 along with that and that's when the issue started.

nextjs: 14.1.4
React: 18.2.0
react-dom: 18.2.0
@phosphor-icons/react: 2.1.4
nodejs: 20.12.1
package manager: pnpm

Using next dev --turbo to run my dev takes care of the error. Maybe a webpack issue?

Saurabh Charde · Answer 8 · Thu Apr 04 2024 17:40:00 GMT+0800 (China Standard Time)

@rektdeckard Could be related to this ? 2f22ef1 not sure though. I assume some build issue since it is weird to ship "node_modules" inside of a dist directory.

Yep. It looks to be this. I fixed it by installing the 2.1.3 package which was released on npm but was never published here on github. It is probably some weird bundling issue but then again why do we even need to ship node_modules with specific react version?

Andreas Halvorsen Tollånes · Answer 9 · Mon Apr 08 2024 15:53:35 GMT+0800 (China Standard Time)

@rektdeckard Could be related to this ? 2f22ef1 not sure though. I assume some build issue since it is weird to ship "node_modules" inside of a dist directory.

Yep. It looks to be this. I fixed it by installing the 2.1.3 package which was released on npm but was never published here on github. It is probably some weird bundling issue but then again why do we even need to ship node_modules with specific react version?

Are you sure you didn't have this cached? I can't get any of the mentioned versions working nor my old version of 2.0.13 after doing yarn cache clean

My versions:

Node: 20.10.0
"@phosphor-icons/react": "^2.1.4",
"react": "^18.2.0",
"react-dom": "^18.2.0",
next": "^12.3.1",

Saurabh Charde · Answer 10 · Mon Apr 08 2024 17:07:23 GMT+0800 (China Standard Time)

@fanzypantz yep. I checked it after I did yarn cache clean. Here are my versions:

"dependencies": {
    "@phosphor-icons/react": "2.1.3",
    "next": "14.1.4",
    "react": "18.2.0",
    "react-dom": "18.2.0",
}

Andreas Halvorsen Tollånes · Answer 11 · Mon Apr 08 2024 20:55:52 GMT+0800 (China Standard Time)

The weird thing, is that this works on my coworkers computer, he also did the cache cleaning, and a random local Linux server we have for development. Edit: He could not build the docker image

But not in our dockerimage, or my local computer. The Dockerfile isn't especially complicated.

# Node version
FROM node:20.10.0 AS builder

ENV NEXT_PUBLIC_API_ENDPOINT=
ENV NEXT_PUBLIC_BASE_URL=

# Install required build tools
RUN apt-get update && \
    apt-get -y install gcc

# Create app directory
WORKDIR /app

# Add the source code to app
COPY package*.json ./
COPY lerna.json ./
COPY /packages ./packages

# Install all the dependencies
RUN yarn install
RUN yarn global add tscpaths

COPY . .

# Generate the build of the application
RUN yarn build

FROM node:20.10.0 AS runner

COPY --from=builder /app/node_modules ./node_modules
COPY --from=builder /app/packages ./packages
COPY --from=builder /app/package*.json ./
COPY --from=builder /app/lerna.json ./

EXPOSE 3000
CMD [ "yarn", "start" ]

Nico Domino · Answer 12 · Sun Apr 14 2024 01:46:33 GMT+0800 (China Standard Time)

Seeing this issue with the following dependencies as well when we upgraded to 2.1.4.

"dependencies": {
    "@phosphor-icons/react": "^2.1.4",
    "next": "14.2.1",
    "react": "^18.2.0",
    "react-dom": "^18.2.0",
}

Importing like so as it reduces the number of modules next.js includes

import { Flask } from "@phosphor-icons/react/dist/csr/Flask"

Downgrading back to @phosphor-icons/react@2.0.15 seems to have fixed it again.

Saurabh Charde · Answer 13 · Sun Apr 14 2024 03:43:06 GMT+0800 (China Standard Time)

Importing like so as it reduces the number of modules next.js includes

@ndom91 have you tried optimizePackageImports?

Leo · Answer 14 · Thu Apr 18 2024 20:56:08 GMT+0800 (China Standard Time)

@rektdeckard Could be related to this ? 2f22ef1 not sure though. I assume some build issue since it is weird to ship "node_modules" inside of a dist directory.

Yep. It looks to be this. I fixed it by installing the 2.1.3 package which was released on npm but was never published here on github. It is probably some weird bundling issue but then again why do we even need to ship node_modules with specific react version?

Are you sure you didn't have this cached? I can't get any of the mentioned versions working nor my old version of 2.0.13 after doing yarn cache clean

My versions:

Node: 20.10.0
"@phosphor-icons/react": "^2.1.4",
"react": "^18.2.0",
"react-dom": "^18.2.0",
next": "^12.3.1",

Make sure to use "2.1.3" and not "^2.1.3", as this will still resolve to install "2.1.4" ;)
Check your yarn.lock for what it's actually installing.

Tobias Fried · Answer 15 · Fri Apr 19 2024 01:47:31 GMT+0800 (China Standard Time)

Hi all, apologies for delay in resolving this! Testing the hypothesis that it is caused by relying on automatic JSX runtime, as @omridevk suggests. I will be pushing some pre-release updates to NPM shortly and would appreciate some help testing, as many of these problems are intractable and arise from specific nuances of project setup.

Tobias Fried · Answer 16 · Fri Apr 19 2024 03:45:00 GMT+0800 (China Standard Time)

Have published an alpha that reverts to classic JSX runtime. Checked out locally with next@13.5.1, react@18.2.0, react-dom@18.2.0 on Node 20, but help testing is appreciated!

pnpm install @phosphor-icons/react@next
#                            ^ or @2.1.5-alpha.3

Tobias Fried · Answer 17 · Fri Apr 19 2024 04:37:00 GMT+0800 (China Standard Time)

We had in fact been bundling the automatic JSX runtime, which was expecting to find a version of react in a sibling directory rather than as a global.

This was a non-issue in most builds, since the end-user's build tooling was probably also using automatic JSX runtime, consuming the ESM build of this library, and thus performing the JSX transform itself.

I don't see any harm in reverting to classic JSX runtime. It has marginal performance and bundle impacts, so going ahead and shipping this.

Saurabh Charde · Answer 18 · Fri Apr 19 2024 23:13:53 GMT+0800 (China Standard Time)

Can confirm updating to 2.1.5 fixed it for me. Thanks 👍

EDIT:

I don't see any harm in reverting to classic JSX runtime

@rektdeckard was there an issue by externalizing the react/jsx-runtime package? (I can see that you reverted it in ad5be55)

Tobias Fried · Answer 19 · Sat Apr 20 2024 00:20:47 GMT+0800 (China Standard Time)

@schardev it won't work (or at least will error and require an additional package to be installed) for users of react@16 and below. There are still tons of apps running 16.8, and I didn't want to hurt the dev experience there. Impact should really be minimal.

Tobias Fried · Answer 20 · Sun Apr 21 2024 06:08:14 GMT+0800 (China Standard Time)

Seems to have done the trick. I'm marking as resolved.

Holovko Ivan · Answer 21 · Mon Apr 22 2024 20:53:13 GMT+0800 (China Standard Time)

Thank you all very much

Omri · Answer 22 · Wed Apr 24 2024 18:22:36 GMT+0800 (China Standard Time)

Thanks @rektdeckard !