Vite+ の異常なタスクランナー: vite-task は如何にしてキャッシュの手動依存管理をなくしたか
原題『Vite+の異常なタスクランナー または vite-task は如何にしてキャッシュの手動依存管理を止めてファイルアクセスを自動捕捉するようになったか』[1] 先日、ついに Vite+ の alpha 版がリリースされました。oxc エコシステムの全面バックアップを受けた高速なネイティブ実装ツールチェーンが揃い踏みしており、開発コミュニティも沸き立っています。 私も仕事で扱っているプロジェクトを手元で Vite+ に置き換えてみたのですが、 vp (ヴイピー) 鬼はえええ！このまま遅いやつら全部 Vite+ に置き換えていこうぜ！ という気持ちになりました。 そんな Vite+ ですが、Rolldown や oxlint, oxfmt に紛れて、かなり面白いことをしているツールが入っています。vite-task です。 vite-task: キャッシュの手動依存管理からの解放 vit
Announcing Vite+ Alpha
We’re excited to open-source Vite+ under the MIT license. Vite+ is a new unified toolchain and entry point to web application development that manages your runtime, package manager, and frontend toolchain. Give it a try today! What is Vite+? Vite+ combines Vite, Vitest, Oxlint, Oxfmt, Rolldown, and tsdown into a single, unified web development toolchain for developing, testing, linting, formatti
Vite 8.0 is out!
Vite 8.0 is out! March 12, 2026 We're thrilled to announce the stable release of Vite 8! When Vite first launched, we made a pragmatic bet on two bundlers: esbuild for speed during development, and Rollup for optimized production builds. That bet served us well for years. We're very grateful to the Rollup and esbuild maintainers. Vite wouldn't have succeeded without them. Today, it resolves into
Announcing Vitest 4.1
Vitest 4.1 is out! March 12, 2026 The next Vitest minor is here Today, we are thrilled to announce Vitest 4.1 packed with new exciting features! Quick links: DocsTranslations: 简体中文GitHub ChangelogIf you've not used Vitest before, we suggest reading the Getting Started and Features guides first. We extend our gratitude to the over 713 contributors to Vitest Core and to the maintainers and contrib
Astro 6.0 | Astro
Astro 6 is here! Astro 6 introduces a broad set of new capabilities, including a built-in Fonts API, Content Security Policy API, and support for Live Content Collections that work with your externally-hosted content through the unified Astro content layer. Alongside these new features, we also completed a major refactor of the Astro dev server and much of the build pipeline. Powered by Vite’s new
How we rebuilt Next.js with AI in one week
*This post was updated at 12:35 pm PT to fix a typo in the build time benchmarks. Last week, one engineer and an AI model rebuilt the most popular front-end framework from scratch. The result, vinext (pronounced "vee-next"), is a drop-in replacement for Next.js, built on Vite, that deploys to Cloudflare Workers with a single command. In early benchmarks, it builds production apps up to 4x faster a
Vite 8 Beta: The Rolldown-powered Vite
Vite 8 Beta: The Rolldown-powered Vite December 3, 2025 TL;DR: The first beta of Vite 8, powered by Rolldown, is now available. Vite 8 ships significantly faster production builds and unlocks future improvement possibilities. You can try the new release by upgrading vite to version 8.0.0-beta.0 and reading the migration guide. We're excited to release the first beta of Vite 8. This release unifi
Announcing Vitest 4.0
Vitest 4.0 is out! October 22, 2025 The next Vitest major is here Today, we are thrilled to announce Vitest 4! Quick links: DocsTranslations: 简体中文Migration GuideGitHub ChangelogIf you've not used Vitest before, we suggest reading the Getting Started and Features guides first. We extend our gratitude to the over 640 contributors to Vitest Core and to the maintainers and contributors of Vitest int
Announcing Vite+
Announcing Vite+: a unified toolchain for JavaScript Last week, we unveiled Vite+ at the first-ever in-person ViteConf in Amsterdam. In this post, we’ll share more details about what it is and the motivation behind it. What is Vite+? Vite+ is a command-line developer tool you can install from npm, just like Vite itself. It’s a drop-in upgrade to Vite with additional features. Imagine that, in
Fresh 2.0 Graduates to Beta, Adds Vite Support | Deno
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. Hot module reloading in islands 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
vitestではbeforeEachを使わない
はじめにlink 最近DBありのテストを記述していた際に、実はvitestではbeforeEachは必要ないのではないか、という考えに至ったのでその理由と設計についてまとめてみる。 下記のリポジトリで実験する https://github.com/koh110/vitest-beforeeach テストでbeforeEachが欲しくなるシーンlink テストを記述する際にbeforeEachが欲しくなるシーンは主に以下の2点ではないかと考えている。 mockの設定/reset seedsの投入 このうち、前者mockの設定/resetはbeforeEachではなくbeforeAll or すべての個別テストごとに設定すべきなのではと考えている。 これは自分がテスト単体での移植性を重視している（テスト単体をコピペしてもなるべくそのまま動かせる）ので、beforeEachでやってしまうとあるテ
Vite 7.0 is out!
Vite 7.0 is out! June 24, 2025 We're happy to share the release of Vite 7! It has been 5 years since Evan You sent the first commit to the Vite repo, and nobody could have predicted how much the frontend ecosystem would change since then. Most modern frontend frameworks and tools are now working together, building on top of Vite's shared infrastructure. And they can innovate at a faster pace by
Announcing Rolldown-Vite
TL;DR: Try out the Rolldown-powered Vite today by using the rolldown-vite package instead of the default vite package. It is a drop-in replacement, as Rolldown will become the default bundler for Vite in the future. Switching should reduce your build time, especially for larger projects. Reach out to discover production use cases! Over the last year, we've been working on Rolldown, a Rust-based ne
Rolldown | Rust bundler for JavaScript
Why do we still need bundlers? Skipping the build step is impractical With the general availability of native ES modules and HTTP/2 in modern browsers, some developers are advocating for an unbundled approach for shipping web applications, even in production. While this approach works for smaller applications, in our opinion bundling is still very much necessary if you are shipping anything non-
Announcing Vitest 3.2
Vitest 3.2 is out! June 2, 2025 Vitest 3.2 focuses on improvements to Browser Mode and TypeScript support. This release also includes some new useful methods, config options and deprecates the workspace config in favour of projects. workspace is Deprecated In an effort to simplify the configuration, the team decided to deprecate the separate vitest.workspace file and recommend using only the pro
Any websites were able to send any requests to the development server and read the response
Upgrade Path Users that does not match either of the following conditions should be able to upgrade to a newer version of Vite that fixes the vulnerability without any additional configuration. Using the backend integration feature Using a reverse proxy in front of Vite Accessing the development server via a domain other than localhost or *.localhost Using a plugin / framework that connects to the
@lazarv/react-server
Execute React components across server, client, workers, and edge environments using a single runtime — with React Server Components, streaming, and deployment built in. The Idea React as a RuntimeReact runs outside the browser. Components are executable units — they run on the server, in workers, and at the edge. The runtime decides where and how each component executes. There is no runtime bound
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Fresh 2.3: Zero JS by default, View Transitions, and Temporal support | Deno
GitHub - almadoro/react-just: React Server Components without a framework. Powered by Vite
Release v3.0.5 · vitest-dev/vitest