You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the issue is that @elysiajs/opentelemetry overrides the route set by @elysiajs/cors. It’s possible that @elysiajs/cors also overrides something in @elysiajs/opentelemetry, but I haven’t looked into it deeply yet.
What is the expected behavior?
To not override cors routes. Or add a warning for cases using @elysiajs/opentelemetry on the doc
What version of Elysia is running?
1.2.12
What platform is your computer?
Windows 10
What steps can reproduce the bug?
Use cors and opentelemtry together. If the cors is set first than openTelemetry it will give 404 when requesting for
OPTIONS
on prefligth.Here I fixed it just changing the order
I think the issue is that
@elysiajs/opentelemetry
overrides the route set by@elysiajs/cors
. It’s possible that@elysiajs/cors
also overrides something in@elysiajs/opentelemetry
, but I haven’t looked into it deeply yet.What is the expected behavior?
To not override cors routes. Or add a warning for cases using
@elysiajs/opentelemetry
on the docWhat do you see instead?
Error 404 on preflight
Additional information
I'm using:
Have you try removing the
node_modules
andbun.lockb
and try again yet?Yes
The text was updated successfully, but these errors were encountered: