React 19 support

[tobiaslins]

Allow react 19 rc as peer dependency

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
analytics-nextjs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 25, 2024 8:03am
analytics-remix	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 25, 2024 8:03am

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/eslint-config-next@15.0.1	Transitive: environment, eval, filesystem, unsafe	+226	23.6 MB	timer, timneutkens, vercel-release-bot
npm/next@15.0.1	environment, filesystem, network, shell, unsafe	+62	115 MB	vercel-release-bot
npm/react-dom@19.0.0-rc-69d4b800-20241021	environment	+1	6.45 MB	fb, gnoff, react-bot, ...2 more
npm/react@19.0.0-rc-69d4b800-20241021	environment	0	239 kB	react-bot
npm/types-react-dom@19.0.0-rc.1	None	0	17.7 kB	eps1lon
npm/types-react@19.0.0-rc.1	None	+1	1.57 MB	eps1lon

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Possible typosquat attack	npm/types-react-dom@19.0.0-rc.1	Did you mean: **@types~~-~~/**react-dom	apps/nextjs-15/package.json pnpm-lock.yaml	⚠︎

View full report↗︎

Next steps

What is a typosquat?

Package name is similar to other popular packages and may not be the package you want.

Use care when consuming similarly named packages and ensure that you did not intend to consume a different package. Malicious packages often publish using similar names as existing popular packages.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/types-react-dom@19.0.0-rc.1

[tobiaslins]

Fix #148

[feugy]

Thanks for the change.

Successfully tested locally.