00:01 Vite is a JavaScript build tool 02:26 Developing a Dev server for native esm requests. 07:06 Evan serves as the Project Lead for Vite 09:24 View is intentionally avoiding major paradigm shifts for stability and user experience. 13:45 Evan You worked intensively on Vite, achieving hot module replacement using native esm. 16:09 Making Vite framework agnostic 20:25 Vite became popular for SSR meta frameworks due to ease of use 22:26 Evan You has a less hands-on role in V compared to Vue 26:32 Code quality, trust, and communication are key for contributors 28:21 Identifying quality and confidence in contributors 31:49 Balancing contributions and cautiousness in project development 33:53 Challenges in providing context for new contributors 37:47 Vite has strong potential for significant growth. Crafted by Merlin AI.
Thanks for the interview 🙏 Very insightful to take a closer look into Vite and Vue, especially the "maintenance burden" and downside of "too many users".
32:00 When I want to contribute something to a project that is highly used I always reach out to a maintainer first via an appropriate channel. If I don't get buy in from them then I simply don't waste my time or theirs contributing. A maintainer that doesn't get back to you at all, is a pretty clear indication that your efforts will likely not be considered. Nothing wrong with that at all, contributors need a bit of thick skin around this stuff.
Because the standard start react is no longer developed and we don't have a choice, the choice is between 2 server side solutions or vite as the time of stating this.
33:00 To the contributors, I would say, you have already put good amount of effort by working on Pull request or creating an issue. Don't let that effort go waste by dropping the ball. Communication is important.
I love Vite and Evan is such an incredible developer.
Good thing I noticed is how open source authors are taking inspiration from one another and making the web better for everyone. True open source.
Evan You is fantastic at coming up with new tools and maintain the focus beyond the startup face 🙌👏👏👏
His hands on approach is inspirational
"We have too many users" based.
Wild how integrated vite is in the framework space.
I mean, 4 million downloads/wekk, is not react level but it is a very huge amount of users
Now the team is working on Rust alternative of Rollup named Roll Down. Excited for it
Looking forward to the growth of the team and contributions
Looking forward to the future of Vite, including Rolldown, doubling down on the oxc toolchain etc etc ✨
Same
00:01 Vite is a JavaScript build tool
02:26 Developing a Dev server for native esm requests.
07:06 Evan serves as the Project Lead for Vite
09:24 View is intentionally avoiding major paradigm shifts for stability and user experience.
13:45 Evan You worked intensively on Vite, achieving hot module replacement using native esm.
16:09 Making Vite framework agnostic
20:25 Vite became popular for SSR meta frameworks due to ease of use
22:26 Evan You has a less hands-on role in V compared to Vue
26:32 Code quality, trust, and communication are key for contributors
28:21 Identifying quality and confidence in contributors
31:49 Balancing contributions and cautiousness in project development
33:53 Challenges in providing context for new contributors
37:47 Vite has strong potential for significant growth.
Crafted by Merlin AI.
Vue*
Thanks for the interview 🙏
Very insightful to take a closer look into Vite and Vue, especially the "maintenance burden" and downside of "too many users".
Vite tooling is slowly building the missing pieces in build tooling. The fact these are all mostly volunteers is impressive.
Great interview! Love the casual format
Thanks for watching
Thanks for the interesting interview! Vue, Vite, Vitest, VitePress
Really great and well produced interview!
Thanks for watching
React/Next should adopt Vite like all other frameworks.
You can use Vite in a React project. But you can't use it in a Nextjs project
@@timmeehan2365 It would be nice if it was possible to use Vite in both React and Next
nah, their fragile pride cant take it
Next.js should 👀
32:00 When I want to contribute something to a project that is highly used I always reach out to a maintainer first via an appropriate channel. If I don't get buy in from them then I simply don't waste my time or theirs contributing.
A maintainer that doesn't get back to you at all, is a pretty clear indication that your efforts will likely not be considered. Nothing wrong with that at all, contributors need a bit of thick skin around this stuff.
It’s the secret sauce
Because the standard start react is no longer developed and we don't have a choice, the choice is between 2 server side solutions or vite as the time of stating this.
Checks out. Vite came out at the right time.
Awesome interview
I've never considered asking "why is Vite everywhere?" the answer seems so simple and obvious... 'cus it's waaaaaaay better than WebPack! ;)
Keep up the great work.
If only NextJS used Vite aswell. Turbopack however is where they bet, the frameworks future build.
IMO leaves room for others to innovate with vite and capture mindshare.
your chapter generator, interprets Vite as VEET
Thanks. Just updated.
fun fact: Evan You look like Joseph Gordon-Levitt
🤔
what brand are your glasses? theyre super cool
Mine are Warby Parker Percys
did you guys call each other to plan your matching outfits or coincidence?
Perhaps it’s just the open source uniform.
👍👍👍
Why I am seeing Satya Nadella 😅
You paying for office 365?
People always build amazing things when they try to solve the problems that THEY are facing (instead of trying to solve someone else's problems)
33:00 To the contributors, I would say, you have already put good amount of effort by working on Pull request or creating an issue. Don't let that effort go waste by dropping the ball. Communication is important.
still using webpack, vite is not that flexible for my use case
Issues are welcomed
Noob gen bla .. bfdl is linus not python
That’s correct. Probably should of stopped and googled that one. FWIW the difference in time between the two is months.
Ha we are both wrong thsts what I meant to say Eric!
Because people don’t know DOM and JavaScript..🙄
I don’t know him either