Mick Lawitzke
                                            Mick Lawitzke
                                        
                                    `useRuntimeConfig` does not inherits env variables without passing `env` param in cloudflare workers
I am using nitropack 2.9.6 and useRuntimeConfig() works fine without passing explicit `(event)`. I think this one can be closed, as @oritwoen also reported it works fine? However there is...
`useRuntimeConfig` does not inherits env variables without passing `env` param in cloudflare workers
Unfortunately crypto is a VERY bad idea on Cloudflare workers, at least with JS. I already got into that topic. BUT there is a solution, which is making another worker...
Hi @pi0 @danielroe , I digged deeper into this and found a critical bug with route rules not beeing applied. Maybe a problem with https://github.com/unjs/radix3? The following rule works for...
It gets even more weird! The route rules are applied if there is a GET route, e.g. `contact.ts` and `contact.post.ts` BUT if the GET route just throws an error it...
This is definitely a critical bug and an annoying one as well. Maybe it will be fixed with v3? @pi0 But in any case it needs to be fixed for...
One thing is CORS but this issue actually turned out to a critical bug. Maybe it was not clear enough in the end but it took me some time to...
But why does it work when adding the get route? Like for PATCH /products it works in my example. Sorry if I miss something. ``` /products.ts /products.patch.ts /items.patch.ts -> Route...
I see, thanks for all the explanations!
@pi0 Is there any update on this issue? I didnt find anything about cors in the docs yet. Is the only workaround to add empty route handlers atm or did...
**Another issue** with this is that non-existent routes return cors error instead of 404.