
Research
NPM targeted by malware campaign mimicking familiar library names
Socket uncovered npm malware campaign mimicking popular Node.js libraries and packages from other ecosystems; packages steal data and execute remote code.
@mapbox/eslint-config-mapbox
Advanced tools
Shared ESLint config for Mapbox engineering teams.
Install the following dev-dependencies:
npm install --save-dev \
@mapbox/eslint-config-mapbox
Extend the @mapbox/eslint-config-mapbox
config in your .eslintrc
(or eslintConfig
key in your package.json
):
"eslintConfig": {
"extends": "@mapbox/eslint-config-mapbox"
}
For TypeScript, prefer .eslint.js
and use the snippet below:
'plugins': [
'@typescript-eslint',
'prettier'
],
'parserOptions': {
'tsconfigRootDir': __dirname
},
'extends': [
'@mapbox/eslint-config-mapbox/node20-typescript'
]
Specify the version of Node.js your project uses by setting .engines.node
in your package.json
, according to the settings you choose.
"engines": {
"node": ">=20"
}
Run eslint
on your project as part of your test
and lint
scripts:
"scripts": {
"lint": "eslint --ignore-path .eslintignore --ext .js,.ts .",
"test": "tape test/*.test.js && npm run lint",
}
The "Quick start" above exemplifies usage of this package with standard Node.js code.
Depending on the ECMAScript version of your code, whether you are using non-standard syntax like Flow and React's JSX, or other considerations, you may want to extend a variety of configurations provided by this package. eslint-config-mapbox
exposes several configurations targeting specific ESLint plugins, each named after the plugin it targets.
To use each plugin-specific configuration, you'll need to do the following:
Install as dev-dependencies @mapbox/eslint-config-mapbox
, eslint
, and any plugins that are used by the configuration(s) you are extending, such as eslint-plugin-node
or eslint-plugin-react
.
Add the configuration(s) you are using to the "extends"
array in your project's ESLint configuration, like this:
{
"extends": [
"@mapbox/eslint-config-mapbox/react",
"@mapbox/eslint-config-mapbox/import",
"@mapbox/eslint-config-mapbox/promise"
]
}
@mapbox/eslint-config-mapbox
/node
.engines.node
in your package.json
, or by extending an LTS-version-specific ESLint configuration: node10
, node12
, node14
, node14-typescript
, node20
, node20-typescript
.@mapbox/eslint-config-mapbox
/react
@mapbox/eslint-config-mapbox
/import
import
and export
).@mapbox/eslint-config-mapbox
/promise
Promise
s.@mapbox/eslint-config-mapbox
/xss
If you are using Prettier to format your JS, install eslint-config-prettier and add it at the end of your "extends"
array. It will turn off all ESLint rules related to the code-style preferences that Prettier already addresses.
FAQs
Generic eslint configuration for Mapbox
The npm package @mapbox/eslint-config-mapbox receives a total of 6,584 weekly downloads. As such, @mapbox/eslint-config-mapbox popularity was classified as popular.
We found that @mapbox/eslint-config-mapbox 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
Socket uncovered npm malware campaign mimicking popular Node.js libraries and packages from other ecosystems; packages steal data and execute remote code.
Research
Socket's research uncovers three dangerous Go modules that contain obfuscated disk-wiping malware, threatening complete data loss.
Research
Socket uncovers malicious packages on PyPI using Gmail's SMTP protocol for command and control (C2) to exfiltrate data and execute commands.