Ecosystem Tests

These tests run notable community plugins against the local ESLint repository. They're meant to validate that current changes to ESLint won't break downstream consumers.

Running

To build and test all plugins:

npm run test:ecosystem

To run on just one plugin:

npm run test:ecosystem -- --plugin <plugin-name>

Plugins are stored in plugins-data.json. Plugin names are keys from that file. For example, to test against @eslint/css:

npm run test:ecosystem -- --plugin @eslint/css

Debugging Commands

The debug package is used to surface the stdout of commands when DEBUG=test:ecosystem is enabled.

DEBUG=test:ecosystem npm run test:ecosystem -- --plugin @eslint/css

Updating

plugins-data.json contains pinned commit hashes for each repository. Those hashes can be updated with the same script run in CI.

To update all plugins:

npm run test:ecosystem:update

To update just one plugin:

npm run test:ecosystem:update -- --plugin <plugin-name>