Skip to main content
Deno 2 is finally here 🎉️
Learn more
Deno 2.0 Release Candidate

The Final Touches: What’s New In v2.0.0-rc.10

Deno 2 is imminent, but if you want to try it right now, you can use the Deno 2.0 Release Candidate. Since we published the release candidate two weeks ago, we’ve made 10 patch updates, where we’ve fixed bugs and added features like a new permission flag for importing modules via HTTP. Read on the full list of changes.

To try out the release candidate, run these instructions in your terminal:

deno upgrade
deno upgrade rc

ℹ️ If you are using alternative distribution method like Homebrew, deno upgrade might not be available.

Follow (the shell or powershell installation instructions)[https://docs.deno.com/runtime/getting_started/installation/], then run the aforementioned commands.

🚨️ We’re actively seeking feedback 🚨️

This release candidate helps us identify issues prior to the final 2 release. If you encounter any issues or need extra guidance, please create an issue in GitHub or ask in our Discord’s #deno-2-help channel. Our team is actively monitoring both places and will help out as soon as we can.

What’s new in v2.0.0-rc.10

Hint for properlly installing npm package using Node API

Hint for properlly installing npm package using Node API

Hint for `window` global

Hint for `window` global

And a ton of bug fixes:

Acknowledgements

As always, we couldn’t build Deno without the help of our community! Whether by answering questions in our community Discord server or reporting bugs, we are incredibly grateful for your support. In particular, we’d like to thank the following people for their contributions to the Deno 2 release candidate: Ian Bull, Kenta Moriuchi, Mohammad Sulaiman, MujahedSafaa, Óscar Otero, Pig Fang, Simon Lecoq, Volker Schlecht, and Carles Escrig Royo.

What’s next

A lot of work has gone into Deno 2.0, which we plan to release NEXT WEEK. Thank you not only for your patience, but also for trying the release candidate and giving feedback in Discord or GitHub. We’ll continue to actively monitor both areas to ensure all major bugs are fixed.