ESLint has a very lightweight development environment that makes updating code fast and easy. This is a step-by-step guide to setting up a local development environment that will let you contribute back to the project.
Go to https://nodejs.org/ to download and install the latest stable version for your operating system.
Most of the installers already come with npm but if for some reason npm doesn't work on your system, you can install it manually using the instructions on the site.
Once you've cloned the repository, run
npm install to get all the necessary dependencies:
$ cd eslint $ npm install
You must be connected to the Internet for this step to work. You'll see a lot of utilities being downloaded.
The upstream source is the main ESLint repository where active development happens. 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.
To add the upstream source for ESLint, run the following in your repository:
git remote add upstream [email protected]:eslint/eslint.git
Now, the remote
upstream points to the upstream source.
Yeoman is a scaffold generator that ESLint uses to help streamline development of new rules. If you don't already have Yeoman installed, you can install it via npm:
npm install -g yo
Then, you can install the ESLint Yeoman generator:
npm install -g generator-eslint
Please see the generator documentation for instructions on how to use it.
Running the tests is the best way to ensure you have correctly set up your development environment. Make sure you're in the
eslint directory and run:
The testing takes a few minutes to complete. If any tests fail, that likely means one or more parts of the environment setup didn't complete correctly. The upstream tests always pass.
Once you have your development environment installed, you can make and submit changes to the ESLint source files. Doing this successfully requires careful adherence to our pull-request submission workflow.
ESLint has several build scripts that help with various parts of development.
The primary script to use is
npm test, which does several things:
build/eslint.jsfor use in a browser
Be sure to run this after making changes and before sending a pull request with your changes.
Note: The full code coverage report is output into
build/eslint.js, a version of ESLint for use in the browser
Generates JSDoc documentation and places it into
This command is used for intensive profiling of ESLint using Chrome Developer Tools. It starts a development server that runs through three profiles:
Your browser should automatically open to the page in question. When that happens:
You should start to see profiles for each run show up on the left side. If not, reload the page in the browser. Once all three profiles have completed, they will be available for inspection.
© JS Foundation and other contributors
Licensed under the MIT License.