Security News
JSR Working Group Kicks Off with Ambitious Roadmap and Plans for Open Governance
At its inaugural meeting, the JSR Working Group outlined plans for an open governance model and a roadmap to enhance JavaScript package management.
eslint-plugin-escompat
Advanced tools
This plugin will report eslint errors for code which - if left untranspiled - will not work in some browsers.
This plugin will report eslint errors for code which - if left untranspiled - will not work in some browsers.
This is useful if you intend to ship code without first using a transpiler, such as Babel.
This won't lint for features that can be polyfilled. For that you can use eslint-plugin-compat.
npm install --save-dev eslint-plugin-escompat
Add "escompat"
to .eslintrc
"plugins"
section, add "browser": true
to "env"
, then configure the individual "escompat/*"
rules.
Alternatively, you can use the recommended
configuration which will do this for you, with the "escompat/*"
rules reporting errors (as in the snippet above).
// .eslintrc
{
"extends": ["plugin:escompat/recommended"]
}
Aside from the recommended
config, there is also the typescript
config which can be used if you're using TypeScript. The TypeScript config only enables some of the rules, avoiding enabling rules for which typescript
safely transpiles down to a more compatible syntax. To enable the typescript
config, simply add the following to your eslint config:
// .eslintrc
{
"extends": ["plugin:escompat/typescript"]
}
eslint-plugin-escompat
uses the browserslist
configuration in package.json
If you have a browserlist, is is safe to enable all of these rules - as any that do not coincide with your chosen browsers will be turned off automatically.
See browserslist/browserslist for configuration. Here's some examples:
// Simple configuration (package.json)
{
// ...
"browserslist": ["last 1 versions", "not ie <= 8"],
}
// Use development and production configurations (package.json)
{
// ...
"browserslist": {
"development": ["last 2 versions"],
"production": ["last 4 versions"]
}
}
:bulb: You can also define browsers in a separate browserslist file
✔️ = enabled in plugin:escompat/recommended
config.
🔹 = enabled in plugin:escompat/typescript
config.
This project was largely inspired by the great eslint-plugin-compat library.
FAQs
This plugin will report eslint errors for code which - if left untranspiled - will not work in some browsers.
The npm package eslint-plugin-escompat receives a total of 69,764 weekly downloads. As such, eslint-plugin-escompat popularity was classified as popular.
We found that eslint-plugin-escompat demonstrated a healthy version release cadence and project activity because the last version was released less than 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
At its inaugural meeting, the JSR Working Group outlined plans for an open governance model and a roadmap to enhance JavaScript package management.
Security News
Research
An advanced npm supply chain attack is leveraging Ethereum smart contracts for decentralized, persistent malware control, evading traditional defenses.
Security News
Research
Attackers are impersonating Sindre Sorhus on npm with a fake 'chalk-node' package containing a malicious backdoor to compromise developers' projects.