-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting error "Package jsdom can't be external" after upgrading to Next.js 15 #295
Comments
Hey @birdzai ,
|
Yes, manually installing jsdom into node_modules fixed the error. I wasn't sure if you needed to be informed of having to perform this as something you cared about, so I thought I would raise it as an issue. Go ahead and close this issue if you think that's ok. |
Thanks @birdzai. We hadn't change much in this project since Next.js 14, so it's likely it's related to the latest Next.js update. But adding jsdom to external dependencies is a way to do it currently, though I understand that it's not very convenient #54 (comment) |
Thanks again for reporting @birdzai ! |
I thought I would test out upgrading a project to the newly release Next.js V15 and when running the app I'm getting this error in the server logs:
I of course followed the suggestion of manually installing jsdom into my node_modules folder, but I hadn't needed to do this before.
The text was updated successfully, but these errors were encountered: