Replies: 20 comments 31 replies
-
|
Any chance to get #9590 added as part of Vite 4? Switching jsx automatic transform to esbuild should bring a nice performance boost for React developers. |
Beta Was this translation helpful? Give feedback.
-
|
There are unaddressed requests in the PR, but once they are done, we could release a new major of plugin-react independent from Vite core. I think it is still better to try to bundle the releases but changes to plugins can't be applied when they are ready. |
Beta Was this translation helpful? Give feedback.
-
|
Will the module federation be present? |
Beta Was this translation helpful? Give feedback.
-
|
We don't have plans for first-class support yet, but there is a Vite plugin you can use now too: https://github.com/originjs/vite-plugin-federation |
Beta Was this translation helpful? Give feedback.
-
|
you can also try hel-micro |
Beta Was this translation helpful? Give feedback.
-
|
I would love to give more feedback on vite 3 (and vite 4) but unfortunately am still stuck on vite 2 (like many others?). Is any active work going into the most upvoted issue: When disabling sourcemaps, I get stuck later on the build with this issue: |
Beta Was this translation helpful? Give feedback.
-
|
We would need some help on identifying the memory issue for #2433 as it's a broad topic. We had a brief discussion with Lukas from Rollup and have a hunch that it's caused by Rollup's module graph being kept entirely in-memory for tree-shaking. This may be improved in the future from Rollup instead, but another potential candidate to improve in Vite is #1309 |
Beta Was this translation helpful? Give feedback.
-
|
+1 to #1309 -- rebuilding |
Beta Was this translation helpful? Give feedback.
-
|
Personally I love anything latest. So am in 4 already. Works really good. |
Beta Was this translation helpful? Give feedback.
-
|
My biggest wishlist items for Vite at the moment are #9378, #7887 and #2830. Of those, the only one that I think could be considered breaking — and therefore worth prioritising for a new major version — is #9378. I would argue that the current default behaviour around |
Beta Was this translation helpful? Give feedback.
-
|
Not technically a breaking change, but I'd love to see #9763 landed. At the moment, Vite SSR will crash if you are using a pnpm or Yarn monorepo and have any CJS dependencies. |
Beta Was this translation helpful? Give feedback.
-
|
What is the time to support http2 with using proxy by default? I think it is important for loading performance. |
Beta Was this translation helpful? Give feedback.
-
|
This is also discussed in Vite 3 #7611 (comment), but the results seems to be that there wasn't much performance difference. I think it would still be better in the long run to move to http2 though, PR welcome! |
Beta Was this translation helpful? Give feedback.
-
|
generation of type decalarations in dist folder in library mode without any flags or plugins |
Beta Was this translation helpful? Give feedback.
-
|
As far as I know, for this we would need to include whole Here you can see a dependency graph of that plugin: https://npmgraph.js.org/?q=vite-plugin-dts Lines 38 to 40 in f787a60 So I'm sorry, but your request will never happen. |
Beta Was this translation helpful? Give feedback.
-
|
Browsers can get pretty slow when a project has lot of modules which results into a lot of http requests. Not sure what the best long-term approach is but it would be nice to address this #10047 so |
Beta Was this translation helpful? Give feedback.
-
|
We also experience major problem with the modules, browser (in dev) has over a minute in pending for all those http requests. we rebuild a lot of stuff to be more lazy, but I was thinking about the http-server that is used... is there a better, more performant substitute? it seems that the simple amount of requests puts the server under so much distress, that it just takes forever to resolve the first requests |
Beta Was this translation helpful? Give feedback.
-
|
It's unlikely to be related to the http server being used. It's hard to understand what exactly the issue is in your case without a reproduction though |
Beta Was this translation helpful? Give feedback.
-
|
I did not realize that v4 is already out in the wild, and I'm happy to report that our issue with |
Beta Was this translation helpful? Give feedback.
-
|
As far as my wish list for Vite 4 is concerned... I'm still trying to figure out what is going on in Vite 3 regarding a lib production bundle and tree shaking not apparently working. For reference #8464 is tracking this issue w/ Vite 3. Even adding the specific Rollup parameters mentioned in that issue doesn't seem to be effective w/ my UI library / end developers setups. Coming from Rollup before Vite 3 this wasn't a problem. With moving to Rollup 3 for Vite 4 making sure tree shaking works for production builds (lib or otherwise) out of the box would be superb. Thanks all Vite devs / maintainers! |
Beta Was this translation helpful? Give feedback.
-
|
Just as a note after spending a bit more time w/ Vite 3. It appears what is happening with my Svelte UI framework / library when creating distribution bundles is that all the CSS from every Svelte component from the UI library is getting included / no tree-shaking for the CSS from each Svelte component even if that component is not included in the final build. This is related to issue: #4389 |
Beta Was this translation helpful? Give feedback.
-
|
Dependency pre-bundling only applies in development mode, and uses esbuild to convert dependencies to ESM. In production builds, @rollup/plugin-commonjs is used instead. Give the possibility(option) to use esbuild instead of @rollup/plugin-commonjs during the production build. |
Beta Was this translation helpful? Give feedback.
-
|
Have you seen this? https://vitejs.dev/guide/migration.html#using-esbuild-deps-optimization-at-build-time |
Beta Was this translation helpful? Give feedback.
-
|
Experimental |
Beta Was this translation helpful? Give feedback.
-
|
implement an option/plugin which supports node core modules/globals I understand that the goal is browsers....but as a separate option/plugin - it would be cool |
Beta Was this translation helpful? Give feedback.
-
|
I think this should be implemented in userland instead of something for Vite 4. There are a few options currently like https://github.com/sodatea/vite-plugin-node-stdlib-browser |
Beta Was this translation helpful? Give feedback.
-
|
I think in 2022 it is a little bit hard to get rid of all packages which are using node global/core modules and if you're working in a big company it is a little bit problematic to include such packages with first line in the description: Disclaimer: I've only tested this plugin in simple projects. If you encounter any issues, please open an issue with a minimal reproduction in the project repository. Therefore it would be great to include an official plugin for legacy project/package. Over time everything will move to ESM and the plugin will not be needed, but as an additional option - it would be nice |
Beta Was this translation helpful? Give feedback.
-
|
I don't think this would be something that couldn't be part of a minor, but would love to see some more SSR love - specifically #9054 and #9446. Import assertions also remain an issue - #9446 |
Beta Was this translation helpful? Give feedback.
-
|
Potentially expose transformCjsImport so people can manually transform modules the same way Vite does. |
Beta Was this translation helpful? Give feedback.
-
|
Is it possible to use Rollup v3 with Vite v3? |
Beta Was this translation helpful? Give feedback.
-
|
Rollup 3 is big enough to require a major on Vite's side. You can already use it with vite@4.0.0-alpha.0, and we'll try to keep Vite 4 scope small so we can release the stable version in a month |
Beta Was this translation helpful? Give feedback.
-
|
Can you update rollup to v3.3.0 in the next alpha release? It includes important changes rollup/rollup#4327 |
Beta Was this translation helpful? Give feedback.
-
|
We are already on v3.3 (#10890), the next alpha will use it 👍🏼 |
Beta Was this translation helpful? Give feedback.
-
|
I saw a conversation on Discord about swc being available in vite v4, but no mention here. Is that happening? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, we plan to offer an official React plugin using SWC, and keep the current one using Babel, and document the tradeoffs so users can choose the best one for them. |
Beta Was this translation helpful? Give feedback.
-
Looking forward for this one. Quick question, though. Planning to start a new project with React and TS, should I stick to previous template (with esbuild) or SWC one is production ready? |
Beta Was this translation helpful? Give feedback.
-
|
You can read more here. Both are "production ready". |
Beta Was this translation helpful? Give feedback.
-
|
Would adding SystemJS support be a breaking change? I mean it sounds like just a feature, but maybe it requires changing some internals that would cause backwards incompatibility. If yes, can it be reconsidered as it was rejected by Evan? See #588 (comment) for more details. If it wouldn't be breaking then of course it could be added in some next minor release, so not adding it in 4.0 is not a big problem Or maybe it is already supported but |
Beta Was this translation helpful? Give feedback.
-
|
I'm probably squarely in the minority here, but one change I'd love to see for Vite 4 is getting rid of the config bundling step. It seems harmless, and allows people to use TypeScript to author their configs, but it results in subtle bugs, such as these ones in SvelteKit:
Rollup used to do something similar — it would use itself to bundle Inside a -import type { UserConfig } from 'vite';
-const config: UserConfig = {
+/** @type {import('vite').UserConfig} */
+const config = { |
Beta Was this translation helpful? Give feedback.
-
|
In SvelteKit our build config is currently split in two files : |
Beta Was this translation helpful? Give feedback.
-
|
That's unrelated. It was done for the best compatibility with the ecosystem of Vite tools and Svelte tools which each look for their own config files |
Beta Was this translation helpful? Give feedback.
-
|
We are discussing aligning the output file name format with rollup and esbuild (from |
Beta Was this translation helpful? Give feedback.
-
|
I see that v4 just hit beta - is there an estimate on when it will be out of beta? |
Beta Was this translation helpful? Give feedback.
-
|
We are aiming for this Friday, testing and reports are highly appreciated. |
Beta Was this translation helpful? Give feedback.
-
|
I just took a stab at upgrading our project to the beta and ran into a bunch of errors around using styled components (I believe due to the ?inline css changes). There were a ton of warnings around our EDIT: Here's a repro of the stylus issue: https://stackblitz.com/edit/vitejs-vite-1pe6vf?file=App.tsx |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Thanks @bluwy can confirm that worked and it seems that vite 4 works nicely on my company's codebase now! 🎉 |
Beta Was this translation helpful? Give feedback.
-
|
I have a vite 3 project. How can I update it to vite 4? Do I need to make a new project from scratch and copy the files? Or do I simply update the version number in package.json, delete node_modules folder and do npm install? |
Beta Was this translation helpful? Give feedback.
-
|
Just update the version in |
Beta Was this translation helpful? Give feedback.
-
|
I tried the vite upgrade command, but it doesn't work for me. I get |
Beta Was this translation helpful? Give feedback.
-
|
@benmccann Aren't we supposed to use this or is this old now? |
Beta Was this translation helpful? Give feedback.
and others
-
With Rollup 3 released, we will be starting Vite 4 alpha/beta soon to bump the internal Rollup version. Along with other changes in the v4 milestone.
This release is planned to be less breaking, so not much work should be needed to upgrade. Among the main goals for this major release are:
es2020compatibility by default #9062)dotenv(Support for Multiline values in env files #10149, feat(env): support dotenv-expand to contains process env #10370)Some cleanups:
modeand env var handling (Rethink dev/prod/mode handling #9274)If you have any feedback about Vite 4, especially regarding breaking changes that we will not be able to do in future minors, let's discuss this here or create an issue and link it to this discussion.
Beta Was this translation helpful? Give feedback.
All reactions