Skip to content

Commit

Permalink
Docs: Add instruction re home-directory config files (refs #7729) (#9426
Browse files Browse the repository at this point in the history
)

Without this, config file in home directory makes 1 test fail.
  • Loading branch information
jrpool authored and not-an-aardvark committed Oct 13, 2017
1 parent 30d018b commit f7ed84f
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions docs/developer-guide/development-environment.md
Expand Up @@ -21,6 +21,8 @@ $ npm install

You must be connected to the Internet for this step to work. You'll see a lot of utilities being downloaded.

If you have an ESLint configuration file in your home directory (such as `~/.eslintrc.js`), either delete or rename it. This will help ensure that all the tests in Step 5 pass. It will also prevent ESLint from running with an incorrect configuration in case the configuration file in your development environment becomes misnamed, moved, or deleted.

## Step 3: Add the upstream source

The *upstream source* is the main ESLint repository that active development happens on. While you won't have push access to upstream, you will have pull access, allowing you to pull in the latest code whenever you want.
Expand Down

0 comments on commit f7ed84f

Please sign in to comment.