eslint-config-amo
Advanced tools
Shared eslint config for all amo related JS projects.
This project follows the semantic versioning specification.
In order to release a new version, please follow these steps:
Make sure your local master branch is up-to-date.
Run the following command from the master branch to (1) bump the version accordingly and (2) create a commit and a tag for the release:
npm version minor
Note: change minor to patch or major depending on the release (but minor is the most frequent).
Push to the main repository (denoted upstream below):
git push upstream master --tag
Create a GitHub Release for the new tag: https://github.com/mozilla/eslint-config-amo/releases (you can either select the tag itself or create a new "draft"). Please add a short description of the changes (see the other releases for inspiration).
FAQs
Eslint config for amo based projects
The npm package eslint-config-amo receives a total of 163 weekly downloads. As such, eslint-config-amo popularity was classified as not popular.
We found that eslint-config-amo demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 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.
Research
Security News
Malicious npm package postcss-optimizer delivers BeaverTail malware, targeting developer systems; similarities to past campaigns suggest a North Korean connection.
Security News
CISA's KEV data is now on GitHub, offering easier access, API integration, commit history tracking, and automated updates for security teams and researchers.
Security News
Opengrep forks Semgrep to preserve open source SAST in response to controversial licensing changes.