• Val Town goes read-only
  • Val Town shuts down
  • Deno Deploy shuts down

Val Town and Deno Deploy are shutting down

Val Town's migration guide says code becomes read-only on December 10, 2026 and the service shuts down on January 10, 2027. Apps keep running until then. It points people to Node, Bun, or a provider runtime such as Cloudflare Workers or Vercel Functions.

Deno announced on October 9, 2026 that its team is joining Cloudflare, and that Deno Deploy “will continue operating for six months before shutting down”. That puts the end around April 2027; the post gives no exact day.

What breaks

Moving a Deno app to Node means replacing Deno.* calls, URL and jsr: imports, and deno.json tasks. Most of that is mechanical. Deno KV, Deno.cron and Fresh are not, because Node has no built-in equivalent.

I ran a Deno-to-Node codemod on 27 public Deno repos. npm install worked in all 27 afterwards and tsc came out clean in 7. Deno KV showed up in 7 of them and Fresh in 3; those always needed a person to decide.

How to fix it

Start with an inventory: the scanner flags Deploy config, KV, cron, Fresh and Val Town imports, and counts the Deno runtime calls. Let a tool do the mechanical rewrites, and decide early where KV data and scheduled jobs will live, since that choice shapes the rest of the move.

Check a repository for this

Deno Deploy config, Deno KV, Deno.cron, Fresh, Val Town imports, and how much of the code uses the Deno runtime.

Runs in your browser with 2 anonymous GitHub API requests. Example: 0f-0b/kv-relay@076195780df5.

The same rules run offline, with a --fix for the safe rewrites, in atokim4/deno-exit (MIT).

Sources

Dates and wording re-read on the official pages on . Vendors move dates; the official page wins.