
Security Fundamentals
Turtles, Clams, and Cyber Threat Actors: Shell Usage
The Socket Threat Research Team uncovers how threat actors weaponize shell techniques across npm, PyPI, and Go ecosystems to maintain persistence and exfiltrate data.
@synatic/eslint-config-synatic-node
Advanced tools
Global repo for how code should be linted and styled
Global repo for how linting and code styling should be done for Synatic projects.
In the root of the project is a .eslintrc.json
file, this is where the majority of the rules, plugins and config will live and where you should primarily be making changes. The base file is for node projects that use mocha. You can test out changes to the base config by adding code to the ./lib-examples/
folder and your editor should be able to pick up any issues with the code which will allow you to refine the rules and verify that they work the way you would like them too.
Once you have the rules setup the way you would like to you can run the npm run copy
command and this will take the config in the .eslintrc.json
file and copy it to ./lib/index.js
where it will be used in other projects once published.
The library also supports more advanced configuration for other project types, for example projects that use jest can make use of both the base configuration file in the root together with the jest specific config in ./lib/jest.js
by having their project extend @synatic/eslint-config-synatic-node/lib/jest
. Currently there is no way to test these specific configurations in this project without copying them to the .eslintrc.json
file and testing them, but do not leave them there when committing or else they will apply to the shared base configuration.
Once you have made all the above changes and ran the npm run copy
command you can commit to git
run the npm version <major,minor,patch>
command to increment the version, push to develop and submit a PR as normal.
To add the shared configuration to your project you can do the following:
npm i -D @synatic/eslint-config-synatic-node
in your project.eslintrc.json
file in your project{
"env": {},
"extends": ["@synatic/eslint-config-synatic-node"],
"globals": {},
"parserOptions": {},
"overrides": [],
"rules": {}
}
extends
in the above example with your desired one..prettierrc.json
in your project and inside it add the code from this repositories version of the file as this will be the most up to date versionpackage.json
file, which can be found under peerDependencies
"engines": {
"node": ">=14.0.0",
"npm": ">=6.0.0"
},
"lint": "eslint .",
"lint-fix": "eslint . --fix",
"lint-errors": "eslint . --quiet",
"prettier": "prettier . --write"
FAQs
Global repo for how code should be linted and styled
The npm package @synatic/eslint-config-synatic-node receives a total of 427 weekly downloads. As such, @synatic/eslint-config-synatic-node popularity was classified as not popular.
We found that @synatic/eslint-config-synatic-node demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 3 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.
Security Fundamentals
The Socket Threat Research Team uncovers how threat actors weaponize shell techniques across npm, PyPI, and Go ecosystems to maintain persistence and exfiltrate data.
Security News
At VulnCon 2025, NIST scrapped its NVD consortium plans, admitted it can't keep up with CVEs, and outlined automation efforts amid a mounting backlog.
Product
We redesigned our GitHub PR comments to deliver clear, actionable security insights without adding noise to your workflow.