Security News
Cloudflare Adds Security.txt Setup Wizard
Cloudflare has launched a setup wizard allowing users to easily create and manage a security.txt file for vulnerability disclosure on their websites.
neostandard
Advanced tools
standard
npm install -D neostandard eslint
npx neostandard --migrate > eslint.config.js
(uses our config helper)standard
with eslint
in all places where you run standard
, eg. "scripts"
and .github/workflows/
(neostandard
CLI tracked in #2)npm uninstall standard
"standard"
top level key from your package.json
standard
specific integrations if you no longer use them (eg. vscode-standard))npm install -D neostandard eslint
Add an eslint.config.js
:
Using config helper:
npx neostandard --esm > eslint.config.js
Or to get CommonJS:
npx neostandard > eslint.config.js
Or manually create the file as ESM:
import { neostandard } from 'neostandard'
export default neostandard({
// options
})
Or as CommonJS:
module.exports = require('neostandard')({
// options
})
Run neostandard
by running ESLint, eg. using npx eslint
, npx eslint --fix
or similar
env
- string[]
- adds additional globals by importing them from the globals npm modulefiles
- string[]
- additional file patterns to match. Uses the same shape as ESLint files
filesTs
- string[]
- additional file patterns for the TypeScript configs to match. Uses the same shape as ESLint files
globals
- string[] | object
- an array of names of globals or an object of the same shape as ESLint languageOptions.globals
ignores
- string[]
- an array of glob patterns for files that the config should not apply to, see ESLint documentation for detailsnoStyle
- boolean
- if set, no style rules will be added. Especially useful when combined with Prettier, dprint or similarsemi
- boolean
- if set, enforce rather than forbid semicolons (same as semistandard
did)ts
- boolean
- if set, TypeScript syntax will be supported and *.ts
(including *.d.ts
) will be checked. To add additional file patterns to the TypeScript checks, use filesTs
Finds a .gitignore
file that resides in the same directory as the ESLint config file and returns an array of ESLint ignores that matches the same files.
ESM:
import neostandard, { resolveIgnoresFromGitignore } from 'neostandard'
export default neostandard({
ignores: resolveIgnoresFromGitignore(),
})
CommonJS:
module.exports = require('neostandard')({
ignores: require('neostandard').resolveIgnoresFromGitignore(),
})
neostandard
exports all the ESLint plugins that it uses. This to ensure that users who need to reference the plugin themselves will use the exact same instance of the plugin, which is a necessity when a plugin prefix is defined in multiple places.
@stylistic
- export of @stylistic/eslint-plugin
@typescript-eslint
- export of @typescript-eslint/eslint-plugin
n
- export of eslint-plugin-n
promise
- export of eslint-plugin-promise
If one eg. wants to add the eslint-plugin-n
recommended config, then one can do:
import neostandard, { plugins } from 'neostandard'
export default [
...neostandard({
ignores: resolveIgnoresFromGitignore(),
}),
plugins.n.configs['flat/recommended'],
]
eslint-plugin-import
rules from standard
: #15neostandard
runner: #33 / #2Full list in 1.0.0 milestone
standard-engine
.ts
as option in main packagesemistandard
as option in main packageeslint-stylistic
instead of deprecated ESLint style ruleseslint-config-prettier
anymore)@stylistic/comma-dangle
– changed – set to prefer dangling commas in everything but functions and is it set to warn
rather than error
@stylistic/no-multi-spaces
– changed – sets ignoreEOLComments
to true
, useful for aligning comments across multiple linedot-notation
– deactivated – clashes with the noPropertyAccessFromIndexSignature
check in TypeScriptn/no-deprecated-api
– changed – changed to warn
instead of error
as they are not urgent to fixeslint-plugin-import
You can use the provided CLI tool to generate a config for you:
neostandard --semi --ts > eslint.config.js
To see all available flags, run:
neostandard --help
The CLI tool can also migrate an existing "standard"
configuration from package.json
:
neostandard --migrate > eslint.config.js
Migrations can also be extended, so to eg. migrate a semistandard
setup, do:
neostandard --semi --migrate > eslint.config.js
Yes! If you use neostandard
in your project, you can include one of these badges in
your readme to let people know that your code is using the neostandard style.
[![neostandard javascript style](https://img.shields.io/badge/neo-standard-7fffff?style=flat&labelColor=ff80ff)](https://github.com/neostandard/neostandard)
[![neostandard javascript style](https://img.shields.io/badge/code_style-neostandard-7fffff?style=flat&labelColor=ff80ff)](https://github.com/neostandard/neostandard)
[![neostandard javascript style](https://img.shields.io/badge/code_style-neostandard-brightgreen?style=flat)](https://github.com/neostandard/neostandard)
FAQs
A modern successor to standard
The npm package neostandard receives a total of 11,258 weekly downloads. As such, neostandard popularity was classified as popular.
We found that neostandard demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 4 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 News
Cloudflare has launched a setup wizard allowing users to easily create and manage a security.txt file for vulnerability disclosure on their websites.
Security News
The Socket Research team breaks down a malicious npm package targeting the legitimate DOMPurify library. It uses obfuscated code to hide that it is exfiltrating browser and crypto wallet data.
Security News
ENISA’s 2024 report highlights the EU’s top cybersecurity threats, including rising DDoS attacks, ransomware, supply chain vulnerabilities, and weaponized AI.