eslint-config-wpcalypso
Advanced tools
ESLint configuration following WordPress.com's Calypso JavaScript Coding Guidelines
An ESLint configuration following WordPress.com's "Calypso" JavaScript Coding Guidelines.
You should install this configuration and peer dependencies as devDependencies in your project:
yarn add --dev eslint-config-wpcalypso eslint eslint-plugin-wpcalypso
If you're planning to use the React superset of rules, you should also install eslint-plugin-react:
yarn add --dev eslint-plugin-react
Next, simply extend the configuration from your project's .eslintrc file:
"extends": "wpcalypso"
Or, if your project uses React and you want to opt in to additional React-specific rules, extend the React superset:
"extends": "wpcalypso/react"
Refer to the ESLint documentation on Shareable Configs for more information.
Want to suggest a change to our style guide? Edit the JavaScript Coding Guidelines on the Automattic/wp-calypso repository and submit a pull request.
Want to revise the ESLint rules used here? Edit the index.js file and submit a pull request.
FAQs
ESLint configuration following WordPress.com's Calypso JavaScript Coding Guidelines
The npm package eslint-config-wpcalypso receives a total of 5,425 weekly downloads. As such, eslint-config-wpcalypso popularity was classified as popular.
We found that eslint-config-wpcalypso demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 43 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security Fundamentals
The Socket Threat Research Team uncovers how threat actors weaponize shell techniques across npm, PyPI, and Go ecosystems to maintain persistence and exfiltrate data.
Security News
At VulnCon 2025, NIST scrapped its NVD consortium plans, admitted it can't keep up with CVEs, and outlined automation efforts amid a mounting backlog.
Product
We redesigned our GitHub PR comments to deliver clear, actionable security insights without adding noise to your workflow.