{"slug": "fresh-2-3-zero-js-by-default-view-transitions-and-temporal-support", "title": "Fresh 2.3: Zero JS by default, View Transitions, and Temporal support", "summary": "Here is a factual summary of the article:\n\nFresh 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.", "body_md": "Fresh 2.3: Zero JS by default, View Transitions, and Temporal support\nFresh 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.\nYou can start a new project with:\ndeno create @fresh/init\nor update an existing one with:\ndeno run -Ar jsr:@fresh/update\nZero JavaScript by default\nFresh has always said that pages ship no JavaScript unless they need to, but\nthat wasn’t strictly true. Every page ended up with a small client-entry\nscript to bootstrap the island reviver and partials engine, even when neither\nwas used.\nThanks to Jeroen Akkerman in\n#3696, Fresh now checks whether\nthe page actually uses islands or partials (f-client-nav\n) before injecting\nanything. If it doesn’t, the page ships with no