Installations

npm install eslint-plugin-es

Pull Requests

Open

13

Total

48

Closed

7

Merged

28

Issues

Open

24

Total

46

Closed

22

Releases

13

v4.1.0

Published on 03 Dec 2020

v4.0.0

Published on 19 Nov 2020

v3.0.1

Published on 15 May 2020

v3.0.0

Published on 26 Dec 2019

v2.0.0

Published on 02 Sept 2019

v1.4.1

Published on 02 Sept 2019

View all 13 releases

Developer

mysticatea

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

>=8.10.0

Typescript Support

No

Node Version

15.2.0

NPM Version

6.14.8 Statistics

108 Stars

136 Commits

21 Forks

5 Watching

2 Branches

8 Contributors

Updated on 05 Sept 2024

Bundle Size

137.39 kB

Minified

26.16 kB

Minified + Gzipped

Bundlephobia

Languages

JavaScript (100%)

Total Downloads

Cumulative downloads

Total Downloads

867,732,728

Last day

-8.7%

905,786

Compared to previous day

Last week

1.6%

5,376,140

Compared to previous week

Last month

19.9%

21,404,230

Compared to previous month

Last year

1.8%

234,565,087

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

2

eslint-utils regexpp

Peer Dependencies

1

eslint

Dev Dependencies

17

@mysticatea/eslint-plugin @vuepress/plugin-pwa acorn babel-eslint codecov eslint eslint4b espree globals mocha npm-run-all nyc opener rimraf semver vue-eslint-editor vuepress

Versions

eslint-plugin-es

ESLint plugin which disallows each ECMAScript syntax.

🏁 Goal

Espree, the default parser of ESLint, has supported ecmaVersion option. However, the error messages of new syntax are not readable (e.g., "unexpected token" or something like).

When we use this plugin along with the latest ecmaVersion option value, it tells us the readable error message for the new syntax, such as "ES2020 BigInt is forbidden." Plus, this plugin lets us disable each syntactic feature individually.

📖 Usage

See documentation

🚥 Semantic Versioning Policy

This plugin follows semantic versioning and ESLint's semantic versioning policy.

We will release a new minor version to add new rules when TC39 decided to advance proposals to Stage 4. In the minor releases, we don't update configs.
We will release a new major version to update configs when new ECMAScript snapshots are available.

📰 Changelog

See releases.

❤️ Contributing

Welcome contributing!

Please use GitHub's Issues/PRs.

Development Tools

npm test runs tests and measures coverage.
npm run clean removes the coverage result of npm test command.
npm run coverage shows the coverage result of the last npm test command.
npm run docs:build builds documentation.
npm run docs:watch builds documentation on each file change.
npm run watch runs tests on each file change.

No vulnerabilities found.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

10

License

Determines if the project has defined a license.

4

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Maintained

Determines if the project is "actively maintained".

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

Security-Policy

Determines if the project has published a security policy.

0

SAST

Determines if the project uses static code analysis.

Score

3.8

/10

Last Scanned on 2024-11-25

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More