Skip to content

feat: remove react from next-auth, move to vue#1

Open
phoenix-ru wants to merge 23 commits into
v4from
feat/remove-react
Open

feat: remove react from next-auth, move to vue#1
phoenix-ru wants to merge 23 commits into
v4from
feat/remove-react

Conversation

@phoenix-ru

@phoenix-ru phoenix-ru commented Mar 13, 2026

Copy link
Copy Markdown
Member

☕️ Reasoning

This PR removes react, preact and next dependencies from the next-auth package, replacing the functionality with vue instead, for better integration with NuxtAuth.

⚠️ Updated nodemailer peer support to allow newer patched releases and avoid known audit findings from older 7.x versions. Consumers using advanced Nodemailer options should review the breaking changes in 8.0 and 9.0, especially auth error codes and stricter TLS validation for remote content/OAuth/proxy requests.

🧢 Checklist

  • Documentation
  • Tests
  • Ready to be merged

🎫 Affected issues

📌 Resources

@pkg-pr-new

pkg-pr-new Bot commented Apr 10, 2026

Copy link
Copy Markdown

Open in StackBlitz

npm i https://pkg.pr.new/sidebase/fork-authjs/@sidebase/fork-authjs@1
pnpm add https://pkg.pr.new/sidebase/fork-authjs/@sidebase/fork-authjs@1
yarn add https://pkg.pr.new/sidebase/fork-authjs/@sidebase/fork-authjs@1.tgz

commit: 1e654ad

phoenix-ru and others added 9 commits April 10, 2026 14:54
The inline email normalizer validated the address on the ASCII `@` before any
Unicode normalization. A character that is a homoglyph of `@` — e.g. U+FF20
FULLWIDTH COMMERCIAL AT — passed the single-`@` (atCount) check, but can be
canonicalized to an ASCII `@` by a downstream address parser (NFKC), splitting
the address into multiple recipients (CWE-180: validate before canonicalize).

Apply `String.prototype.normalize("NFKC")` before validation so any such
homoglyph becomes a real `@` and is rejected by the existing atCount check.
Behaviour on legitimate addresses is unchanged. Adds a regression test.

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
(cherry picked from commit 19d2feb)
`detectOrigin` returned the auto-detected forwarded host whenever
`VERCEL`/`AUTH_TRUST_HOST` was set, ignoring an explicitly configured
`NEXTAUTH_URL`. A configured canonical URL should always win; only fall
back to the forwarded host when no `NEXTAUTH_URL` is set.

Adds unit tests for detectOrigin precedence.

(cherry picked from commit 2a39465)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants