Vite looks the way forward. Only thing that was annoying for me still, was that Storybook still uses webpack stuff, but they are moving over to better support for Vite as I understand.
I rather compare Gatsby to CRA or Vite, because of its «serverless» output. I Gatsby is doing a wonderful job, especially with the build in accessibility features 😍 But seriously, there are some downsides with ESbuild and Vite, like no three shaking, no Babel/ESLint check support during the build. Also fast-refresh is not working. And Vite does not type check, so all these will make them faster by design. It is kind of important to know the downsides before actually cosseting them to be an real alternative. But things are going in that direction for sure!
Is it fast because of parallelism or because of go? What about all the talk about V8 being so fast. I would assume webpack/rollup also used parallelism through workers but maybe not ?
NextJS is currently using webpack, so even if they have plans to migrate to esbuild, it would still be a pain to move it 1:1. There are also features in webpack that do not exist in esbuild and there are no plans to in the future, such as code transforms, manipulating ASTs, etc.
They did just hire the author of Webpack, so they definitely have plans for the future, whether that is taking some of the best elements of ESBuild and tying it into Webpack, or just scrapping Webpack entirely and building something new, who knows. They'll need to do something because it won't be long before plenty of competing React abstractions built on Esbuilds/Snowpack look to dethrone Nextjs.
@@coherentpanda7115 For them to adopt ESBuild, they have to deprecate Webpack, as most of the bundler process is done in Webpack. I don't see them deprecating Webpack even if the author is working with them
Would you consider covering snowpack as well? I'm curious to hear what you think, I've been using it for development and it's concept of unbundled development is super interesting
My original plan was to cover Snowpack and then Vite came out and I was going to cover Vite and then I realized ESBuild was also super interesting. The neat thing about Snowpack AFAICT is that it effectively removes bundling by leveraging native browser ES Modules. Vite definitely seems poised to out pace Snowpack in terms of popularity. Seems to have taken all the best ideas of Snowpack and Parcel and packaged it into one super strong bundler.
Who is really so displeased with webpack that they want to replace it? Literally a Swiss Army knife of front end development. Most people will do a large build maybe once per a project. Saving 30 seconds once every couple of months maybe vs spending time to learn and debug a new tool isn’t really a big deal.
Or, if you have internal develop or staging sites that iterate very fast. Spending five or more minutes every time you push to upstream is not the most productive work flow i could imagine.
With serverless/cloud computing prevalent especially in frontend development, multiple and parallel builds are done simultaneously. Waiting for 5 minutes just to be able to preview and review your changes before shipping it can become a bottleneck and costly.
@@exactzero I don’t know why you are building front end projects in the cloud, but it likely isn’t necessary. Yarn already caches your packages. If you have environment variables, you should inject those directly into the app from the server, and any compile time environment variables should be retrieved via an async function.
![ROSÉ(로제) - APT. (Band VER.) (With. 이영지) [더 시즌즈-이영지의 레인보우] | KBS 241129 방송](http://i.ytimg.com/vi/IW8qaemx74g/mqdefault.jpg)
If EvanW made ESBuild, and EvanY made Vite, can you even imagine what EvanZ will make? 😳
EvanU made Vite 😆😆
@@lightify97 Evan You = EvanYou = EvanY. Anyway, it was a good joke.
Where EVANX?
What is Vite? How you cook it ? how you eat it? A video on Vite would be appreciated the community.
Vite looks the way forward. Only thing that was annoying for me still, was that Storybook still uses webpack stuff, but they are moving over to better support for Vite as I understand.
Hopefully! I can create components faster than waiting for Storybook to load.
Great video! 1st time I'm hearing about these tools. Thanks
Nice video! I never knew vite existed either, thanks for introducing it in this video :)
i subscribed as soon as i heard that finger get sizzled
Hell yeah!!
Great video. Always been frustrated with webpack complexity and speed despite their very best efforts in every release to make it better.
that's a great video, any idea about running esbuild with node+typescript?
Are you going to make a demo video of the tool?
I rather compare Gatsby to CRA or Vite, because of its «serverless» output.
I Gatsby is doing a wonderful job, especially with the build in accessibility features 😍
But seriously, there are some downsides with ESbuild and Vite, like no three shaking, no Babel/ESLint check support during the build. Also fast-refresh is not working.
And Vite does not type check, so all these will make them faster by design.
It is kind of important to know the downsides before actually cosseting them to be an real alternative.
But things are going in that direction for sure!
Hi Harry, Can you make a video about the Frontend developer interview preparation process. How can I prepare myself for job. Thanks.
There is Snowpack which is another esm based build to have an eye on..
And it uses esbuild under the hood as well!!!
@@lukaswerner4390 so does Vite
Is it fast because of parallelism or because of go? What about all the talk about V8 being so fast. I would assume webpack/rollup also used parallelism through workers but maybe not ?
it pronounced : veet not vite, its french for fast
With a short e like in fit but with the accent on t not on i.
Nice ***RASPBERRRY*** sound effects!
Hoping for Next.js to adopt this in some way.
NextJS is currently using webpack, so even if they have plans to migrate to esbuild, it would still be a pain to move it 1:1. There are also features in webpack that do not exist in esbuild and there are no plans to in the future, such as code transforms, manipulating ASTs, etc.
They did just hire the author of Webpack, so they definitely have plans for the future, whether that is taking some of the best elements of ESBuild and tying it into Webpack, or just scrapping Webpack entirely and building something new, who knows. They'll need to do something because it won't be long before plenty of competing React abstractions built on Esbuilds/Snowpack look to dethrone Nextjs.
@@coherentpanda7115 For them to adopt ESBuild, they have to deprecate Webpack, as most of the bundler process is done in Webpack. I don't see them deprecating Webpack even if the author is working with them
What about Snowpack?
Not to be that guy, but it's actually pronounced veet...
Hah! I’ll take it. Fair enough!
@@hswolff It looks like the guy from Vue likes french words :-)
Thanks for being "that guy" for the rest of us.
If I had a kid I'd name him "harry wolf"
haha but really, who ever dips into the webpack stuff? Definitely curious to hear about those adventures
Would you consider covering snowpack as well? I'm curious to hear what you think, I've been using it for development and it's concept of unbundled development is super interesting
My original plan was to cover Snowpack and then Vite came out and I was going to cover Vite and then I realized ESBuild was also super interesting.
The neat thing about Snowpack AFAICT is that it effectively removes bundling by leveraging native browser ES Modules.
Vite definitely seems poised to out pace Snowpack in terms of popularity. Seems to have taken all the best ideas of Snowpack and Parcel and packaged it into one super strong bundler.
You should check out SolidJS
How many times you gonna say "Vite" before you look right on the front page where it tells you how to pronounce it?
no ones say javascript tools must be written in javascript :)
You created VueJS.
yeah, Evan You is the creator / author of many cutting-edge technologies / frameworks, e.g. VueJS, Vuepress, Vite ecosystem...
It's pronounced Vite, not Vite!
Remix uses ESBuild
It's pronounced veet... it's a French word
Who is really so displeased with webpack that they want to replace it? Literally a Swiss Army knife of front end development. Most people will do a large build maybe once per a project. Saving 30 seconds once every couple of months maybe vs spending time to learn and debug a new tool isn’t really a big deal.
Or, if you have internal develop or staging sites that iterate very fast. Spending five or more minutes every time you push to upstream is not the most productive work flow i could imagine.
With serverless/cloud computing prevalent especially in frontend development, multiple and parallel builds are done simultaneously. Waiting for 5 minutes just to be able to preview and review your changes before shipping it can become a bottleneck and costly.
@@exactzero I don’t know why you are building front end projects in the cloud, but it likely isn’t necessary. Yarn already caches your packages. If you have environment variables, you should inject those directly into the app from the server, and any compile time environment variables should be retrieved via an async function.
Once you switch to Snowpack and witness the speed, it';s hard to want to go back to the old way of doing things.