On the other side, the documentation is top. Even though it would help to have more examples/best practices, the overall documentation is one of the best. Same for both, Vite and Vitest.
LLMs know a lot of Vite/Vitest being so popular it helps.
Plugin system.
Integration between Vite and Vitest.
Vitest with browser mode and isolation fails on CI. There are some spikes in storage usage from Chrome's temp files.
Vitest + Istanbul coverage is really really slow.
Vitest + V8 coverage doesn't work with Chrome, only Chromium?? Not sure yet about the performance.
I don't have control on how scripts are injected and it's quite complex to inject a script at runtime before your main entry point.
The bundle seems bigger and chunks are a little bit "unexpected". This is something I need to dive deeper.
I started with V7 then I've waited v8 hoping it will be better, but no.
To name a few things:
Dev server in buildless mode doesn't scale - 2000 reqs for a refresh? It's slower then Webpack's incremental builds.
Dev server in build mode is not ready, at least source maps don't work at this point.
I don't want to throw shade on Vite/Vitest, I'm just frustrated with my experience. From outside, Vite/Vitest look top notch, but in my project they feel like the wrong tool for the job.
For context, I have a Lit-based SPA, around 200 screens and 6000 unit tests.
This is literally me while I'm migrating to @vite.dev and @vitest.dev. Once again I think Webpack is way underestimated. After months of work, today I configured vitest for coverage. The performance is dead. From 2-3 min to 27 min? 2-3 min was already just like Karma/Webpack/Jasmine, but 27 min??
Had a great experience today at ING Front-End Summit. 🙏
Vite+ is open source under MIT and free for everyone.
Thank you for all your efforts 🙏
Waited almost 2 years to buy a monitor and Apple comes with the exactly same monitor as 4 years ago 💀
🤬🤬🤬
Does it work with vitest too?
Is there any progress update on @vite.dev's Full Bundle Mode?
Since v8.0 is already in beta, can I hope for 8.1?
Well the joy didn't last. With isolation off, mock implementations get leaked in other files that use the original implementation at import time. 😪
Is this the final boss?
After months of investigations I think I found the problem. In isolation mode, Chrome doesn't seems to handle the load. For 1k tests in browser mode, @vitest.dev generates around 40k requests, which seems to be too much for Chrome.
Introducing Deno Sandbox
⭐ Instant Linux microVMs
⭐ TypeScript and Python (!) SDKs + REST API
⭐ Secure against prompt injection attacks
deno.com/blog/introdu...
Deno Deploy gets new features as it gains GA status.
⭐ Runs any node.js app or framework
⭐ Tunnels
⭐ Postgres databases
⭐ Built-in traces, logs, metrics
deno.com/blog/deno-de...
Any ETA for Vitest with Vite 8 (Rolldown)?
I'm not sure how to validate if this is indeed a real bug or a misconfig. 🤔
In the same environment, @webdevs.firefox.com doesn't have this issue.
I'm still digging this issue and I might have found a @developer.chrome.com bug. When running @vitest.dev in browser mode with Chrome, there is a spike of some deleted but opened temp files by Chrome. In low space environments, this can hit the max limit which crushes vitest.
Happy New Year! 🎊
I've tried a docker container with Ubuntu to be closer to the Azure DevOps agents, but no issues.
The only difference seems to be some warnings about disk space 🤔
🙋
WinterTC's Minimum Common Web API standard is now officially published as ECMA-429, Edition 1 . To many more editions!
Thanks @jasnell.me, @andreubotella.com, @akiro.se, @littledan.dev and everyone else that was involved in making this happen.
🎉
After months of migrating to @vitest.dev, I finally managed to fix all the tests...just to find out nothing works in the pipeline 🫠
I get a weird error: Failed to fetch dynamically imported module:...
This fails after around 1000 tests. The same error I'm usually getting in headful mode locally.
Congratulations!
Happy Halloween! 🎃
(with some delay)
JavaScript top-level await is no longer considered 'baseline' due to a pretty big Safari bug caniuse.com/mdn-javascri...
The module graph fails in cases where two modules import a third at the same time. Demo: random-stuff.jakearchibald.com/bug-repros/t...
It's best to avoid the feature for now 😔
👀
SVGOMG has been updated to use SVGO 4! (thanks Adrien Crivelli!)
This is the URL for SVGOMG. Unfortunately someone maintains a fork with ads, so, err, don't use that 😀
jakearchibald.github.io/svgomg/
any ETA for vite 8?