eslint-plugin-no-bad-map-access
Advanced tools
An ESLint rule that uses TypeScript plugin to check if an ES6 Map is being accessed incorrectly. Also looks for {} as Map, which is not a valid cast
npm install eslint-plugin-no-bad-map-access --save-dev
Add the following to your .eslintrc.json:
"rules": {
...
"no-bad-map-access/no-bad-map-access": "error"
}
...
"plugins": [
...
"no-bad-map-access"
]
npm install
npm run build
npm run test
FAQs
Linter rules that flag incorrect ES6 Map access
We found that eslint-plugin-no-bad-map-access demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer 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 News
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
Security News
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.
Security News
Node.js will be enforcing stricter semver-major PR policies a month before major releases to enhance stability and ensure reliable release candidates.