-
-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request for Update to Deno 2.1 #466
Comments
Hello 😀 We've already started working on this, but we can't give you a timeline for when it will be done for now. I can tell you that we are making this a higher priority. |
Really looking forward to this update! |
Thanks for the update. Kudos |
Amazing to see that this is worked on. We are blocked by not being able to integrate with other local node-based packages due to this. Discovering after a days of work that following the tutorial installs a very different version of Deno (2.1) than the runtime is able to execute sucks. Everything works fine locally and everything fails during the deployment with errors that send you in circles regarding modules not found and paths... |
That's awesome @nyannyacha! Is there an unstable branch where we can help with early testing? |
Sorry, I want to say the work has not yet progressed sufficiently enough for early testing. Work is in progress on the branch that exists in my fork. I can tell you that the work has not progressed far enough to pass the compilation. This work involves a major refactoring of the repository, so there is a lot to review. |
It has been over a month since the release of Deno 2.1, which is now the latest stable version. Could you please provide an update on when we can expect the Supabase Edge Runtime to be updated to this version?
The current version used in Edge Runtime seems to be lagging behind, and adopting the latest Deno version would help in resolving some dependency issues and leveraging new features.
Any information or timeline on this update would be greatly appreciated. Thank you!
The text was updated successfully, but these errors were encountered: