Adds an extension for NextAuth.js

[simnalamburt]

What's the problem this PR addresses?
NextAuth.js is not usable with Yarn 2 PnP due to wrong dependency. I tried to patch NextAuth.js first but they rejected it. So I'm fixing Next.js and Yarn instead. I already have fixed the Next.js side and this is the remaining piece.

How did you fix it?
Added an extension

Checklist

• I have read the Contributing Guide.
• I have set the packages that need to be released for my changes to be effective.
• I will check that all automated PR checks pass before the PR gets reviewed.

References

• Support Yarn 2 PnP nextauthjs/next-auth#1034
• Prevent unpredictable dependency hosting by explicitly resolve module path on webpack.ProvidePlugin vercel/next.js#20971

[merceyz]

As we mentioned in the linked issues it was a problem with how Next.js provided the polyfill for process so adding it as a dependency to next-auth isn't the correct fix, do you have a repro that shows that it's still needed so it can be fixed in Next.js?

I tested with https://github.com/nextauthjs/next-auth-example but can't reproduce it

[simnalamburt]

As I stated in vercel/next.js#20971 (comment), it's not yet. It fails when you use it with Webpack 5.

How to reproduce the issue:

git clone https://github.com/simnalamburt/next-auth-example.git
cd next-auth-example
yarn
yarn dev

References

• https://github.com/simnalamburt/next-auth-example
• nextauthjs/next-auth-example@main...simnalamburt:main

[JakubKoralewski]

I can't repro it either anymore. I just checked with my project in which I originally found the problem where a week ago I needed this to fix the Module not found: can't resolve 'process' error:

packageExtensions:
  next-auth@*:
    dependencies:
      process: "^0.11.10"

but now I removed it, tested it (first it failed), but after updating next-auth to "next-auth": "^3.3.0", from "next-auth": "^3.2.0-canary.35", I get an error different than Module not found: can't resolve 'process'. I think this is fixed! @simnalamburt, could you check again with latest next-auth?

[simnalamburt]

The error reproduction above is using the latest version of next and next-auth.

Reference

• https://github.com/simnalamburt/next-auth-example/blob/c384f8ae906227bdbb11bed92bc4774a0ceb1899/yarn.lock#L2222

[merceyz]

It fails when you use it with Webpack 5.

Yeah that makes it a missing polyfill in Next.js, see vercel/next.js#22247 and https://github.com/vercel/next.js/blob/fea5c18132146976913f4148210b74d6d9b1ef8c/packages/next/build/webpack-config.ts#L394-L398

[simnalamburt]

Does adding process:require.resolve('process') to the polyfill list actually solves this issue? It didn't worked for me.

Reference

• Polyfill for process not included with Webpack 5 and Yarn 2 PnP vercel/next.js#22247 (comment)
• simnalamburt/next-auth-example@c128495

[merceyz]

You need to use require.resolve('process/') otherwise it will just return process again

[simnalamburt]

Currently there's no known solution or workaround of vercel/next.js#22247, shall we reopen this PR?