UnhandledRejection Error: Cannot Find React Package #90

IvanNavin · 2024-04-02T15:34:55Z

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.

The text was updated successfully, but these errors were encountered:

omridevk · 2024-04-02T16:58:24Z

same here

omridevk · 2024-04-02T17:01:30Z

@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 · 2024-04-03T04:02:37Z

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 · 2024-04-03T04:06:32Z

@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.

IvanNavin · 2024-04-03T04:13:49Z

@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 · 2024-04-03T05:57:29Z

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

fanzypantz · 2024-04-03T08:50:39Z

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

derFBeste · 2024-04-03T19:40:06Z

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?

schardev · 2024-04-04T09:40:00Z

@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?

fanzypantz · 2024-04-08T07:53:35Z

@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",

schardev · 2024-04-08T09:07:23Z

@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",
}

fanzypantz · 2024-04-08T12:55:52Z

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" ]

ndom91 · 2024-04-13T17:46:33Z

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.

schardev · 2024-04-13T19:43:06Z

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

@ndom91 have you tried optimizePackageImports?

lcvbeek · 2024-04-18T12:56:08Z

@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.

rektdeckard · 2024-04-18T17:47:31Z

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.

rektdeckard · 2024-04-18T19:45:00Z

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

rektdeckard · 2024-04-18T20:37:00Z

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.

schardev · 2024-04-19T15:13:53Z

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)

rektdeckard · 2024-04-19T16:20:47Z

@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.

rektdeckard · 2024-04-20T22:08:14Z

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

IvanNavin · 2024-04-22T12:53:13Z

Thank you all very much

omridevk · 2024-04-24T10:22:36Z

Thanks @rektdeckard !

IvanNavin added the bug Something isn't working label Apr 2, 2024

IvanNavin assigned rektdeckard Apr 2, 2024

This was referenced Apr 18, 2024

Issues with Vitest/Vite phosphor-icons/homepage#477

Closed

Error when evaluating SSR module in remix-create@latest phosphor-icons/homepage#459

Closed

This was referenced Apr 18, 2024

Cannot find package on node 20 #88

Closed

Issue updating past 2.1.3 #94

Closed

rektdeckard closed this as completed Apr 20, 2024

rafaverde mentioned this issue Jul 23, 2024

[Snyk] Upgrade @phosphor-icons/react from 2.1.5 to 2.1.7 rafaverde/foodExplorer#1

Open

WesleyR10 mentioned this issue Aug 22, 2024

[Snyk] Upgrade @phosphor-icons/react from 2.0.15 to 2.1.7 WesleyR10/Food_Explorer_-Front-end#5

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

UnhandledRejection Error: Cannot Find React Package #90

UnhandledRejection Error: Cannot Find React Package #90

IvanNavin commented Apr 2, 2024

omridevk commented Apr 2, 2024

omridevk commented Apr 2, 2024

oscadev commented Apr 3, 2024

oscadev commented Apr 3, 2024 •

edited

Loading

IvanNavin commented Apr 3, 2024

xwu-alterdomus commented Apr 3, 2024 •

edited

Loading

fanzypantz commented Apr 3, 2024

derFBeste commented Apr 3, 2024

schardev commented Apr 4, 2024

fanzypantz commented Apr 8, 2024

schardev commented Apr 8, 2024

fanzypantz commented Apr 8, 2024 •

edited

Loading

ndom91 commented Apr 13, 2024 •

edited

Loading

schardev commented Apr 13, 2024

lcvbeek commented Apr 18, 2024

rektdeckard commented Apr 18, 2024

rektdeckard commented Apr 18, 2024

rektdeckard commented Apr 18, 2024

schardev commented Apr 19, 2024 •

edited

Loading

rektdeckard commented Apr 19, 2024

rektdeckard commented Apr 20, 2024

IvanNavin commented Apr 22, 2024

omridevk commented Apr 24, 2024

UnhandledRejection Error: Cannot Find React Package #90

UnhandledRejection Error: Cannot Find React Package #90

Comments

IvanNavin commented Apr 2, 2024

omridevk commented Apr 2, 2024

omridevk commented Apr 2, 2024

oscadev commented Apr 3, 2024

oscadev commented Apr 3, 2024 • edited Loading

IvanNavin commented Apr 3, 2024

xwu-alterdomus commented Apr 3, 2024 • edited Loading

fanzypantz commented Apr 3, 2024

derFBeste commented Apr 3, 2024

schardev commented Apr 4, 2024

fanzypantz commented Apr 8, 2024

schardev commented Apr 8, 2024

fanzypantz commented Apr 8, 2024 • edited Loading

ndom91 commented Apr 13, 2024 • edited Loading

schardev commented Apr 13, 2024

lcvbeek commented Apr 18, 2024

rektdeckard commented Apr 18, 2024

rektdeckard commented Apr 18, 2024

rektdeckard commented Apr 18, 2024

schardev commented Apr 19, 2024 • edited Loading

rektdeckard commented Apr 19, 2024

rektdeckard commented Apr 20, 2024

IvanNavin commented Apr 22, 2024

omridevk commented Apr 24, 2024

oscadev commented Apr 3, 2024 •

edited

Loading

xwu-alterdomus commented Apr 3, 2024 •

edited

Loading

fanzypantz commented Apr 8, 2024 •

edited

Loading

ndom91 commented Apr 13, 2024 •

edited

Loading

schardev commented Apr 19, 2024 •

edited

Loading