3 ms·
We're using Vite and enjoying it, would you say much of Vite could be replaced with pure esbuild? I guess Vite provides a nice development experience but is bu
by antihero 5y ago
We're using Vite and enjoying it, would you say much of Vite could be replaced with pure esbuild?
I guess Vite provides a nice development experience but is built on esbuild.
- maga 5y agoI guess it depends on your project and workflow preferences. Personally, I'm not a big fan of HMR and the bundling times are negligible even without "pre-bundling" npm dependencies (as Vite puts), so I see little reason for Vite.
- aidos 5y agoWe switched over to Vite some time back and it's been pretty life changing. We're using react and tailwind too, so the HMR works really well for us. The config is beyond minimal. If you're using webpack you may want to look away now :-) import { resolve } from 'path' import { defineConfig } from 'vite' import reactRefresh from '@vitejs/plugin-react-refresh' export default defineConfig({ plugins: [reactRefresh()], build: { rollupOptions: { input: { index: resolve(__dirname, 'index.html'), } }, sourcemap: true }, esbuild: { jsxInject: `import * as React from "react"` }, resolve: { alias: [ { find: '@', replacement: '/src' }, ] }, })
- Rapzid 5y agoThere is a short paragraph adressing this on the "Why Vite" page: https://vitejs.dev/guide/why.html#why-not-bundle-with-esbuild https://vitejs.dev/guide/why.html#why-not-bundle-with-esbuil... I'm also a huge fan of HMR, and esbuild in the past has been anti-HMR.