Error [ERR_PACKAGE_PATH_NOT_EXPORTED] react

[gkielwasser]

Question 💬

Hi,

I'm using the beta.2 version.

My build give me the following error Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './react' is not defined by "exports" in my-project\node_modules\next-auth\package.json.
The error happen as soon as I encapsulate my app with the SessionProvider provider.

I'm using the following to wrap my app:

import { SessionProvider } from "next-auth/react"

<SessionProvider session={pageProps.session}>
      [...]
 </SessionProvider>     

Also, I'm not sure what usefull informations I could share about this error.

Thanks for help!

How to reproduce ☕️

Here is my nextauth dependency: "next-auth": "4.0.0-beta.2"

Contributing 🙌🏽

No, I am afraid I cannot help regarding this

[balazsorban44]

have a reproduction?

[gkielwasser]

I can confirm nothing related to a wrong package of next-auth. Tripe check (maybe more) the package version number in node_modules :)
Not keen about those automatic fixes, I have checked my diff on yarn.lock. I have seen lots of @babel/* packages have been updated.
Also the real reason might be the updates of those packages in my environnment during the installation of Next11 version.
new implementation of the Babel loader for webpack
Hope that could help someone

[Tammerabi]

Just thought I'd chime in and say I'm having this issue as well.
"next": "^9.5.3",
"next-auth": "4.0.0-beta.2",
Tried with both node v13.14.0 and v16.9.0

Edit: seems like upgrading next to 10 fixed it

[balazsorban44]

Again, upgrading to next 10 has no effect for this whatsoever. running npm install again probably reinstalled next-auth as well, fixing your problem.

[gkielwasser]

I'm not sure what you mean by reinstalled next-auth ?

[balazsorban44]

The point is that NextAuth does not depend on any Next 10 specific features, so the reason for the error being gone must be something else than downgrading next

[gkielwasser]

So as an answer I would say, double check those dependencies typescript + beta.2

[saevarb]

Just to help anyone else passing by: I ran into this error because I hadn't seen the v4 migration docs about there being a bad publish, so I was trying to use beta4. Switching to beta2 fixed this issue.

[balazsorban44]

4.0.0-beta.4 works as well. 😉 If you are having trouble, read this: https://next-auth.js.org/getting-started/upgrade-v4#verify-the-correct-version

[saevarb]

4.0.0-beta.4 works as well. wink If you are having trouble, read this: https://next-auth.js.org/getting-started/upgrade-v4#verify-the-correct-version

Thanks for the reply! From the docs, it sounds a lot like beta4 isn't valid.

After trying to install beta2 because I was having the package export problem, that problem went away. However, instead, the azure AD provider was broken and I wasted several hours on trying to debug that.. until I tried installing the beta4 again. Doing that un-broke the azure AD provider and let me login again, but no matter what I do, when I deploy the application to Azure App Services with beta4, I get the module export error.

The worst part is that I'm simply not able to reproduce it locally. It only happens when I try to deploy the application. Running the build artifact in a new folder locally doesn't exhibit this issue, and neither does building it and running it isolated in a docker container.

My conclusion is that there must simply be something funky going on with whatever azure app service is doing. This wouldn't be the first thing, either, since I'm already using a hack like start:prod": "node_modules/next/dist/bin/next start" in my package.json file to start it on azure because it simply won't work otherwise.

[balazsorban44]

I'm sorry to hear that. Although I'm curious which part of the docs implies that beta.4 wouldn't work? The only broken release is 4.0.0 and installing it will even warn you being deprecated. (I did try to remove it from npm, but I wasn't allowed to)

[saevarb]

version to be exactly 4.0.0-beta.1 (or beta.2 etc.

I suppose I must have missed the etc here - my bad!

Also, I probably should have clarified that my module export error is about the azure-ad provider, not react.

I also just tried updating the package.json to add the following line to exports:

...
"./providers/*": "./providers/*.js",
"./providers/azure-ad": "./providers/azure-ad.js" // <-
...

And this does indeed seem to fix the module export error, and I'm finally able to start a sign-in process. It's not the end of my troubles, however, as now I am getting a CLIENT_FETCH_ERROR:

2021-10-12T12:58:44.008070842Z error: CLIENT_FETCH_ERROR {
2021-10-12T12:58:44.008128343Z   error: FetchError: invalid json response body at https://<website>/<basePath>/api/auth/providers reason: Unexpected token  in JSON at position 0
2021-10-12T12:58:44.008136744Z       at /home/site/wwwroot/node_modules/node-fetch/lib/index.js:272:32
2021-10-12T12:58:44.008141244Z       at processTicksAndRejections (internal/process/task_queues.js:97:5)
2021-10-12T12:58:44.008145744Z       at async fetchData (/home/site/wwwroot/node_modules/next-auth/lib/client.js:22:18) {
2021-10-12T12:58:44.008150044Z     type: 'invalid-json'
2021-10-12T12:58:44.008154244Z   },
2021-10-12T12:58:44.008158344Z   path: 'providers'
2021-10-12T12:58:44.008162544Z }

The only problem with this error is that if I follow the URL it complains about, it gives me totally valid JSON.

I have given up on this problem for now and my conclusion regarding azure is the same, and I've talked to my devops people to let me deploy docker containers instead, where I have 100% control of the environment.

I know this is all mostly irrelevant info but maybe someone else runs into a similar issue.