Not killed, but for most typical frontend site codebases with a single index.html where scripts,stylesheets are injected into its probably the best solution
I wish you covered more details of how vite is different from parcel (or similar instrument). I recognize that it may sound too basic information but beginners like me would appreciate some basic details along with more advanced ones. Apart from that the content is really good and I cannot even imagine how difficult it was to build such instrument. Thank you for the material. Your time is well appreciated
Build cycles in my first job were 2-3 minutes. 2-3 minutes. Two, to three minutes. A full build of everything from the drop to make a .bin file to burn to 'the thing' was 27 minutes.
Hi Victor! This tutorial is part of a whole course that Evan You teaches. You can access the course for free this weekend only: www.vuemastery.com/vite-weekend-2021
I just remember crying and dying trying to update babel and babel plugins, and having a build tool that takes advantage of the current state of browsers is so nice.
Love you man! For the last few years I could never get into typescript because of all the issues I had with webpack configuration but this solved essentially all my pain points! THANK YOU SO MUCH!
Efficient as Native, that's great 😃👍 Thanks 🙏 I'm a 100% n00b programmer in JavaScript, I'm trying to educate myself, I can code on Pascal 7, Delphi and Visual Basic, so I can't understand much, but I understand enough, to see that is reduced to calls 🤙to Native code and not to a VM or other slow engine
Thanks for Vite, great tool! As Fo TS, the most valuable reason to use TS is type checking and we lose it with Vite. It would be awesome to have an option to switch from es build
The best thing about vite is the fouder itself teach people.I hope Evan Yu can teach us more about vite. Maybe do a lots of common projects such ecommerce, CRUD and etc. So people can see clearly the power of vite. But i wondering what happen to Vuejs?
A little bit of clarification, Well, not type checking typescript files wasn't a choice for Vite, it's a limitation bound to ESBuild Since ESBuild is written in Go & Go is a statically typed language. But it doesn't support interfaces/unions/generics (generics are supported in beta though). Also it's OOP works bit differently & uses structs instead of classes (similar to Rust/C) to support OOP-'ish' paradigm. Thus it's hard to implement the TS Type-Checker in Go but not impossible Also implementing "static" Typechecking is a lengthy process & requires huge patience & a lot of code. All the reason combined it was a bit too hard for the ESBuild (also Vite) team to accomplish such difficulty but we know OSS, right? We'll overcome this limitation too!👍 BTW, for your information, the one & only Typescript type-checker is the official one. Though there's been work going on in SWC (Rust based frontend build system) but it seems the author will keep the type-checker part proprietary & paid
Was trying to use it with my ts+react project, but faced with some polyfill issues so I give up and choose raw esbuild. Anyways, from the developer perspective vite looks simple and amazing and I wish to use it in future projects
thanks for your explained. iwanna ask in my case i have laravel breeze with vite and i must run 'npm run dev' to open the project and works good. then how to deploy to the web server works good cause in the web server i cannot run ''npm run dev''
Followed along here and found that not only is hot reloading not working, nothing updates at all unless I restart the dev server. Any basic troubleshooting tips?
Is it going to work with stuff relying on Babel plugins such as Relay compiler, allowing to have GraphQL fragments inside of js/ts code (similarly to how you use JSX inside .js/.ts files)?
I may be missing a point but how do i procress a js file before rendering the html page. In Webpack one has an html (ejs) file and a js file per page. So I am kind of lost here. I don't use frameworks and only vanilla javascript
Its really cool I just didn't get why would you use typescript but without type checking? just to get features such as interfaces etc? would it be worth to write interfaces if there is no type checking
You have awesome content.I am stuck on a problem plz guide me on I am implementing server-side rendering for a datatable (e.g., blog listing) in my Laravel project. I need to create a JavaScript file for this purpose. Should I place this datatable JS file in the public directory? If so, how do I compile the JS file from the resources directory to the public directory using Laravel Vite?Where should be the file placement in the folder structure. project-root/ ├── resources/ │ ├── js/ │ │ ├── app.js │ │ └── datatable/ │ │ └── blogListing.js ├── public/ │ └── build/ ├── vite.config.js ├── package.json └── ...
I have problems with the @use and @import in vite.js. I can't use @use to import a folder for example @use 'components', I can't use @import with comma and without .scss extension, for example @import 'uno', 'due', 'tre': but I have to write always @import.... why? it's terrible
Thanks Evan! Like some others watching this I work daily with Webpack5 which gets the job done. Vite looks like just the thing to try out on a new three.js experimental 🧪project where I was looking for faster/hot reloads (than Webpack) to be more forgiving on me as I blunder my way up the three.js learning curve
Me: Who's teaching Vite? Someone: You? Me: ME? Someone: No, You. You: Someone has to do It. It: Sheesh... Can we get dinner first? [At Dinner] Someone: So anyways, Im a React developer. What about You?
Vite is awesome, but I must admit I get a bit lost between what I was thinking a frontend tooling does and what a framework does(typically, why vite's plugin could manage my app framework. Is it still a bundler/tool to manage/compile my frontend since it starts to handle logic of the app? As a newbie, it's a bit hard for me to understand where Vite ends and where Vue starts.
We have a full course taught by Evan: www.vuemastery.com/courses/lightning-fast-builds-with-vite/intro-to-vite, hopefully he can help answer your questions. 💡
@@j4nch Which courses are you referring to? We've been hard at work publishing a bunch of new courses on the latest releases, with 5 new courses published in the past couple months :D
@@VueMastery I only tried the "Intro to Vue 3", but it doesn't use the Composition API(which should be the de facto approach nowadays), nor the script setup tag which make much more sense to me. I never liked the option api approach(reason why I was mostly doing some angular/react until now)
Don't need to worry about new things. As long as you know the fundamental, no matter is Vue, React or others. You can easily pick it up. Those "influencers" just want to emphasize "it's must know thing" to make you feel imposter syndrome so they can sell you their interview tutorials. You can really see the difference between tutorial sellers and devs want to do teach you something.
is that the reason I am learning golang because is the future in my opinion personal first laravel octane in the back end now vite in the front end beatiful.
npm init vite - BOOM! it DOES work with react I consider to use it instead of CRA - advantages are obvious, what about disadvantages, can you point some?
What's the point of supporting Typescript in development if there's no type-checking? The claim that your ide can handle that is not a good one. VScode isn’t a great tool for surfacing errors in customized typescript workflows or just in deeply nested projects in general.
Evan, how am I supposed to get my coffee in between builds now huh? you only think about yourself.
Hahahaha I said to my team the same :D
You will be fired in nearest few years, because frontend will be generated using AI.
Go drink your coffee. and eat banana!
Great comment man hahaha
Nice one!! :D
That's the downside of vite I am struggling with 😂
Having someone explain his own work is so much better 🙂
Omg he's a really good teacher too.
Evan, this is amazing. You basically killed all webpack-based tooling. Good job, I won't miss any of that, not one bit!
@@dae2530 keep coping like that
Not killed, but for most typical frontend site codebases with a single index.html where scripts,stylesheets are injected into its probably the best solution
@@heathledger7291 It can also handle multiple entry points...
First time seeing the vanilla version of vite, it really is looking like the future of frontend tooling!
Yeah 😊
Yeah!that is so cool
I love Vue for all the freedom it gives in development and I hope fall in love with Vite too.
I've been enjoying the Vite + Svelte combo, it's like "wow, where has this been all my life?"
i Love how excited and proud he is
this is by far the awesomest video to understand what vite does
What an absolute legend this guy is
This guy is the best thing that happened to JS just like Taylor Otwell is the best thing that happened to PHP
What about Fabien Potencier?
i use vite for building components in react, and i really love it ❤️🔥❤️🔥❤️🔥
this is incredible! I'm honored to receive such valuable education.
I wish you covered more details of how vite is different from parcel (or similar instrument). I recognize that it may sound too basic information but beginners like me would appreciate some basic details along with more advanced ones. Apart from that the content is really good and I cannot even imagine how difficult it was to build such instrument. Thank you for the material. Your time is well appreciated
this hands down one of the coolest shit i've seen in frontend tools
Build cycles in my first job were 2-3 minutes. 2-3 minutes. Two, to three minutes. A full build of everything from the drop to make a .bin file to burn to 'the thing' was 27 minutes.
Love the way he’s teaching
This is a great peek at what's going on in the frontend world 😄 I hope you turn this into a series.
Hi Victor! This tutorial is part of a whole course that Evan You teaches. You can access the course for free this weekend only: www.vuemastery.com/vite-weekend-2021
@@VueMastery Oh wow! Thank you so much 🙏
I just remember crying and dying trying to update babel and babel plugins, and having a build tool that takes advantage of the current state of browsers is so nice.
This man is a legend. 15 gold Olympic medals if JS was a sport.
Never thought Vue creator, an ex-Google would do this simple tutorial, awesome!
Love you man! For the last few years I could never get into typescript because of all the issues I had with webpack configuration but this solved essentially all my pain points! THANK YOU SO MUCH!
Efficient as Native, that's great 😃👍
Thanks 🙏
I'm a 100% n00b programmer in JavaScript, I'm trying to educate myself, I can code on Pascal 7, Delphi and Visual Basic, so I can't understand much, but I understand enough, to see that is reduced to calls 🤙to Native code and not to a VM or other slow engine
"Who's the teacher in that video?"
"It's You"
"Huh? I mean who is the teacher?"
"It's really You!"
...
: hi, I'm you
: then who I'm!
Thank you for care of dev server speed, it was pain working without it.
You're awesome, Evan!
Started with Grunt the other day. Will be migrating to Vite immediately 😆
This is amazing... Please support angular too!
Evan it's really Great, Thankyo for this .
Thanks for Vite, great tool! As Fo TS, the most valuable reason to use TS is type checking and we lose it with Vite. It would be awesome to have an option to switch from es build
The best thing about vite is the fouder itself teach people.I hope Evan Yu can teach us more about vite. Maybe do a lots of common projects such ecommerce, CRUD and etc. So people can see clearly the power of vite. But i wondering what happen to Vuejs?
Sigue en pie, lo único es otra herramienta más pero con otra agilidad
Vít (same pronunciation as Vite) is czech name. Vít is super formal form though.
Home form: Vítek
English: Guy, Vitus
Does it do tree shaking? I was assuming only importing debounce from lodash, The file size would ib in KBs instead of 1.3MB @13:00
How about debuging JS/TS in the chrome dev tools ?
A little bit of clarification,
Well, not type checking typescript files wasn't a choice for Vite, it's a limitation bound to ESBuild
Since ESBuild is written in Go & Go is a statically typed language. But it doesn't support interfaces/unions/generics (generics are supported in beta though). Also it's OOP works bit differently & uses structs instead of classes (similar to Rust/C) to support OOP-'ish' paradigm. Thus it's hard to implement the TS Type-Checker in Go but not impossible
Also implementing "static" Typechecking is a lengthy process & requires huge patience & a lot of code. All the reason combined it was a bit too hard for the ESBuild (also Vite) team to accomplish such difficulty but we know OSS, right? We'll overcome this limitation too!👍
BTW, for your information, the one & only Typescript type-checker is the official one. Though there's been work going on in SWC (Rust based frontend build system) but it seems the author will keep the type-checker part proprietary & paid
Go has interfaces, by the way
Well now I know it's not Vite as in bite, but Veet as in the hair removal cream. Can't wait to use it though.
The "t" at the end is also a soft one
Hi Evan, any plans for mobile app development with vuejs?
Was trying to use it with my ts+react project, but faced with some polyfill issues so I give up and choose raw esbuild. Anyways, from the developer perspective vite looks simple and amazing and I wish to use it in future projects
thanks for your explained. iwanna ask in my case i have laravel breeze with vite and i must run 'npm run dev' to open the project and works good. then how to deploy to the web server works good cause in the web server i cannot run ''npm run dev''
Awesome video! Quick question, what's the VS Code theme's name and the icon's name? looks super dope!
I always found that vite felt somehow like magic. Now I know it IS magic 😉
Can I change the css code template of the provided css file?
please make a video about module federation using vite originjs plugin
Vite is awesome :), you deserve to have a better microphone!!
and a debounce support for webcam
How do I unlock my aetherium I sent less than zero point three
great tutorial, thank you so much
I often have problems with old listeners still being attached after a hot reload. Are there any best practices to avoid this?
Yes. Not to use hot reload.
Bose NC 700 - have the same headphones :)
Followed along here and found that not only is hot reloading not working, nothing updates at all unless I restart the dev server. Any basic troubleshooting tips?
Is there ANY tutorial for vitesse????
Is it going to work with stuff relying on Babel plugins such as Relay compiler, allowing to have GraphQL fragments inside of js/ts code (similarly to how you use JSX inside .js/.ts files)?
Wow, this is a game-changing tool.🙂
If the us and html is in the public folder, it does not load the import module?
but still vite is not working for me with react the server do not start. has some error on callback function
i have websocket connection to wss failed. How i can resolve that, thanks
I hope we get React Native support in the future
How to add env variables to vite.config.js (I'm creating a React Vite Project)
Is it Google Glass on the thumbnail?
Is the image flipped? I thought there was only right-eye version.
Yes it's flipped. Good eye! 😁
Hey, what about Vite support Vue 2?
This dude was born to be a Javascript engineer.
I too collect Gundam, Evan!
I may be missing a point but how do i procress a js file before rendering the html page. In Webpack one has an html (ejs) file and a js file per page. So I am kind of lost here. I don't use frameworks and only vanilla javascript
Its really cool I just didn't get why would you use typescript but without type checking? just to get features such as interfaces etc? would it be worth to write interfaces if there is no type checking
VSCode or another IDE that's setup properly will give you type-checking, so doing `let foo: number = "bar"` for example will show an error in the IDE
Why is angular not supported? I know that angular cli is already using esbuild on version 13, so angular cli is just as fast as vite?
I wish there was a option to make it use one src folder
Why is it working? I mean, I can't see any webpack configuration anywhere.
Haha, good one. Because it's not webpack, but esbuild for development and rollup for production.
dumb question.. why not just use esbuild then? What am I missing here?
Yeah, good question.
vite is awesome 🥰
amazing video
You have awesome content.I am stuck on a problem plz guide me on
I am implementing server-side rendering for a datatable (e.g., blog listing) in my Laravel project. I need to create a JavaScript file for this purpose. Should I place this datatable JS file in the public directory? If so, how do I compile the JS file from the resources directory to the public directory using Laravel Vite?Where should be the file placement in the folder structure.
project-root/
├── resources/
│ ├── js/
│ │ ├── app.js
│ │ └── datatable/
│ │ └── blogListing.js
├── public/
│ └── build/
├── vite.config.js
├── package.json
└── ...
I have problems with the @use and @import in vite.js.
I can't use @use to import a folder for example @use 'components', I can't use @import with comma and without .scss extension, for example @import 'uno', 'due', 'tre': but I have to write always @import.... why? it's terrible
Thanks Evan! Like some others watching this I work daily with Webpack5 which gets the job done. Vite looks like just the thing to try out on a new three.js experimental 🧪project where I was looking for faster/hot reloads (than Webpack) to be more forgiving on me as I blunder my way up the three.js learning curve
what terminal app/theme he use?
I was wondering the same. Looks much better than Apple's.
it's iTerm
30x faster but don't do type checking! Not a fair comparison plus removing a really important feature to make it faster.
Me: Who's teaching Vite?
Someone: You?
Me: ME?
Someone: No, You.
You: Someone has to do It.
It: Sheesh... Can we get dinner first?
[At Dinner]
Someone: So anyways, Im a React developer. What about You?
Same, React😂
Hahahahahaha
lol 😂
still have insane difficulty setting up node/express with a local client server. tasks like this shouldn't be so hard
hello does someone know what colour theme is this on vscode?
JIC, you need a better camera mount; Seems like earthquake everytime you type.
Could I ask, if my repo needs to import third party library which is still using require syntax, how to solve the vite compile issue for this?
Vite is awesome, but I must admit I get a bit lost between what I was thinking a frontend tooling does and what a framework does(typically, why vite's plugin could manage my app framework. Is it still a bundler/tool to manage/compile my frontend since it starts to handle logic of the app? As a newbie, it's a bit hard for me to understand where Vite ends and where Vue starts.
We have a full course taught by Evan: www.vuemastery.com/courses/lightning-fast-builds-with-vite/intro-to-vite, hopefully he can help answer your questions. 💡
@@VueMastery thanks, I will take a look. The last courses I checked on your platform were outdated.
@@j4nch Which courses are you referring to? We've been hard at work publishing a bunch of new courses on the latest releases, with 5 new courses published in the past couple months :D
@@VueMastery I only tried the "Intro to Vue 3", but it doesn't use the Composition API(which should be the de facto approach nowadays), nor the script setup tag which make much more sense to me. I never liked the option api approach(reason why I was mostly doing some angular/react until now)
The production quality of this vid is very high, good job! How did you record it? Or what software did you use for it?
does anybody know which VS code color schema Evan is using on the video?
I think it is Material Theme (Palenight High Contrast)
@@pdi999 awesome! thank you
Vite is the best!
I love vue
其实是想说 loaash-es 会 tree shaking 的是吗？
every couple of weeks something new called "a must" and you should start learning it, and before you manage to master it something newer comes in
Except that if Evan You states that it's "a must", it probably is.
Don't need to worry about new things. As long as you know the fundamental, no matter is Vue, React or others. You can easily pick it up.
Those "influencers" just want to emphasize "it's must know thing" to make you feel imposter syndrome so they can sell you their interview tutorials. You can really see the difference between tutorial sellers and devs want to do teach you something.
@@Snakeeaterrr No, he wouldn't. When he say it's a must, it's likely either a critical bug so you need to upgrade your Vue, or Vue 4 5 6 is coming.
Does anyone knows what theme is used in Vscode ?
Purple shade
awesome, looks very very well
Thanks for the presentation but at the moment vite does not work well with docker I hope that problem gets fixed.
I'm using it with Docker 🙂 although it was not straight forward. What is it you're going through? maybe I can help.
@@shinobi77 What is the issue?
Apparently you do not fully understand what you talk about. If Vite works in your system then it will work in Docker as well.
@@mojekonto9287 exactly
@@shinobi77 Can you share your script/Dockerfile/whatever worked so that others can benefit?
Where I can find these vite's videos... ??
You can find them here: www.vuemastery.com/courses/lightning-fast-builds-with-vite/intro-to-vite ☺
Thanks Evan!
is that the reason I am learning golang because is the future in my opinion personal first laravel octane in the back end now vite in the front end beatiful.
rust?
I would like to ask, as I am trying to access free tickets available registration link, the page cannot be reached
Hi David, is this link working for you?: www.vuemastery.com/vite-weekend-2021
Does it work with frameworks such as vuetify? How can i bundle my existing vuetify project with vite 🙈 with vite ... Get it?
npm init vite - BOOM!
it DOES work with react
I consider to use it instead of CRA - advantages are obvious, what about disadvantages, can you point some?
Evan You, so fucking smart guy. Daamn.
Evan is the next Linus
What's the point of supporting Typescript in development if there's no type-checking? The claim that your ide can handle that is not a good one. VScode isn’t a great tool for surfacing errors in customized typescript workflows or just in deeply nested projects in general.
Why Vite use 5173 port,
because V = 5
so VITE is V173 or 5173
It looks like CSS Module Scripts comes into our lives. Are there any plans to abandon your own version of working with CSS in favor of native modules?