😢

🤣🤣🤣

Thank you, will try

Do you have some code to share? I never tried aws lambda

Unfortunately, we use ffmpeg to decode and encode audio and video. So I need to externalize services and use plain nodejs. With vercel fluid a lot of issue disappeared, but again we can't use ffmpeg there

So what do we need? A good tutorial that handles real cases?

Yes this is another issue and the workaround is to add a script... but nuxt/nitro is too awesome to use workaround everywhere ahah

Yes even pm2 is different

It happens also with node, I will try to publish a minimum reproducible once I get this again

Yes and as I use 3 deployments (vercel, cloudflare and node) it's very stressfull

Sometimes I also discovered issue when using import, on cloudflare (as always sometimes)
import { fn } from '@/server/utils'
import { fn } from '~/server/utils'
import { fn } from './utils'

cause differents scenario. and you need to debug your imports according the provider

About the auto-import, usually you create functions in defineEventHandler, so in locally you don't need to import functions that are in /server/utils. But if you deploy it on cloudflare then you start to receive errors because the workers don't know where the function is stored

It's very hard to create a reproducible, but once I'll get some issue I will try to fork the repo and I will share it with you. Again I'm not the only one that complain these issues

Thanks, I miss you on X :)

The issue are always related to the backend (nitro in that case)

I use several deployments, vercel, cloudflare, and node.. I spoke with a few devs they're have same issue. It's not easy to reproduce because happen randomly. Sometimes you need to deactivate auto imports, sometime envs are not considered, sometime you need to use useEvent and sometimes doesn't work