Meta tags:
description=Next Generation Frontend Tooling;

Headings (most frequently used words):

comparisons, with, other, no, bundler, solutions, snowpack, wmr, web, dev, server,

Text of the page (most frequently used words):
vite (22), the (18), and (16), for (13), that (10), dev (10), #server (9), support (9), more (8), rollup (8), build (6), pre (6), bundling (6), snowpack (6), web (5), wmr (5), preact (5), with (5), plugin (5), vue (5), dependency (5), different (5), plugins (5), this (4), terms (4), features (4), provides (4), api (4), from (3), integration (3), provide (3), other (3), scope (3), not (3), official (3), framework (3), production (3), based (3), inspired (3), projects (3), are (3), using (3), experience (3), have (3), esbuild (3), optimizers (3), bundler (3), also (3), comparisons (3), config (3), guide (3), migration (2), backend (2), page (2), level (2), project (2), benefit (2), users (2), bit (2), setup (2), was (2), designed (2), integrated (2), such (2), rendering (2), you (2), fine (2), similar (2), tooling (2), now (2), still (2), first (2), class (2), single (2), file (2), template (2), asset (2), reference (2), hmr (2), example (2), perform (2), style (2), automatic (2), css (2), monorepo (2), yarn (2), legacy (2), bundle (2), mode (2), output (2), into (2), can (2), between (2), optimizer (2), two (2), solutions (2), static (2), github (2), 日本語 (2), 简体中文 (2), english (2), languages (2), changelog (2), compat (2), community (2), awesome (2), discord (2), chat (2), twitter (2), links (2), version (2), suggest, changes, overall, opinionated, higher, tool, aims, out, box, workflow, said, umbrella, contains, many, excellent, tools, may, well, lower, does, integrations, requires, manually, setting, configuration, previously, great, koa, mainly, offers, closer, meta, same, emphasis, compact, size, itself, likely, going, offer, tuned, team, feature, set, interface, initially, created, serve, future, foundation, although, fully, agnostic, component, format, covering, all, advanced, resolving, custom, blocks, addition, grained, sfcs, updating, sfc, will, hot, updates, without, resetting, its, state, module, script, refined, sass, less, including, improved, resolution, aliases, npm, dependencies, rebasing, inlined, files, url, import, processor, handle, setups, successfully, pnpm, monorepos, uses, instead, results, significant, performance, improvements, cold, start, invalidations, faster, generates, dual, modern, bundles, auto, delivers, right, browser, optimized, async, chunk, loading, code, splitting, library, multi, due, process, supports, wide, range, currently, available, opts, deeper, one, order, streamlined, allows, works, both, universal, default, unbundled, transforms, each, separate, built, modules, which, then, fed, actual, choose, end, bundlers, fit, specific, needs, webpack, even, downside, fragmented, unstable, officially, maintained, configurations, native, esm, very, aside, implementation, details, share, lot, technical, advantages, over, traditional, some, main, differences, esinstall, sponsors, javascript, apis, side, ssr, env, variables, modes, deploying, site, building, handling, getting, started, why, documentation, covers, latest, see, https, old,

Text of the page (random words):
comparisons with other no bundler solutions vite this documentation covers vite 2 old version for the latest version see https vite dev vite guide config plugins links twitter discord chat awesome vite dev community rollup plugins compat changelog languages english 简体中文 日本語 github guide config plugins links twitter discord chat awesome vite dev community rollup plugins compat changelog languages english 简体中文 日本語 github guide why vite getting started features using plugins dependency pre bundling static asset handling building for production deploying a static site env variables and modes server side rendering ssr backend integration comparisons snowpack wmr web dev server migration from v1 apis plugin api hmr api javascript api config reference sponsors comparisons with other no bundler solutions snowpack snowpack is also a no bundle native esm dev server that is very similar in scope to vite aside from different implementation details the two projects share a lot in terms of technical advantages over traditional tooling vite s dependency pre bundling is also inspired by snowpack v1 now esinstall some of the main differences between the two projects are production build snowpack s default build output is unbundled it transforms each file into separate built modules which can then be fed into different optimizers that perform the actual bundling the benefit of this is that you can choose between different end bundlers to fit specific needs e g webpack rollup or even esbuild the downside is that it s a bit of a fragmented experience for example the esbuild optimizer is still unstable the rollup optimizer is not officially maintained and different optimizers have different output and configurations vite opts to have a deeper integration with one single bundler rollup in order to provide a more streamlined experience it also allows vite to support a universal plugin api that works for both dev and build due to a more integrated build process vite supports a wide range of features that are currently not available in snowpack build optimizers multi page support library mode automatic css code splitting optimized async chunk loading official legacy mode plugin that generates dual modern legacy bundles and auto delivers the right bundle based on browser support faster dependency pre bundling vite uses esbuild instead of rollup for dependency pre bundling this results in significant performance improvements in terms of cold server start and re bundling on dependency invalidations monorepo support vite is designed to handle monorepo setups and we have users successfully using it with yarn yarn 2 and pnpm based monorepos css pre processor support vite provides more refined support for sass and less including improved import resolution aliases and npm dependencies and automatic url rebasing for inlined files first class vue support vite was initially created to serve as the future foundation of vue js tooling although as of 2 0 vite is now fully framework agnostic the official vue plugin still provides first class support for vue s single file component format covering all advanced features such as template asset reference resolving script setup style module custom blocks and more in addition vite provides fine grained hmr for vue sfcs for example updating the template or style of an sfc will perform hot updates without resetting its state wmr wmr by the preact team provides a similar feature set and vite 2 0 s support for rollup s plugin interface is inspired by it wmr is mainly designed for preact projects and offers more integrated features such as pre rendering in terms of scope it s closer to a preact meta framework with the same emphasis on compact size as preact itself if you are using preact wmr is likely going to offer a more fine tuned experience web dev server web dev server previously es dev server is a great project and vite 1 0 s koa based server setup was inspired by it web dev server is a bit lower level in terms of scope it does not provide official framework integrations and requires manually setting up a rollup configuration for the production build overall vite is a more opinionated higher level tool that aims to provide a more out of the box workflow that said the web umbrella project contains many other excellent tools that may benefit vite users as well suggest changes to this page backend integration migration from v1