vite

I'm glad that your trivial migration was trivial. All this was a big source of churn for plugins and frameworks: https://github.com/vitejs/vite/discussions/16358

Vite 8 has been a huge disappointment: https://github.com/vitejs/vite/issues/21939 Build filesizes have doubled... No build speed gain is worth that... I would take a slightly longer build time for half the filesize any day

The solution here is working for me: https://github.com/vitejs/vite/discussions/21505 Though sometimes oxc complains about JSX in JS when running vite, but it still works fine.

I have a small React project using vite 7 and have the following in my config so that vite interprets ".js" files as JSX: // See https://github.com/vitejs/vite/discussions/14652 esbuild: { loader: "jsx", include: /.*\.jsx?$/, exclude: [], }, optimizeDeps: { esbuildOptions: { loader: { ".js": "jsx", }, }, }, Note the comment at the top. I had no idea how to come up with this config by checking the documentation pages of vite and its various related tools. Luckily I found the GitHub issue and someone else had come up with the right incantation. Now this new vite uses new tools, and their documentation is still lacking. I spent half an hour trying to figure out how vite (and related tools that I had to navigate and try to piece a coherent view of: esbuild, oxc, roll

Looks like a lot of them are pinning to tags (which are not guaranteed to change) or SHA (https://github.com/vitejs/vite/blob/8da04227d6f818a8ad9efc00...) which is more hermetic.

CSS sourcemaps, being a basic assets in frontend tooling for many years, are still unsupported in Vite(https://github.com/vitejs/vite/issues/2830). Being an open issue for that long, while sourcemaps are supplied for free with tools like ESBuild & SCSS, are perhaps an indication of too much complexity in Vite? About build performance; ESBuild(and SWC as well) happily build large projects within reasonable time(<200ms). I doubt that skipping bundling all-together, by using ES-Modules during development, is worth the extra hassle in tooling. It made sense during the Webpack/Vuepack/Parcel 1 era, but not that much anymore since ESBuild happened. Spending some extra time in writing a custom buildscript (ESBuild + SCSS + simple async task manager + Chokidar + Tinylr or something similar) pays itself back really quick when a project gets larger

Stable API perhaps, but vite has issues with memory leaks, which can break builds in CI. https://github.com/vitejs/vite/issues/2433

React Context HMR still has problem. Due to this problem, I think nextjs still the better choice for react dev. Maybe vite supports too many frameworks, do not have enough time to handle the react problems. [1]: https://github.com/vitejs/vite/issues/3301

I've used Vite in a simple vuejs project and love its simplicity over webpack. However, debugging Vue3 with hot-module-reload seems to be broken. The moment HRM changes a source file, the line numbers and breakpoints not always line up and breakpoints. (https://github.com/vitejs/vite/issues/5916). The inability to debug properly is not a minor issue so I'm torn to go back to webpack or disable HMR to keep using Vite. Other than that, the simplification that Vite brings to the build process is sorely needed. I can only imagine how many developer hours have been lost in dealing with Webpack configuration issues. It is ironic that setting up a web development environment is more complicated than building a basic application. Thank you Vite developers for offering relief :)!

I always encourage users to use vite, and it is quite easy for the dev server. https://github.com/vitejs/vite/issues/3909 For deployment it's a different story then but for example netlify has a quite intuitive way to set headers for CORS: https://github.com/padenot/ringbuf.js/blob/master/public/_he...

Looks great! For SharedArrayBuffer and CORS, I have some experience and it's not difficult to deal with. You can check my project for music live coding in browsers: https://glicol.org All the audio library and langauge parser are written in Rust and compiled to WebAssembly, running in AudioWorklet thread. The control parameter is constantly shared from main thread to AudioWorklet thread with my customised ringbuf.js to avoid GC from JS in real-time audio: https://github.com/chaosprint/glicol I use vite.js for development; for local dev server CORS, check: https://github.com/vitejs/vite/issues/3909 For deployment CORS, e.g. Netlify, just edit the '_header' file as: /* Cross-Origin-Opener-Policy: same-origin Cross-Origin-Embedder-Policy: require-corp in the 'public' folder.

Vite [0] configures React, Vue and more perfectly out of the box [0] https://github.com/vitejs/vite