Closed prodkt closed 9 months ago
@prodkt it's next-auth package that is not fully compatible with latest nextjs 13 canary and throwing error while installing packages.
if you use --legacy-peer-deps flag while installing packages, like: npm i --legacy-peer-deps then it works.
Why don't we update the package to contain a non-breaking combination of packages?
Sorry about this – this should be fixed now! 🙏
Found in the pull requests. Simply over-riding the pull from vercel/platforms with janpio/platforms pnpm i && pnpm dev all works flawlessly. Something in this main branch causing all the pain. Just a heads up!