Federico Minaya

Vercel now supports the `edge` runtime for remix in production I deployed a short example using `@vercel/og` to https://vercel-og-remix-fedeya.vercel.app here is the repo: https://github.com/fedeya/vercel-og-remix. The only problem i found right...

Hi @Jaydeep189 you are using the edge runtime?

@Jaydeep189 i released a new version (1.5.0) with it the `signUpHandler` can be used on the edge and with the new route handlers (app dir), can you try again with...

Ok this is very strange, I cloned the repo, added the environment variables and started the development server and all works fine. I also tried with Next.js 12.2.5 and it...

the unique difference between your own fetch request and the one made by `signUp` is the charset in the `Content-Type`. I added it in the latest version, can you check...

Hi, this seems like a problem with node gyp on your machine, this library uses argon2 for passwords and token hashing and argon2 are C++ bindings, can you try installing...

It seems this is a remix v2 bug. If this doesn't improve in future versions of the remix, it may be necessary to think about somewhere else to put the...

Hi @lewsmith @justinhandley to fix this i released a new version (3.1.0) with a new api to just generate the sitemap and robots in each route, i marked it as...

this not be possible because in the remix code each server platform package send the app load context in a `handleLoader` or `handleAction` never sended to the `entry.server.ts`

Looks like the `AppLoadContext` is being sent to `handleRequest` in the `entry.server` as the last argument in the new express starter ```ts export default function handleRequest( request: Request, responseStatusCode: number,...