Setting up vite, React, TypeScript, eslint, prettier, vitest, testing-library and react-router

[@AlanRutter-h2m]

I have been updating a react app that I 'inherited' and decided to use vite, vitest and eslint. I read through countless articles, all saying different things, all configuring their apps slightly differently. Then I found this video .... a presenter that speaks clearly, presents the content at a comfortable pace to follow along, doesn't rush or skip over important bits. One of the best coding tutorials I have come across. Thanks to this video, i was easily able to re-configure the app. Great job.

[@maplestoryinchinese]

This is amazing! Quality content like this deserves so much more recognition.

[@BJAnderson]

Long time angular dev here. Was looking for a good tutorial on how to set up a real react project that I would actually use to build a professional (linted/formatted/tested) project from. This is that tutorial. A-ma-zing!!! Thank you so much!

[@Cognitoman]

Yea not bad

[@isurumaldeniya9536]

Thank you CJ for the super helpful video. If someone get error when accessing `toHaveTextContent` when writing tests add `import '@testing-library/jest-dom/vitest' ` in setupTest.ts file

[@youngun550]

8:32 to 8:37 is charming. I've seen this whole video 3 times now. It's really helped me get a firm sense of what eslint actually is and how to get a good ts environment. This is one of the best tutorials I've seen in a long time!

[@rembautimes8808]

An amazing video for productivity .

[@michaela.178]

Now that was a good tutorial! No point in excusing yourself for setting up tests the way you did. It's exactly what one would need to get started. I'd also add that one shouldn't get too obsessed with the designations of test types, you'll need those terms to keep some structure in your zoo of tests, eventually. Primarily, the set of all tests serves as cleverly laid out tripwires that keep us informed about unintentional changes, which helps our(future)selfes and anyone else getting on the project to make changes confidently.

[@elenafromny9567]

OMG! I tryied to set up jets for 2 days and now I found this video, thank you a lot!

[@PraveenChaudhary-u7f]

Good work man, one of the best videos on setting up a Vite project with Vitest + RTL.

[@wellingtonostemberg7585]

Thank you too much! You helped me solving a problem, nobody says that we need to add the file information on tsconfig -> include, this helped me a lot

[@shashikaharshana]

What a video. Dude you are just amazing attention to the detail is awesome. Love the content keep it up my bro. Love from Sri Lanka.

[@tukitukitsuki]

Amazing! This is the first time I have seen such a detailed video.

[@neddev2990]

You are so damn efficient at writing code! It's a pleasure to watch ;)

[@papacktrue]

Thank you! so helpfull!

[@CodingGarden]

Thanks for your support! 💚

[@ThomasPoth]

This video was very helpful for me. And there were no hiccups. I was able to code properly without any problems or weird bugs getting in my way. Thank you very much!

[@abeljr88]

I have set up my own boilerplate in the past using also vite and some linting packages. But this video is complete that it includes test packages for testing. Love it.

[@domoknows3275]

amazing tutorial. pretty much going to use this as my default starting vite project

[@davidaviles5032]

This was by far one of the most amazing videos I have ever seen. Setting up ESLint has been so foreign and walking through a good set up is much appreciated. I will say I had a lot of trouble configuring ESLint with Prettier This was because I had Prettier Extension installed as well as ESLint. I followed your steps but something was conflicting. I ended up turning off my Prettier Extension. Come to find out my formatting was not working and my prettier config file was not being recognized. I really do not know what. Everything worked when I added the prettier rules from my config file into my eslint config file, which according to docs, overrides prettier config file. So I ended up removing prettier config file, extended the prettier recommended as the video shown and any rules I did not like from the default linting rules for prettier formatting I added inside the prettier rules in the eslint file and everything worked as expected. For example JSX attributes would have double quotes fixed on save and js would allow single quotes. I know this was long but hope you read it and provide any insight you might have. Thnks again for the video

[@Hattrick249]

thank you for this video, really appreciate you taking the time to walk through everything! I'm working through The Odin Project and am currently on the React testing lessons. They teach you how to use create-react-app to build applications (which has Jest and the react testing library configured out of the box), but I much prefer Vite. This video includes everything that I need to know to still follow the curriculum despite the differences in tech used.

[@julianm786]

Thanks, I was struggling so much with the setup, you made it really easy

[@theprimecoder4981]

Thank you, I have been looking for this video for weeks.

[@tiagonobrega8046]

This video was extremely helpful to me. Thank you for the great content man, you covered a lot of stuff and explained it all in a way that it was easy to understand!

[@davidbrookoliver]

Valeu!

[@christiannikolov923]

So glad you uploaded it can't wait to get my hands on it.

[@angelhdzdev]

Hey CJ, we don't need Auto Rename Tag extension anymore! The setting is Enable Linked Editing. Same with Bracket Pair Colorizer, the setting is Bracket Pair Colorization. Cheers!

[@BenMakerProducer]

Nice video !! It would have been great to see more examples with TypeScript and react-router (loaders, react-query, params, matches, ...) 😁

[@dbmitrich]

Thank you for this guide! I found answers to some questions I had before.

[@Andrei-pq6qp]

This is gold. Excellent explanations. I love it.

[@zb2747]

Thank you for this video - would love more on formatting and linting configuration, CI/CD automation tools, and more on testing.

[@xxxMantou]

this is amazingly helpful setup tutorial, comfortable pace to follow alone!

[@AI-su3ds]

I'm happy I found your channel. Thank you for helpful videos

[@Fullflexno]

Love it! Great job, CJ!

[@paulraven8236]

nice! actually I came here to check my eslint config, but I'm vitesting now :D . I've never used testing libraries before, but man I'm hours just looking at dom checking accesibility and stuff. Thanks!! you improved my workflow :)

[@riendlyf]

I was looking for that setup!! Thanks!!

[@chuckydigitalworldwide]

That was amazing!! Thanks! Glad I found this channel

[@belaldif6689]

High quality content, we are looking for the next: React-testing-library 😁

[@whoa_dood]

Great Video CJ, thank you for all the hard work!

[@fernandoferrari9937]

congrats for the video, so instructional. i was looking for something like this.

[@rcchandan]

Reloading VS Code is so normal, Its now part of the development process 😂😂. Great content though, Helped me migrate a codebase from webpage to vite.

[@ievlevdmitriy]

Amazing! I've already shared this video to my friends. Thank you for your excellent job!

[@christopheraulotte5277]

Really great tutorial. You know your subject, you are cool and fun when you talk. Amazing, I recommend.

[@beakerbkr]

Fantastic content with great instruction!

[@endlessnameless3613]

Big thanks for this! It would be nice do the same but with webpack. I mean React app from scratch, without CRA💫

[@jonatankruszewski53]

Amazing resource! Any chance that the setting can be uploaded to the new eslint flat config? airbnb doesn't support the new format :(

[@kinglouis5190]

sir i love your turorial am your follower from cameroon

[@sanhvo6105]

i am beginner. Thank you so much for sharing this useful knowledge. This is wonderfull

[@sanjitselvan5348]

Thanks for this setup video!

[@stepo355]

Nice overview, thank you!

[@agustinperez8700]

This video is weasome, It has all the configurations that you always look for

[@djarma7980]

Thank you a lot of for saving my time😅, this video help me a lot!

[@sebastianchaca00]

I have type error on my vite react app but still working, how can I make it throw an error like CRA ? I followed your steps but I don't know how s supposed to work. Thanks

[@ArleiFerreiraFarnetaniJunior]

Congratulations and thanks a lot! 👊👊👊

[@jasonnares9634]

This is just amazing. Thank you so much.

[@itamar-jr-tech]

I am use BrowserRouter to work at the browser because I put a specific path, for example path='/login'. And work my test too

[@helloWorldPlus]

Something I would add is the import order. It takes some time to be doing the imports order manually.

[@flnnx]

That was very informative. Thanks

[@karlkrasnowsky3895]

2:04 ... By naming it react-ts-app it automatically created tsconfig for you and you weren't prompted if you wanted typescript or not? what sort of magic is this?

[@WaguanKing]

most video i watch abt that they are using mac os but im using windows sometimes while following up like when i want to use vite some files are missing and aloot of errors appears any advice

[@KikeVanegas23]

Great job!

[@tesohi]

jesus christ, it helped so much! I really thank you a lot!!

[@abuzain859]

Hey there! I watched your video and it is awesome . Now i am using the Vitest in my project but I am getting this error : ( Not implemented: window.computedStyle(elt, pseudoElt) at module.exports (C:\Users\Faizan\Desktop\full-stack ode_modules\jsdom\lib\jsdom\browser ot-implemented.js:9:17) )

[@3ggr]

awesome tutorial!🔥

[@ontheruntonowhere]

I like almost everything about this but I feel like the WrappedApp thing is not efficient or necessary. Otherwise BIG PROPS to you for putting this all together. I'm integrating much of this into my own boilerplate setup. 👍👍

[@adarshchhokar3818]

AYYY I LOVED THAT CATJAM

[@alexandr8151]

really useful video, thanks a lot!

[@SidneiMV]

Great job bro! video is liked.

[@karlkrasnowsky3895]

7:37 : Looks like the latest vite installer adds eslint by default.

[@gargantooga]

this is gold!

[@DmitriyLekomtsev]

Is there Vite template with all of this preconfigured?

[@Pouetpouets]

Thanks, helped me a lot

[@kabo123]

is this compatible with the add storybook command?

[@robmad0x]

I wholeheartly love this guy, just starting this type of project and this tutorial actually made it more managable and fun. Thanks a bunch my guy!🥲

[@michelmbili]

Is there any reason for using function App () {} instead of the arrow function ?

[@maplestoryinchinese]

Nope, only reason not to use an arrow function is when you're working with methods as using them would cause issues around the value of .this keyword

[@temurkhan9601]

very usefull video thank you for makin it. I have question I feel like I am following each steps one by one but somehow I still can manage to miss something or I dunno at some point I have a different result than the video. Can it be because now the codes changes a little or my previous setting are not allowing it or I am really missing something. Who else had a same issue ?

[@CodingGarden]

Sorry for the late reply. There were some breaking changes in version 6 of @testing-library/jest-dom I updated the template to include the fixes: github.com/CodingGarden/react-ts-starter/commit/a1b2aa106cacd5f2377a4b1800879e058e3bfe25

[@temurkhan9601]

@@CodingGarden u d man. Tyvm

[@danielpreza4159]

do you have pettier installed either like a dependency or as an extension as well?

[@CodingGarden]

I have it as both a dependency and extension. The npm dependency is used in conjunction with eslint for "eslint fix all auto fixable problems". If I want to format files manually without eslint, I can run "Format Document With -> Prettier" in VS Code (this uses the prettier extension only).

[@boyefrederic4716]

Hi @Coding garden! This is an amazing content. I have a question though, can we do this kind of config with a nexjts project too

[@CodingGarden]

You can definitely use eslint and prettier with next.js, but not vite (next.js uses swc under the hood - swc.rs/). You should also be able to use vitest and test-library with next.js

[@coderboysobuj]

Help -> React router dom with vite project doesn't work on server when i refresh the page, it's shows me server 404 page

[@Cognitoman]

Ohh so the public is like a place for images, videos audio etc… so that when when you build your files they are safe. If you were to put images in the assets folder they would get deleted every time during build time… I deleted that public folder… wonder if there is way to just ignore folders or files… in your assets folder so it doesn’t get deleted..

[@incacube]

great video for beginners like myself. i use prettier as extension in vscode, should i disable and use it as dependency?

[@CodingGarden]

I believe you need the extension installed for the eslint rules to work.

[@hjrr6471]

thank you for this kind vid

[@bahramsarafzadeh8250]

Nice! You're a life saver...

[@morpheusmatrix1073]

Hi great video ! But am getting some error. I choosed React at the first input, but the second just propose me javascript and typescript. So I choosed Javascript as variant. But am getting error in loading page "Failed to load module script: Expected a JavaScript module script but the server responded with a MIME type of "text/jsx". Strict MIME type checking is enforced for module scripts per HTML spec." Plz help

[@kennethmatov1546]

Very informative! Is there a way to automate all these initial setup steps?

[@CodingGarden]

You can click "use this template" on the github repo, or you can use a tool like degit. Repo is here: github.com/CodingGarden/react-ts-starter If you want to use degit, you can type "npx degit CodingGarden/react-ts-starter your-app-name", to create a folder with the base template.

[@kennethmatov1546]

@@CodingGarden Thank you so much.

[@Lucas-av7]

Thanks, dude!

[@jfeyers]

If anyone runs into an error (related to expect.extend(matchers);) in your jest setup upon running a test, change your matchers import to "import * as matchers from '@testing-library/jest-dom/matchers';"

[@dheerajs5774]

Tnx a lot man 🙏

[@nikhilpandeydigital]

Thank you so much

[@zaphry]

god is that you? came from the heavens to help us peasants???? love u

[@asyncawaited]

"This video is just starting, but you've probably been watching KZbin all day." Based.

[@Okir09]

In the .eslintcr.cjs i get : 'module' is not defined. :( :( :( please help :(

[@pkvpraveen]

When I converted all my jest based tests to vitest, It took a looong time to execute 😢

[@DARSHAN1212]

I 💌🍀Love Coding Garden!!

[@som3ah0]

wow super wow really for such content ... wish this channel get bigger and bigger bist wishes for you really ... thank you so mush pro

[@beshoosamy8452]

Amazing Video! Can you make a video about deploying vite app with react-router-dom 6.6+ to GitHub pages?

[@emil4483]

Are you perhaps planning to release an edited version of 'Intro to React with TypeScript' on KZbin? I noticed that you jumped from "Intro to TypeScript + Express" directly to "Setting up vite..." Thanks!

[@CodingGarden]

I plan to re-do it sometime this week using this template as a starter. Last time I got a bit in the weeds. However, the VOD will be available on the archive channel soon.

[@emil4483]

@@CodingGarden Great news ✨

[@emil4483]

@@CodingGarden 😅 Hey CJ, is it safe to assume at this time that this episode is unlikely to appear? Greetings

[@NewtonJR1987]

Hey, thank you so much for the video, it's amazing. I'm having some trouble on this part 14:24 when we add the eslint parse option project: './tsconfig.json' In the same file (.eslintrc) the module declaration on top of the file says: Parsing error: Cannot read file 'tsconfig.json', and in the every other file on the first line. But the tsconfig file is in the root folder of the project, I don't know what to do now, can you help? EDIT: Oops, just found the answer from another user on the comments below: replace the project key from parserOptions with: project: ...... for tsconfigRootDir: __dirname

[@quickguidesbynatanoob9867]

Can this also be used in JS react not TS? thanks

[@CodingGarden]

Yes that is possible. The airbnb setup would be slightly different but it is possible.

[@GMEveryday]

@@CodingGarden my biggest problem with vite react is it doesn't show errors on vscode terminal you have to constantly open browser console to see the problem. For beginners like me, it's time consuming. You know any work around with that?

[@Krzysiekoy]

10:01 - notice the squiggly line under module.exports on line 1. The error says: "module' is not defined. (eslint no-undef)". Holy shit, I was stuck on this for so long and it was so frustrating. What is so frustrating about this is that this file was created AUTOMATICALLY by using the official vite documentation (the command is yarn create vite your-app-name --template react-ts). I didn't touch shit, this is all created automatically, yet it still has an error... The app works even with this squiggly line but it is so frustrating because you think you have done something wrong. Another pain point is that there is no one obvious way to solve this. The error go away if you do one of the following: - remove eslint:recommended - replace eslint:recommended with something else (e.g. airbnb, like shown in this video) - change file extension from .cjs to .js - add node:true to the "env" object. Why does it have to be like that? How come that the official starter template comes with an error only for me to pull my hair out. /rant over

[@CodingGarden]

Yeah it is a bit frustrating when a freshly generated app gives errors like this. I just created an issue and opened a PR against vite to fix this in newly generated react apps. github.com/vitejs/vite/issues/13517 github.com/vitejs/vite/pull/13518

[@Krzysiekoy]

@@CodingGarden Wow, that is so cool, didn't think you'd take your time to respond since this is an old-ish video. Thanks, man, you rock!!!

[@ОксанаКраснодемская-у7з]

Thank you!!!

[@yolla_4]

what font are you using?

[@CodingGarden]

Anonymous Pro - more info here: github.com/CodingGarden/vscode-settings#font

[@azamatcto]

where is placed expect() function

[@thibao8726]

thanks bro , you can help how can you show Emoji 8:05 same you

[@Californ1a]

Personally not a huge fan of Prettier. Quite a few of the opinions in it don't match my preferred eslint configs, so format on save always ends up making eslint complain if I use Prettier, especially for stuff like arrow functions or ternaries (when to line break, place ? and : at start or end of line, use or don't use extra indent when nested, etc.). For that reason I've been using HookyQR's Beautify, but it hasn't been updated in over 3 years (so I've largely just been using the built-in formatter, since vscode 1.63.2 in Nov 2021 with the multi-language syntax) - I really wish there was a beautify/prettier-type of extension that just used your eslint config rather than their own opinions and much smaller list of options. There is Prettier ESLint, which just runs prettier and then eslint --fix, but that seems like a poor workaround for something that should just be built into the base formatting extension itself, using the actual eslint config for the formatting, rather than needing to format it twice. I'd essentially want the opposite of eslint-config-prettier, instead of disabling eslint rules to fit prettier, I'd want to override prettier rules to match eslint. The built-in formatter's been doing alright for me though.

[@runningtractor]

eslint-plugin-prettier vs. prettier-eslint, which one is the best? another video about setting prettier-eslint?

[@CodingGarden]

eslint-plugin-prettier adds rules to your eslint config that correspond to prettier formatting rules, so when you run "eslint fix all auto fixable problems", it using prettier rules to auto fix things in a single command. prettier-eslint is separate from eslint and is a 2 part process. It first runs prettier to format your files and then "eslint fix all auto fixable problems". You can read more about this here: prettier.io/docs/en/integrating-with-linters.html

[@alext5497]

Just don't use prettier. Easy