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

Thank you! Small note, we are still very much interested, but our priority is on making the core more stable and finishing up the docs migration (https://next-auth.js.org and https://authjs.dev have a lot of shared content right now).

Once that's done, we will have more time to look into new frameworks again! 💚

In the meantime, I was wondering about your opinion on this comment by @sergiodxa: #6246 (reply in thread), considering that there is https://remix.run/docs/en/v1/utils/sessions

Thank you! Small note, we are still very much interested, but our priority is on making the core more stable and finishing up the docs migration (https://next-auth.js.org and https://authjs.dev have a lot of shared content right now).

Once that's done, we will have more time to look into new frameworks again! 💚

In the meantime, I was wondering about your opinion on this comment by @sergiodxa: #6246 (reply in thread), considering that there is https://remix.run/docs/en/v1/utils/sessions

No problem, it seems silly to merge it when that remix bug means you have to use a patch and for some reason they still haven't merged in the fix.

But yes I agree it would be easier to work with remix if it didn't return a response object and just the info you needed to create the response. Not even mainly to use the built in remix session storage methods, although that could be especially nice for things like cloudflare. But mainly after playing with it a lot and the best way to integrate it, is as I lay out in the README, is using a fetcher.Form and you are basically ignoring the html of the response but of course you need the set-cookie.

This ends up working fine for most things as if it succeeds you can easily show they are signed in. But for errors you can tell it encountered an error via the response code but would need to parse the html response to see if it's something you want to tell the user like if the email already exists in the database.

Also it becomes a pain for strategies that succeed but don't log the user in like with email magic links.

@acoreyj just a ping reminder. Is it possible to finish the work you have started here? Do you have an y plans for that?

@acoreyj now that Remix moved to Vite, is this more feasible to become a reality?

@voltuer @Guria

I can make sure this is working with the latest Remix. Although a bit confused on what Remix is to become as it is merging with React Router so not clear if this makes sense in that context

@voltuer @Guria

I can make sure this is working with the latest Remix. Although a bit confused on what Remix is to become as it is merging with React Router so not clear if this makes sense in that context

Yeah it'd be great if you could double check this against the latest versions of Remix!

The way I see it, I can't imagine the framework will disappear in any sense. Shopify bought them as replacement for their homegrown framework and as a competitor to Vercel/next, netlify/gatsby, etc.

@acoreyj is attempting to deploy a commit to the authjs Team on Vercel.

A member of the Team first needs to authorize it.

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

🚮 Removed packages: npm/@actions/core@1.10.1), npm/@ariakit/react@0.4.5), npm/@aws-sdk/client-dynamodb@3.499.0), npm/@aws-sdk/lib-dynamodb@3.499.0), npm/@azure/data-tables@13.2.2), npm/@balazsorban/monorepo-release@0.5.1), npm/@builder.io/qwik-city@1.5.5), npm/@builder.io/qwik@1.5.5), npm/@builder.io/qwik@1.7.3), npm/@cloudflare/workers-types@4.20240117.0), npm/@eslint/compat@1.1.1), npm/@eslint/js@9.9.1), npm/@graphql-codegen/cli@5.0.0), npm/@graphql-codegen/client-preset@4.1.0), npm/@graphql-typed-document-node/core@3.2.0), npm/@inkeep/widgets@0.2.272), npm/@libsql/client@0.6.0), npm/@mikro-orm/core@5.9.7), npm/@mikro-orm/sqlite@5.9.7), npm/@miniflare/d1@2.14.2)

View full report↗︎

You shouldn't touch the package.json version manually. Just set it to 0.0.1, for example, for the first release. And then once released, subsequent updates are automatically bumped by our CI tooling

@voltuer @Guria
I can make sure this is working with the latest Remix. Although a bit confused on what Remix is to become as it is merging with React Router so not clear if this makes sense in that context

Yeah it'd be great if you could double check this against the latest versions of Remix!

The way I see it, I can't imagine the framework will disappear in any sense. Shopify bought them as replacement for their homegrown framework and as a competitor to Vercel/next, netlify/gatsby, etc.

@ndom91 thanks but i decided to use Next, but if I ever try Remix again in the future I'll try it out

Maybe the name should change to '@auth/react-router' because Remix will be merged into the upcoming React Router 7

any plan to get this merged?