This major release fully focuses on getting in sync with the wider ESLint ecosystem
and doesn't in itself introduce any new rules or features.
When you upgrade, consider running standard --fix to automatically format your
code to match the current set of rules.
This is the first release by two of our standard co-maintainers @Divlo and @voxpelli. Buy them a cake if you run into them, thanks for getting this release out!
Major changes
eslint-config-node has been replaced with the up to date fork eslint-config-n. If you have used comments like // eslint-disable-line node/no-deprecated-api you now have to reference the n/ rules instead.
Introduce "warning" system for disruptive rules (read more below)
Change rule to a "warning": Require let or const instead of var (no-var) #633
standard treats all rule violations as errors, which means that standard
will exit with a non-zero (error) exit code.
However, we may occasionally release a new major version of standard
which changes a rule that affects the majority of standard users (for example,
transitioning from var to let/const). We do this only when we think the
advantage is worth the cost and only when the rule is auto-fixable.
In these situations, we have a "transition period" where the rule change is only
a "warning". Warnings don't cause standard to return a non-zero (error)
exit code. However, a warning message will still print to the console. During
the transition period, using standard --fix will update your code so that it's
ready for the next major version.
The slow and careful approach is what we strive for with standard. We're
generally extremely conservative in enforcing the usage of new language
features. We want using standard to be light and fun and so we're careful
about making changes that may get in your way. As always, you can disable a rule at any time, if necessary.
As with every new major release, there are lots of new rules in 16.0.0 designed
to help catch bugs and make programmer intent more explicit. This release brings
better performance, tons of bug fixes, improved JSX, React ⚛️, and Next.js support!
When you upgrade, consider running standard --fix to automatically format your
code to match the newly added rules.
❤️ If you enjoy StandardJS and want to support future releases, please support Feross!
New features
🏎 Better performance: the filesystem doesn't need to be traversed multiple times! #1023
Massive improvements (on the order of minutes!) for projects with huge folders which are are ignored with .gitignore
🌟 Support the .gitignore ignore syntax from the command line #1117
In older versions, the command standard src would not lint the src/ folder
Instead, a glob pattern like standard src/**/*.js was required
This is now fixed! You can run standard src to lint the src/ folder!
🌟 Support relative paths from the command line in more situations (e.g. standard ../src/*.js) #1384
🌟 New extensions option for linting additional extensions besides .js, .jsx, .mjs, and .cjs
Can be configured with the --ext command line flag or in package.json:
Example:
standard --ext .ts
{
"standard": {
"extensions": [".ts"]
}
}
🌟 New cache directory location, respecting XDG_CACHE_HOME preference, with fallback to ~/.cache/standard standard-engine/#214
Changed features
Update eslint from ~7.11.0 to ~7.12.1
Update standard-engine from ^12 to ^14
Fix inaccurate --help command which indicates that bundle.js is automatically ignored when it is not anymore standard-engine/#224
Remove deglob package and use built-in ESLint folder-traversal support
Paths with square brackets (e.g. [ and ]) are no longer skipped #1333
This pattern is particularly common in Next.js apps, e.g. blog/[slug].js
You may notice new errors in these files since they were not being linted before
Better mono-repo support: Nested node_modules/ folders are ignored by default #1182
This major release fully focuses on getting in sync with the wider ESLint ecosystem
and doesn't in itself introduce any new rules or features.
When you upgrade, consider running standard --fix to automatically format your
code to match the current set of rules.
This is the first release by two of our standard co-maintainers @Divlo and @voxpelli. Buy them a cake if you run into them, thanks for getting this release out!
Major changes
eslint-config-node has been replaced with the up to date fork eslint-config-n. If you have used comments like // eslint-disable-line node/no-deprecated-api you now have to reference the n/ rules instead.
NOTE: If you use standard with the --parser babel-eslint option, please ensure that you update babel-eslint to 10.0.3 or later for compatibility with this version of standard.
As with every new major release, there are lots of new rules in 14.0.0 designed
to help catch bugs and make programmer intent more explicit. This release brings
support for ES 2019, the latest version of the ECMAScript specification, as well
as many quality-of-life improvements for users who use tagged template strings,
JSX, and .mjs files for ES modules.
When you upgrade, consider running standard --fix to automatically format your
code to match the newly added rules.
standard keeps growing! The latest stats show that standard and
eslint-standard-* shareable configs are depended upon by 318,512 GitHub
repositories and 33,349 public npm packages. Thanks for spreading the
word!
We now have a Discord server. Come chat with the
maintainers, ask questions, and get help from the community!
❤️ If you enjoy StandardJS and want to support future releases, check out
Feross's GitHub Sponsors page.
GitHub is matching donations, so your dollars go twice as far! 🚀
Require the first JSX property to be placed on a new line if the JSX tag takes up multiple lines and there are multiple properties (react/jsx-first-prop-new-line) #696 [1%]
Require linebreaks in curly braces in JSX attributes and expressions to be consistent (react/jsx-curly-newline) #1372 [1%]
Require JSX attributes and logical expressions to be indented correctly (react/jsx-indent) #1370 [1%]
As with every new major release, there are lots of new rules in 13.0.0 designed
to help catch bugs and make programmer intent more explicit.
standard is more popular than ever – 640,000 downloads per month! It's
even more popular – 3,000,000 downloads per month – if you include the ESLint configuration
that we also publish (for advanced users).
When you upgrade, consider running standard --fix to automatically format your code to match the newly added rules.
❤️ If you enjoy StandardJS and want to support future releases, check out Feross's GitHub Sponsors page. GitHub is matching donations, so your dollars go twice as far! 🚀
New features
Update eslint from ~5.16.0 to ~6.0.1
BREAKING: Node.js 6 is no longer supported
Node.js 6 is EOL and will no longer be receiving security updates. As a result, the eslint team has decided to drop support for it.
To prevent breaking CI for projects which still support Node 6, standard silently passes when run by an unsupported version of Node.
For eslint-config-standard users only: Plugins are no longer affected by eslint's location
Previously, ESLint loaded plugins relative to the location of the ESLint package itself. As a result, we suggested that users with global ESLint installations should also install plugins globally, and users with local ESLint installations should install plugins locally.
With ESLint v6, plugins should always be installed locally, even if ESLint was installed globally. More precisely, ESLint v6 resolves plugins relative to the end user’s project by default, and always resolves shareable configs and parsers relative to the location of the config file that imports them.
Since ESLint 5 no longer supports Node 4, standard silently passes when run in Node 4, which matches the current behavior for Node 0.10, 0.12, and all other unsupported versions of Node.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
Release Notes
standard/standard (standard)v17.1.2
Compare Source
v17.1.1
Compare Source
v17.1.0
Compare Source
v17.0.0
Compare Source
v16.0.4
Compare Source
v16.0.3
Compare Source
We're super excited to announce standard 17!
This major release fully focuses on getting in sync with the wider ESLint ecosystem
and doesn't in itself introduce any new rules or features.
When you upgrade, consider running standard --fix to automatically format your
code to match the current set of rules.
This is the first release by two of our standard co-maintainers @Divlo and @voxpelli. Buy them a cake if you run into them, thanks for getting this release out!
Major changes
Changed features
v16.0.2
Compare Source
v16.0.1
Compare Source
standard treats all rule violations as errors, which means that standard
will exit with a non-zero (error) exit code.
However, we may occasionally release a new major version of standard
which changes a rule that affects the majority of standard users (for example,
transitioning from var to let/const). We do this only when we think the
advantage is worth the cost and only when the rule is
auto-fixable.
In these situations, we have a "transition period" where the rule change is only
a "warning". Warnings don't cause standard to return a non-zero (error)
exit code. However, a warning message will still print to the console. During
the transition period, using standard --fix will update your code so that it's
ready for the next major version.
The slow and careful approach is what we strive for with standard. We're
generally extremely conservative in enforcing the usage of new language
features. We want using standard to be light and fun and so we're careful
about making changes that may get in your way. As always, you can
disable a rule at any time, if necessary.
v16.0.0
Compare Source
We're super excited to announce standard 16!
As with every new major release, there are lots of new rules in 16.0.0 designed
to help catch bugs and make programmer intent more explicit. This release brings
better performance, tons of bug fixes, improved JSX, React ⚛️, and Next.js support!
When you upgrade, consider running standard --fix to automatically format your
code to match the newly added rules.
❤️ If you enjoy StandardJS and want to support future releases, please
support Feross!
New features
🏎 Better performance: the filesystem doesn't need to be traversed multiple times! #1023
🌟 Support the .gitignore ignore syntax from the command line #1117
🌟 Support relative paths from the command line in more situations (e.g. standard ../src/*.js) #1384
🌟 New extensions option for linting additional extensions besides .js, .jsx, .mjs, and .cjs
Can be configured with the --ext command line flag or in package.json:
Example:
{ "standard": { "extensions": [".ts"] } }🌟 New cache directory location, respecting XDG_CACHE_HOME preference, with fallback to ~/.cache/standard standard-engine/#214
Changed features
Update eslint from ~7.11.0 to ~7.12.1
Update standard-engine from ^12 to ^14
Paths with square brackets (e.g. [ and ]) are no longer skipped #1333
Better mono-repo support: Nested node_modules/ folders are ignored by default #1182
Remove eslint-plugin-standard #1316
New rules
(Estimated % of affected standard users, based on test suite in parens)
Changed rules
v15.0.1
Compare Source
v15.0.0
Compare Source
We're super excited to announce standard 17!
This major release fully focuses on getting in sync with the wider ESLint ecosystem
and doesn't in itself introduce any new rules or features.
When you upgrade, consider running standard --fix to automatically format your
code to match the current set of rules.
This is the first release by two of our standard co-maintainers @Divlo and @voxpelli. Buy them a cake if you run into them, thanks for getting this release out!
Major changes
Changed features
v14.3.4
Compare Source
v14.3.3
Compare Source
v14.3.2
Compare Source
v14.3.1
Compare Source
v14.3.0
Compare Source
v14.2.0
Compare Source
v14.1.0
Compare Source
NOTE: If you use standard with the --parser babel-eslint option, please ensure that you update babel-eslint to 10.0.3 or later for compatibility with this version of standard.
v14.0.2
Compare Source
v14.0.1
Compare Source
v14.0.0
Compare Source
We're super excited to announce standard 14!
As with every new major release, there are lots of new rules in 14.0.0 designed
to help catch bugs and make programmer intent more explicit. This release brings
support for ES 2019, the latest version of the ECMAScript specification, as well
as many quality-of-life improvements for users who use tagged template strings,
JSX, and .mjs files for ES modules.
When you upgrade, consider running standard --fix to automatically format your
code to match the newly added rules.
standard keeps growing! The latest stats show that standard and
eslint-standard-* shareable configs are depended upon by 318,512 GitHub
repositories and 33,349 public npm packages. Thanks for spreading the
word!
We now have a Discord server. Come chat with the
maintainers, ask questions, and get help from the community!
❤️ If you enjoy StandardJS and want to support future releases, check out
Feross's GitHub Sponsors page.
GitHub is matching donations, so your dollars go twice as far! 🚀
New features
Changed features
New rules
(Estimated % of affected standard users, based on test suite in parens)
Changed rules
v13.1.0
Compare Source
v13.0.2
Compare Source
v13.0.1
Compare Source
Changed rules
v13.0.0
Compare Source
Welcome to the latest version of standard!
As with every new major release, there are lots of new rules in 13.0.0 designed
to help catch bugs and make programmer intent more explicit.
standard is more popular than ever – 640,000 downloads per month! It's
even more popular – 3,000,000 downloads per month – if you include the
ESLint configuration
that we also publish (for advanced users).
When you upgrade, consider running standard --fix to automatically format your code to match the newly added rules.
❤️ If you enjoy StandardJS and want to support future releases, check out Feross's GitHub Sponsors page. GitHub is matching donations, so your dollars go twice as far! 🚀
New features
New rules
(Estimated % of affected standard users, based on test suite in parens)
v12.0.1
Compare Source
v12.0.0
Compare Source
New version of ESLint, new version of Standard!
When you upgrade, consider running standard --fix to automatically format your code to match the newly added rules.
New features
New rules
(Estimated % of affected standard users, based on test suite in parens)
Changed rules
None.
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.