We have a few checks we’ll run in continuous integration when someone opens a pull request, but it’d be even better if we could run some of those checks before they even commit their code so they can fix it right away rather than waiting for CI to run. Let’s use husky’s precommit script to run our validation.

Static Analysis Testing JavaScript Applications

Validate Code in a pre-commit git Hook with husky

Instructor: [00:00] As cool as it is that we can run our `"validate"` script and make sure that we're not making any mistakes, it would be really nice if we could just make sure that always happens before somebody commits any code. That way, they don't commit code that violates any of these things that we've set in place.

[00:15] To make that happen, I'm going to `npm install` as a dev dependency `husky`. Husky, actually does something interesting when it installs by doing this setting up `Git hooks`. It's not showing up in here because I've hidden those files.

### Terminal
![husky install message](https://res.cloudinary.com/dg3gyk0gu/image/upload/v1574890640/transcript-images/javascript-validate-code-in-a-pre-commit-git-hook-with-husky-2d052239-husky-install.jpg)

[00:28] If you take a look at the directory structure here, we're going to see there's a `.gitdirectory`. If we take a look at what's in there, we'll see `.git`. In there, there's a `hooks` directory, inside of the `hooks` directory, there are whole bunch of files, which Husky just created for us.

### Terminal Input
```
ls -a
ls -a .git
ls -a .git/hooks
```

[00:44] Let's go ahead and we'll take a look at one of those files. `.git/hooks` and then we'll do `/pre-commit`. This is what Husky puts in that file. It might be a little bit much to take in, but basically, what this does is enable what we're about to do.

### Terminal Input
```
cat .git/hooks/pre-commit
```

[00:59] I'm going to create a `.huskyrc` file. Here we have this `"hooks"`. We'll specify `"pre-commit"`, `"npm run validate"`. What this is going to do is that hooks directory is built into Git Anytime you do a commit, Git is going to run that `pre-commit` script that's in that hooks directory. That `pre-commit` script that Husky created for us is actually going to look up this configuration and run this script that we have here.

### .huskyrc
```
{
  "hooks": {
    "pre-commit": "npm run validate"
  }
}
```

[01:30] Let's go ahead and try that. We'll do `git add` all this stuff and we'll `git commit 'husky rocks'`. You'll see that it's going to run our `pre-commit` script, which is running the `"validate"` script. Because that `"validate"` script past, we were able to create the commit.

[01:48] If we tried to do something that is incorrect, like maybe we have some type of problem here and we try to commit that mess up, then it's going to run our `"validate"` script. It's going to fail. It says `pre-commit` hook failed, and so the commit wasn't created.

### Terminal
![pre-commit fails](https://res.cloudinary.com/dg3gyk0gu/image/upload/v1574890643/transcript-images/javascript-validate-code-in-a-pre-commit-git-hook-with-husky-2d052239-pre-commit-fails.jpg)

[02:04] If we just want to make this commit, then we can add the no verify flag to bypass this. We can add a `--no-verify`, and we're able to create the commit without running our pre commit script. Most of the time, you're probably going to want that `"validate"` script to pass.

### Terminal Input
```
git commit -am ‘mess-up’ —no-verify
```

[02:19] In review, to make all this work, we added `husky` as a dependency in our `devDependencies`. Then we added a `.huskyrc` file, which defines our hooks and our `pre-commit` script. The script that we want to have run before we commit any code is `npm run validate`.

[02:37] There are other scripts that you can run in here. I recommend that you just take a look at the `git/hooks` directory. You'll see all of the different scripts that you can use with husky.

### Terminal
![husky hook scripts](https://res.cloudinary.com/dg3gyk0gu/image/upload/v1574890640/transcript-images/javascript-validate-code-in-a-pre-commit-git-hook-with-husky-2d052239-hooks-scripts.jpg)


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.

Intro to Static Analysis Testing JavaScript Applications

The static code analysis and linting tool ESLint is the de-facto standard for linting JavaScript projects. In this lesson we’ll see how to install, run, and configure it for your preferences.

Lint JavaScript by Configuring and Running ESLint

Whatever editor you use, chances are there’s probably some plugin or extension you can use to integrate ESLint and your editor to get a nice in-editor experience using ESLint so you don’t have to run the ESLint script to check your code and instead can identify issues as you’re writing and editing your code. Let’s take a look at what you can do with [the ESLint Extension for VSCode](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint).

Use the ESLint Extension for VSCode

ESLint has [a TON of rules](https://eslint.org/docs/rules/) you can configure for your project. But who has time to do all that? This is why ESLint has an extends configuration which you can use to base your own configuration off of other configurations. Let’s add all of ESLint’s built-in recommended rules to our project and override just the ones we want to change.

Use pre-built ESLint Configuration using extends

Let’s add an npm script called lint so we can run ESLint whenever we want with the proper command line flags.

Run ESLint with npm Scripts

The code formatting tool [prettier](https://prettier.io/) can help you avoid a lot of useless time spent formatting code and arguing about code formatting with your co-workers. It can also help you catch subtle issues with your code that you may not notice otherwise. In this lesson we’ll learn how to install and run prettier.

Format Code by Installing and Running Prettier

1. Prettier is a pretty opinionated tool, but it does allow for some customization. In this lesson we’ll check out [the prettier playground](https://prettier.io/playground/) and see what options we want to enable in our project’s `.prettierrc` file. 
2. After adding in our custom configuration, we’ll create a `.prettierignore` file so that you can avoid formatting any files generated within the project such as `node_modules` or a `build` folder.

Configure Prettier

Running prettier manually is great, but it’d be even better if we could just run prettier anytime we save our file. Whatever editor you use, there’s likely a plugin or extension for it to integrate with prettier. Let’s try out [the Prettier Extension for VSCode](https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode).

Use the Prettier Extension for VSCode

Because prettier can automatically fix a lot of stylistic issues in our codebase, it’s not necessary to have eslint check for those and it can actually be kind of annoying if it does. So let’s see how we can use eslint-config-prettier to disable all rules that are made irrelevant thanks to prettier.

Disable Unnecessary ESLint Stylistic Rules with eslint-config-prettier

1. You can’t force everyone on your project to use the prettier integration for their editor, so let’s add a validation script to verify that prettier has been run on all project files.
2. Fortunately for us, Prettier accepts a `--list-different` flag that you can use that will throw an error when code is not up to the standard of your project.

Validate All Files are Properly Formatted with Prettier

ESLint can check for a lot of things, but it’s not a great tool for checking the types of variables that flow through your application. For this you’ll need a type-checking tool like [Flow](https://flow.org/) or [TypeScript](https://www.typescriptlang.org/). Let’s see how we can configure our project to work with TypeScript.

Avoid Common Errors by Installing and Configuring TypeScript

ESLint does not have support for TypeScript out of the box, but luckily adding support for TypeScript is straightforward thanks to the [TypeScript-ESLint](https://typescript-eslint.io/) project. And now that we have TypeScript, there are a lot of rules that we don’t need ESLint to bother checking because TypeScript will prevent those problems in the first place! Let’s get these two tools integrated.

Make ESLint Support TypeScript Files

Rather than failing when a developer has failed to format their files or run linting on all the files in the project on every commit, it would be even better to just automatically format the files on commit and only check the relevant files with eslint. Let’s use lint-staged to run scripts on the files that are going to be committed as part of our precommit hook.

Auto-format All Files and Validate Relevant Files in a precommit Script with lint-staged

I use npm scripts a lot, and that validate script is a great way to bring everything together. But with the way these tools work, we can run them all at the same time and things will work just as well. This will speed up our script runtime a lot, so let’s use [npm-run-all](https://npm.im/npm-run-all) to make that happen.

Validate Code in a pre-commit git Hook with husky

Transcript

Validate Code in a pre-commit git Hook with husky