Fresh 2.3: Zero JS by default, View Transitions, and Temporal support Here is a factual summary of the article: Fresh 2.3, a web framework for Deno, has been released with over 100 commits from 20 contributors. The update delivers on its "zero JavaScript by default" promise by ensuring pages with no interactive islands or partials ship without any client-side scripts, and it adds built-in support for the View Transitions API and WebSockets. Additionally, the release includes significant Vite integration improvements, such as dropping Babel transforms for better npm package compatibility and fixing various caching and development server issues. Fresh 2.3: Zero JS by default, View Transitions, and Temporal support Fresh 2.3 is out, with over 100 commits from 20 contributors. This release makes the “zero JavaScript by default” promise actually hold, adds View Transitions support, pre-compiles middleware chains, and rounds out a long list of Vite integration fixes. You can start a new project with: deno create @fresh/init or update an existing one with: deno run -Ar jsr:@fresh/update Zero JavaScript by default Fresh has always said that pages ship no JavaScript unless they need to, but that wasn’t strictly true. Every page ended up with a small client-entry script to bootstrap the island reviver and partials engine, even when neither was used. Thanks to Jeroen Akkerman in 3696, Fresh now checks whether the page actually uses islands or partials f-client-nav before injecting anything. If it doesn’t, the page ships with no