Static Analysis Testing JavaScript Applications
15 video lessons
43m of learning material
There are a ton of ways your application can break. One of the most common sources of bugs is related to typos and incorrect types. Passing a string to a function that expects a number, or falling prey to a common typo in a logical statement are silly mistakes that should never be made, but this happens all the time.
We could write a comprehensive suite of automated tests for our entire codebase to make certain mistakes like this never happen, but that would likely be too much work and slow development down to be worth the benefit. Luckily for us, there are tools like ESLint, TypeScript, Prettier, and more which we can use to satisfy a whole category of testing with a great developer experience.
lessons
1. Intro to Static Analysis Testing JavaScript Applications
Watch Lesson0m 59s2. Lint JavaScript by Configuring and Running ESLint
Watch Lesson4m 40s3. Use the ESLint Extension for VSCode
Watch Lesson1m 17s4. Use pre-built ESLint Configuration using extends
Watch Lesson2m 0s5. Run ESLint with npm Scripts
Watch Lesson2m 18s6. Format Code by Installing and Running Prettier
Watch Lesson2m 55s7. Configure Prettier
Watch Lesson2m 13s8. Use the Prettier Extension for VSCode
Watch Lesson1m 46s9. Disable Unnecessary ESLint Stylistic Rules with eslint-config-prettier
Watch Lesson2m 25s10. Validate All Files are Properly Formatted with Prettier
Watch Lesson3m 10s11. Avoid Common Errors by Installing and Configuring TypeScript
Watch Lesson5m 30s12. Make ESLint Support TypeScript Files
Watch Lesson5m 28s13. Validate Code in a pre-commit git Hook with husky
Watch Lesson2m 46s14. Auto-format All Files and Validate Relevant Files in a precommit Script with lint-staged
Watch Lesson4m 18s15. Run Multiple npm Scripts in Parallel with npm-run-all
Watch Lesson1m 16s