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.
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!
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
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!
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.
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!
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
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';"
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.
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!
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.
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 :)
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!
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. 👍👍
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..
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
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
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) )
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?
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.
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 ?
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
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
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
Are you perhaps planning to release an edited version of 'Intro to React with TypeScript' on RU-vid? I noticed that you jumped from "Intro to TypeScript + Express" directly to "Setting up vite..." Thanks!
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.
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
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.
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
