Running the 3 different build at the same time is not a valid benchmark, because the processes are competing for your CPU. It would have made more sense to run the one after the other.
I got started with ReactJS ⚛️ not too long ago, I couldn't believe I waited a more than 45mins for the create-react-app to fully set-up. Later I found Vite, I have not looked back ever since. Great Video 👍🏾😊
my current company is using vite. And it is awesome, light weight and super fast. But there is hard to figure it out when there're errors during configing to make it work with some libraries.
i recommend every programmer learn the Rollup API and build their own apps that way. Rollup is very straightforward and only needs to be as complicated as you want it to be (vs. webpack, where it's just always complicated lol).
Thanks for the intro. Would have been nice for more information on the impact of the final product Vs bundled file. You speak about the dev experience being fast but in the grand scheme of things, the production application is what matters. What improvements are made here by using Vite?
from what i know. the production is similar to cra and other react tool..vite only really focus on development environment. and as the app grows. the development speed still the same and fast
I take it this is more for new projects, I've tried switching an old react application (3 years) from webpack to vite, but I'm getting a lot of strange errors from the libraries.
I get it. It's fast but why is everyone ignoring the huge security risk of exposing your API connections and key because it serves the JSX files in the network activity tab without masking them or encoding them.
I have an issue with vite-react in vscode, specifically about auto imports When I setup jsconfig base url n paths, vscode doesn't work with it properly but webstorm works well and obeys the config
Vite sucks. There are no words how much it sucks. It fails to refresh files in sub folders. I have had to retart vite altogether to get my changes effective. DO NOT USE VITE AND DO NOT LISTEN TO THIS GUY.
Vite uses chokidar (github.com/paulmillr/chokidar) for file watching! There are scenarios related to different criteria (file-system, env, os...) that makes chokidar fails. This happens with all bundlers not only Vite. If it's failing for you, that doesn't mean it's rubbish.
Bitch wtf? i use vite and its pretty good actually, i have no complains about it, it just works and it is super fast, if you have problema with doesnt mean it sucks and hes lying like wtf you saying
Please stop comparison, just if I you like just use otherwise use webpack. Sorry but I do not like such comparison that creates the pro and cons groups. Thank you for the video
Running the 3 different build at the same time is not a valid benchmark, because the processes are competing for your CPU. It would have made more sense to run the one after the other.
I got started with ReactJS ⚛️ not too long ago, I couldn't believe I waited a more than 45mins for the create-react-app to fully set-up. Later I found Vite, I have not looked back ever since. Great Video 👍🏾😊
wtf you coding on, pentium 3?
@@vnm_8945 hahahaha 🤣😂, I guess the internet connection didn't help either 😂🤣
Same experience
45 ?🤯
Ain’t no way it took 45 mins man 😂
my current company is using vite. And it is awesome, light weight and super fast. But there is hard to figure it out when there're errors during configing to make it work with some libraries.
Exactly!
What about browser support?
Does the code generated by vite work on older browser versions as well?
Evan You , is a true gem for web developers .
Vite, pronounced "veet" (sounds similar to "feet")
i recommend every programmer learn the Rollup API and build their own apps that way. Rollup is very straightforward and only needs to be as complicated as you want it to be (vs. webpack, where it's just always complicated lol).
Vite Error handling is not as good as createReactApp.... This is the only cons
Vite = fast in french and we pronounce it "veet".
Thanks for the info. 😉
Thanks for the intro. Would have been nice for more information on the impact of the final product Vs bundled file. You speak about the dev experience being fast but in the grand scheme of things, the production application is what matters. What improvements are made here by using Vite?
from what i know. the production is similar to cra and other react tool..vite only really focus on development environment. and as the app grows. the development speed still the same and fast
"we need more frontend app builders, milord!"
Vite:68.84s vs Create React App:75.47s vs webpack:84.22s isn't that bad. thanks for sharing.
Vite is a great project starter. There are no issues when I run npm install and create my project.
I take it this is more for new projects, I've tried switching an old react application (3 years) from webpack to vite, but I'm getting a lot of strange errors from the libraries.
Correct, start using it from now on should work best... 😉
I get it. It's fast but why is everyone ignoring the huge security risk of exposing your API connections and key because it serves the JSX files in the network activity tab without masking them or encoding them.
Then, thanks to Vite, it is no longer necessary using webpack?
Yes
You are constantly delievering the best content! Love it.
Vite + React + Ionic > React Native ?
Wow, thank you for your amazing explanation!
why not pronounce it like "bite"?
We need vite.js tutorial full playlist 🙂
How to customise vite?
vite cant work with dynamic module out of the box and I have no idea how to configure it. Create react app at the other hand works out of the box
I'm learning Vite and I was scratching my head looking for how to support dynamic modules, thanks for confirming it cant do that out of the box
Vite is powerful 🚀🚀
Bro do you have scroll issues on chrome when using linux ubuntu
I have an issue with vite-react in vscode, specifically about auto imports
When I setup jsconfig base url n paths, vscode doesn't work with it properly but webstorm works well and obeys the config
you need to configure with vite.config.js path too in order to make it work beside the jsconfig
@@puppycatuaena4270 I have done that ..
Like I said.. it works fine in webstorm.. but vscode ignores it and uses relative paths
Perhaps it also depends on package managers
Try classic yarn (V1)
You won't have any issues
amazing. I will try vite!
thank bro
👍👍
Vite sucks. There are no words how much it sucks. It fails to refresh files in sub folders. I have had to retart vite altogether to get my changes effective. DO NOT USE VITE AND DO NOT LISTEN TO THIS GUY.
Vite uses chokidar (github.com/paulmillr/chokidar) for file watching! There are scenarios related to different criteria (file-system, env, os...) that makes chokidar fails. This happens with all bundlers not only Vite.
If it's failing for you, that doesn't mean it's rubbish.
vite is good, however it still has road ahead for improvement
Bitch wtf? i use vite and its pretty good actually, i have no complains about it, it just works and it is super fast, if you have problema with doesnt mean it sucks and hes lying like wtf you saying
@@coffee-is-power B!!!!tch ? I am not your mother I hope you know. Learn how to break words before typing something.
Yes guys. Just one more step and you'll realise react is a bunch of crap and you'll rediscover coding pleasure with vue 🤓
also when i code with vue, my mental health is more stable, lol
Please stop comparison, just if I you like just use otherwise use webpack. Sorry but I do not like such comparison that creates the pro and cons groups. Thank you for the video
It's pronounced Vite (Vaite).
According to the website it is pronounced veet.
@@joshuaneedham1260 The Sheik has spoken, and has spoken incorrectly.
{2023-05-03}
For fucks sake it's veeeeeeeeeeeet!