After 63 alpha releases, Fresh 2.0 is graduating to beta. These betas are effectively release candidates — the architecture is now stable, and the last big change has landed.
That change is Vite integration. With the new plugin, Fresh can now optionally run as a Vite plugin, giving developers access to hot module reloading, the full Vite plugin ecosystem, and modern tooling for both client and server code — all while remaining fully usable without Vite.
import { defineConfig } from "vite"; import { fresh } from "@fresh/plugin-vite"; export default defineConfig({ plugins: [fresh()], });
The Fresh Vite plugin fully embraces Vite’s new Environment API to leverage the power of the plugin ecosystem for both server code and client code. For configuration details, see the Fresh docs.
With Vite providing access to the underlying module graph of each environment, we can now provide proper hot module reloading (“HMR”) support. Instead of reloading the page and losing all state, HMR allows UI elements to be swapped out whilst keeping the current page alive. Right now, this is scoped to island code and server-only changes will still reload the page.
A lot of care has been spent on making the production output as efficient as possible. In Fresh 2, routes are now loaded on demand — only the code needed to handle a request is loaded and executed. With the Vite plugin, we’re going a step further and will bundle the server code to reduce the number of files that need to be resolved and loaded.
As a result, starting a Fresh app in production is an order-of-magnitude faster. In our projects, we’ve seen boot times improve by 9–12×, depending on project size. We measure this from the moment the process starts until the app is ready to handle requests. That time usually includes resolving files, loading and instantiating modules, and other work done by the JavaScript engine.
Here are the boot numbers for the Fresh website:
86ms8msreact aliasingAliasing react, react-dom and other packages to preact/compat has always
been a bit tricky. This mapping often needed to be manually specified, and
required app code to use esm.sh instead of pulling dependencies directly from
npm. Having to be conscious about this was never an ideal setup.
With our Vite plugin, this will be taken care of for you. Install third party npm packages as usual and never run into aliasing issues again!
<Head> component is back!The beloved <Head>
component from Fresh 1.x is back again! It can be used from components to render
elements into the <head> portion of an HTML document.
export default function Page() { return ( <div> <Head> <title>About me</title> </Head> <h1>About me</h1> <p>some text about me...</p> </div> ); }
This feature isn’t tied to the Vite integration — you can already use it today in a Fresh 2 app. We had removed it in 1.x because the implementation was messy and hurt rendering performance. But with Fresh 2’s cleaner architecture and the chance to explore different approaches, we’ve landed on a much simpler, more efficient solution.
You can try out the Vite plugin today by running:
deno run -Ar jsr:@fresh/initThis will guide you through setting up a simple Fresh app that’s ready to be used with Vite. Let us know if you run into any issues!
Already using Fresh 1.x? The updated migration guide walks you through upgrading to Fresh 2.0 step by step.
Also check out the new guide on deploying to Cloudflare Workers, if that’s your preference.
🚨️ There have been major updates to Deno Deploy! 🚨️
- Improved Playgrounds with livestreaming logs, traces, and templates like Next.js
- Automatic and immediate observability and telemetry
- Simpler management for environment variables
and much more!
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。