ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #vite
When adding scoped styles to a Vite project, choose between Vite’s built‑in CSS modules and a PostCSS‑based solution. This guide compares build size, workflow, browser support, and feature richness, then shows concrete config examples and validation steps.
Learn how Vite’s esbuild‑powered pre‑bundling trims dev‑server startup time, how to tweak it with optimizeDeps, and when it might backfire.
Vite avoids slow cold starts by serving source files as native ES modules in dev and pre-bundling CommonJS dependencies on demand with esbuild. This keeps startup fast and HMR stable when configured with optimizeDeps.
Ship different API URLs per environment in Vite by using VITE_ prefixed .env files, build-time replacement via import.meta.env, and safe defaults to avoid leaking secrets.
Use Vite build.lib to bundle a library entry point, externalize dependencies, and wire up package.json exports for npm consumers.
Decide between Vite's esnext ESM target and legacy fallback bundles. Compare build size, speed, and browser support with a practical configuration and validation checklist.
Vite Library Mode switches your build from an app bundle to a distributable package. Learn how to configure build.lib, manage peer dependencies, and verify the output.
Vite's SSR mode reuses your client source for Node rendering, but it requires a server entry, careful dependency externalization, and guards against browser globals. Here is how to wire it up and what breaks.
Vite pre-bundles node_modules with esbuild in dev, so a stale optimized bundle is usually a cache and discovery problem — not a broken install.
postcss
vitejs