---
title: Troubleshooting
---

These are some troubleshooting tips for more common issues people might run into while developing, including more information on what might be happening and how to fix the problem.

- [Errors running scripts (e.g. `npm install`)](#errors-running-scripts-eg-npm-install)
- [Visual Studio (VS) Code formatting issues](#visual-studio-vs-code-formatting-issues)

## Errors running scripts (e.g. `npm install`)

Make sure you've followed the instructions for [Setup and development](development.md). If you already have, try deleting the `node_modules` folder and installing fresh:

```bash
# 1. Delete all previously-installed dependencies.
rm -rf node_modules

# 2. Delete package-lock.json
rm -rf package-lock.json

# 3. Install dependencies fresh.
npm install
```



## Visual Studio (VS) Code formatting issues

If you're using VS Code and notice that some files are being formatted incorrectly on save, the source is probably a formatter extension you've installed. The reason you're seeing it now is that this project enables the `editor.formatOnSave` setting. Previously, that extension was probably just doing nothing. To fix the problem, you'll need to either properly configure the extension or, if it's simply broken, uninstall it.

Extensions with known issues include:

- [Visual Studio Code Format](https://marketplace.visualstudio.com/items?itemName=ryannaddy.vscode-format#review-details)

Although we have added `\* text=auto eol=lf` to the repo's `.gitattributes` file to achieve this, if Windows users are still having problems they should run git config core.autocrlf false before working on the repo so that git does not convert `LF` to `CRLF` on checkout.