search

denoland / deploy_feedback

For reporting issues with Deno Deploy
https://deno.com/deploy
74 stars 5 forks source link

Is it possible to test locally the "tweaked Deno runtime" used on denodeploy? #709

Open esroyo opened 2 weeks ago

esroyo commented 2 weeks ago

What problem are you trying to solve?

I have an application that has been running on Deno locally (from 1.43.x to current 1.46.x), but has stopped working on denodeploy (It was working back in June).

The denodeploy logs are not enough to debug the issue, as this is a complex application involving node and npm packages. I get a user-land error, but is not obvious why it triggers.

Describe the solution you'd like

I'm wondering if there is a way to run the exact "tweaked Deno runtime" locally. It is very difficult to debug complex issues just by logging.

Describe alternatives you've considered

I have picked the application files related to the issue, and uploaded them to a repo: https://github.com/esroyo/deno-vs-denodeploy/tree/main

Still that is not a trivial code example. Thus I'm not asking to inspect it. But Ideally there should be a way to debug/profile the application with the exact runtime version that will run it on the edge.

Thanks for you time.

igorbdl commented 1 week ago

Thank you for reaching out on this. Currently, it is not possible to run the Deno Deploy runtime locally. This is something we are working to improve on and we are currently experimenting different approaches on how to tackle this with the intent to enable this capability.

esroyo commented 1 week ago

@igorbdl It is great to know that you have this in mind. Any way to follow the progress on that capability? Thanks so much :pray: