Update dependency standard to v17 #47

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.
object-shorthand rule (as warning)
Use of ESLint 8, which allows for support for all of the latest syntax that ESLint 8 includes, such as top level await #1548 #1775
--verbose by default

Changed features

Update eslint from ~7.18.0 to ^8.13.0
Update eslint-config-standard from 16.0.3 to 17.0.0 to adapt to ESLint 8
Update eslint-config-standard-jsx from 10.0.0 to ^11.0.0 to adapt to ESLint 8
Update standard-engine from ^14 to ^15.0.0 to adapt to ESLint 8, see its CHANGELOG
Move from eslint-plugin-node@~11.1.0 to eslint-plugin-n@^15.1.0 to adapt to ESLint 8
Update eslint-plugin-import from ~2.24.2 to ^2.26.0
Update eslint-plugin-promise from ~5.1.0 to ^6.0.0
Update eslint-plugin-react from ~7.25.1 to ^7.28.0

`v16.0.2`

Compare Source

Update eslint from ~7.13.1 to ~7.18.0
Update eslint-config-standard from 16.0.2 to 16.0.3
Update eslint-plugin-import from ~2.22.1 to ~2.24.2
Update eslint-plugin-promise from ~4.2.1 to ~5.1.0
Update eslint-plugin-react from ~7.21.5 to ~7.25.1

`v16.0.1`

Compare Source

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.

`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
- 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
Remove eslint-plugin-standard #1316
- We migrated the remaining no-callback-literal rule into eslint-plugin-node

New rules

(Estimated % of affected standard users, based on test suite in parens)

Require let or const instead of var (no-var) #633 [75%] [automatic fixing reduces to 11%]
Enforce return statements in Array method callbacks (array-callback-return) #859 [7%]
Disallow empty block statements (no-empty) #796 [2%]
Enforce default parameters to be last (default-param-last) #1414 [1%]
Disallow use of the RegExp constructor in favor of regular expression literals (prefer-regex-literals) #1413 [1%]
Disallow spaces inside of computed keys of class methods, getters and setters (computed-property-spacing) #1416 [0%]
Disallow case NaN, switch(NaN), indexOf(NaN), and lastIndexOf(NaN) (use-isnan) #1429 [0%]
Disallow assigning to imported bindings (no-import-assign) #1412 [0%]
Enforce getter/setter pairs in classes (accessor-pairs) #1415 [0%]
Node: Disallow assignment to exports (node/no-exports-assign) #1400 [0%]
React: Prevent usage of the return value of ReactDOM.render (react/no-render-return-value) #1568 [1%]
React: Prevent usage of deprecated methods (react/no-deprecated) #1572 [1%]
React: Prevent direct mutation of this.state (react/no-direct-mutation-state) #1571 [0%]
React: Prevent usage of findDOMNode (react/no-find-dom-node) #1570 [0%]
React: Prevent usage of isMounted (react/no-is-mounted) #1569 [0%]
React: Prevent using string refs (react/no-string-refs) #1567 [0%]
JSX: Prevent missing parentheses around multiline JSX (react/jsx-wrap-multilines) #710 #1382 (0%)
JSX: Check if shorthand fragment syntax requires a key prop (react/jsx-key) #1575 [0%]
JSX: Prevent passing of children as props (react/no-children-prop) #1574 [0%]
JSX: Prevent using children and dangerouslySetInnerHTML as props at the same time (react/no-danger-with-children) #1573 [0%]
JSX: Prevent invalid characters from appearing in markup (react/no-unescaped-entities) #1566 [0%]
JSX: Enforce JSX value is returned in component render function (react/require-render-return) #1565 [0%]
JSX: Prevent usage of unsafe target='_blank' on any component named Link (react/jsx-no-target-blank) #1576 [0%]

Changed rules

Relax rule: JSX: Consider the global scope when checking for defined Components #1115
Relax rule: JSX: Remove conflicting indentation rule in indent #1499

`v15.0.1`

Compare Source

Relax rule: Remove conflicting JSX indenting with indent rule eslint-config-standard/#177

`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

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.
object-shorthand rule (as warning)
Use of ESLint 8, which allows for support for all of the latest syntax that ESLint 8 includes, such as top level await #1548 #1775
--verbose by default

Changed features

Update eslint from ~7.18.0 to ^8.13.0
Update eslint-config-standard from 16.0.3 to 17.0.0 to adapt to ESLint 8
Update eslint-config-standard-jsx from 10.0.0 to ^11.0.0 to adapt to ESLint 8
Update standard-engine from ^14 to ^15.0.0 to adapt to ESLint 8, see its CHANGELOG
Move from eslint-plugin-node@~11.1.0 to eslint-plugin-n@^15.1.0 to adapt to ESLint 8
Update eslint-plugin-import from ~2.24.2 to ^2.26.0
Update eslint-plugin-promise from ~5.1.0 to ^6.0.0
Update eslint-plugin-react from ~7.25.1 to ^7.28.0

`v14.3.4`

Compare Source

Relax rule: no-return-await #1442

`v14.3.3`

Compare Source

Skip running on versions of Node.js older than 8.10.0. #1496

`v14.3.2`

Compare Source

Update eslint to ~6.8.0

`v14.3.1`

Compare Source

Skip running on versions of Node.js older than 8.6.0. #1418

`v14.3.0`

Compare Source

Update eslint to ~6.4.0

`v14.2.0`

Compare Source

Update eslint to ~6.3.0
Update eslint-plugin-node to ~10.0.0

`v14.1.0`

Compare Source

Support ES 2020, the latest version of the ECMAScript specification, which includes support for Dynamic Imports and BigInt. #1378
Security: Upgrade eslint to 6.2.2 to fix security issue (blog post) (security advisory)
Remove funding. See Recap of the funding experiment for thoughts and learnings.

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

Relax rule: Don't check indentation on template literal children (work around for ESLint bug) (indent) #1385

`v14.0.1`

Compare Source

Relax rule (temporarily, to workaround a bug): Disallow missing parentheses around multiline JSX (react/jsx-wrap-multilines) #1382

`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

Support ES 2019, the latest version of the ECMAScript specification. eslint-config-standard/e04e06
Lint *.mjs and *.cjs files automatically by default #1009
Ignore patterns from .git/info/exclude in addition to .gitignore. #1277
Added funding, an open source funding experiment.

Changed features

Remove bundle.js from the default list of ignored files #743

New rules

(Estimated % of affected standard users, based on test suite in parens)

Require Dot Notation Whenever Possible (dot-notation) #1344 [6%]
Require consistent line breaks inside braces (object-curly-newline) #782 [1%]
Disallow template literals when placeholders or tagged template features are not used. (quotes) #838 eslint-config-standard/#151 [1%]
Disallow lexical declarations in case/default clauses (no-case-declarations) #1211 eslint-config-standard/#137 [1%]
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%]
Require JSX event handler names to follow conventions (react/jsx-handler-names) #1371 [1%]
Disallow spaces inside of curly braces in JSX expressions in children (react/jsx-curly-spacing) #1373 [1%]
Require JSX closing bracket to be aligned with the opening tag (react/jsx-closing-bracket-location) #1361 [1%]
Disallow unnecessary curly braces in JSX props and children (react/jsx-curly-brace-presence) #1366 [1%]
Disallow missing key prop in JSX elements that likely require a key prop (react/jsx-key) #1369 [1%]
Disallow import of modules using absolute paths (import/no-absolute-path) #861 #1343 [0%]
Require no spaces before JSX closing brackets (react/jsx-tag-spacing) #1348 eslint-config-standard-jsx/38 [0%]
Disallow multiple spaces between inline JSX props (react/jsx-props-no-multi-spaces) #1363 [0%]
Disallow accidental comments in JSX from being inserted as text nodes (react/jsx-no-comment-textnodes) #1368 [0%]
Prevent usage of unsafe target='_blank' in JSX links (react/jsx-no-target-blank) #1367 [0%]
Require shorthand form for JSX fragments (react/jsx-fragments) #1364 [0%]
Require PascalCase for user-defined JSX components (react/jsx-pascal-case) #1365 [0%]
Require JSX closing tag to be aligned with the opening tag (react/jsx-closing-tag-location) #1358 [0%]
Disallow missing parentheses around multiline JSX (react/jsx-wrap-multilines) #710 [0%]
Require pipeline operators to appear at the start of a line (operator-linebreak) eslint-config-standard/#121 [0%]
Disallow use of the void operator (no-void) eslint-config-standard/#135 [0%]

Changed rules

Relax rule: Don't require newlines between single-line member functions or class field declarations (lines-between-class-members) #1347
Relax rule: Don't check indentation on template literal children (work around for ESLint bug) (indent) #1176
Relax rule: Disallow labels that are variables names (because all labels are already disallowed) (no-label-var) eslint-config-standard/#132

`v13.1.0`

Compare Source

Update eslint from ~6.0.1 to ~6.1.0

`v13.0.2`

Compare Source

Fix global installations of standard not finding dependencies due to ESLint v6 plugin resolution change #1327 #1328 #1329

`v13.0.1`

Compare Source

Changed rules

Relax rule: Only enforce const in destructuring when all variables are constant #1325

`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

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.
  - See migrating to ESLint 6.0.0 for more information.
The documentation is now available in Japanese 🇯🇵!
- Thanks to @munierujp for the excellent work!
- Other community contributed translations exist in Spanish, French, Italian, Korean, Portuguese, Simplified Chinese, and Taiwanese Mandarin.
- More translations are always welcome!
Update eslint-plugin-promise from ~4.0.0 to ~4.2.1
Update eslint-plugin-node from ~7.0.1 to ~9.1.0

New rules

(Estimated % of affected standard users, based on test suite in parens)

Disallow spaces inside of array brackets (array-bracket-spacing) #1203 eslint-config-standard/#131 [14%]
Require const instead of let if variable is never reassigned (prefer-const) #523 eslint-config-standard/#133 [14%]
Disallow quotes around object literal property names that are not strictly required (quote-props) #791 [4%]
Disallow use of Object.prototypes builtins directly (no-prototype-builtins) #1310 [3%]
Require an empty line between class members (lines-between-class-members) #438 [1%]
Disallow using an async function as a Promise executor (no-async-promise-executor) #1309 [1%]
Disallow spaces inside of computed properties (computed-property-spacing) #1315 eslint-config-standard/#131 [1%]
Disallow unnecessary catch clauses (no-useless-catch) #1312 [0%]
Disallow characters which are made with multiple code points in character class syntax (no-misleading-character-class) #1311 [0%]

`v12.0.1`

Compare Source

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.

`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

Update eslint from ~4.19.0 to ~5.4.0.
- Support JSXFragment nodes (e.g. <></>)
- Lots of minor changes to rules to catch more edge cases!
The README is now available in French! (Thanks @charliegerard!)
- Other community contributed translations exist in Spanish, Italian, Korean, Portuguese, Simplified Chinese, and Taiwanese Mandarin.
- More translations are welcome!

New rules

(Estimated % of affected standard users, based on test suite in parens)

Require spacing inside of braces (object-curly-spacing) #609 eslint-config-standard/#35 [29%]
Disallow APIs that were deprecated in Node 10 (no-deprecated-api) #1164 [15%]
- e.g. assert.equal(), assert.deepEqual() and assert.notEqual() were deprecated in Node 10.
Disallow self assignment of properties (no-self-assign) #1186 [0%]
Disallow use of an exported name as the locally imported name of a default export (import/no-named-as-default) eslint-config-standard/#98

Changed rules

None.

`v11.0.1`

Compare Source

`v11.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

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.
object-shorthand rule (as warning)
Use of ESLint 8, which allows for support for all of the latest syntax that ESLint 8 includes, such as top level await #1548 #1775
--verbose by default

Changed features

Update eslint from ~7.18.0 to ^8.13.0
Update eslint-config-standard from 16.0.3 to 17.0.0 to adapt to ESLint 8
Update eslint-config-standard-jsx from 10.0.0 to ^11.0.0 to adapt to ESLint 8
Update standard-engine from ^14 to ^15.0.0 to adapt to ESLint 8, see its CHANGELOG
Move from eslint-plugin-node@~11.1.0 to eslint-plugin-n@^15.1.0 to adapt to ESLint 8
Update eslint-plugin-import from ~2.24.2 to ^2.26.0
Update eslint-plugin-promise from ~5.1.0 to ^6.0.0
Update eslint-plugin-react from ~7.25.1 to ^7.28.0

`v10.0.3`

Compare Source

Support ES 2020, the latest version of the ECMAScript specification, which includes support for Dynamic Imports and BigInt. #1378
Security: Upgrade eslint to 6.2.2 to fix security issue (blog post) (security advisory)
Remove funding. See Recap of the funding experiment for thoughts and learnings.

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.

`v10.0.2`

Compare Source

Changed rules

Relax rule: Disallow import of modules using absolute paths (import/no-absolute-path) #861
- This rule was responsible for up to 25% of the running time of standard, so we are disabling it until its performance improves.

`v10.0.1`

Compare Source

Internal changes (incremented dependency versions)

`v10.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

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.
object-shorthand rule (as warning)
Use of ESLint 8, which allows for support for all of the latest syntax that ESLint 8 includes, such as top level await #1548 #1775
--verbose by default

Changed features

Update eslint from ~7.18.0 to ^8.13.0
Update eslint-config-standard from 16.0.3 to 17.0.0 to adapt to ESLint 8
Update eslint-config-standard-jsx from 10.0.0 to ^11.0.0 to adapt to ESLint 8
Update standard-engine from ^14 to ^15.0.0 to adapt to ESLint 8, see its CHANGELOG
Move from eslint-plugin-node@~11.1.0 to eslint-plugin-n@^15.1.0 to adapt to ESLint 8
Update eslint-plugin-import from ~2.24.2 to ^2.26.0
Update eslint-plugin-promise from ~5.1.0 to ^6.0.0
Update eslint-plugin-react from ~7.25.1 to ^7.28.0

`v9.0.2`

Compare Source

Changed rules

Relax rule: Allow tagged template string expressions (no-unused-expressions) #822

`v9.0.1`

Compare Source

Changed rules

Relax rule: Allow mixing basic operators without parens (no-mixed-operators) #816
- Specifically, these operators: +, -, *, /, %, and **

`v9.0.0`

Compare Source

It's time for a new major version of standard! As usual, this release contains a
bunch of awesomeness to help you keep your code in tip-top shape!

We've added several new rules designed to catch potential programmer errors
(i.e. bugs), as well as rules to make programmer intent more explicit in
certain circumstances.

This release continues our trend of tightening up rules so that, wherever possible,
there's one "right" way to do things. This design goal is intended to reduce the
time that teams and maintainers spend giving code review feedback in pull requests.

When you upgrade, consider running standard --fix to automatically fix some of the
errors caught by the new rules in this version.

Note: If you use the Chai test framework, you will need to make some changes to
your tests to improve their robustness. Read about the changes you need to make.

New features

Update ESLint from 3.10.x to 3.15.x
3 additional rules are now fixable with standard --fix

New rules

(Estimated % of affected standard users, based on test suite in parens)

Disallow mixing different operators without parens (no-mixed-operators) #566 [5%]
Enforce 1 newline at end of file (previously 1 or 2 were ok) (no-multiple-empty-lines) #733 [3%]
Disallow Unused Expressions (no-unused-expressions) #690 [3%]
- Note: this affects users of the Chai test framework. Read about the changes you need to make.
Disallow redundant return statements (no-useless-return) #694 [1%]
Disallow Incorrect Early Use (no-use-before-define) #636 [0%]
Enforce that Promise rejections are passed an Error object as a reason (prefer-promise-reject-errors) #777 [0%]
Enforce comparing typeof expressions against string literals (valid-typeof) #629 [0%]
Enforce spacing around * in generator functions (generator-star-spacing) #724 [0%]
Disallow Unnecessary Labels (no-extra-label) #736 [0%]
Disallow spacing between template tags and their literals (template-tag-spacing) #755 [0%]
Disallow padding within switch statements and classes (padded-blocks) #610 [0%]
Enforce that Symbols are passed a description (symbol-description) #630 [0%]

Changed rules

Relax rule: allow TypeScript Triple-Slash Directives (spaced-comment) #660
Relax rule: allow Flow Comments (spaced-comment) #661

`v8.6.0`

Compare Source

Skip running on versions of Node.js older than 8.6.0. #1418

`v8.5.0`

Compare Source

Update ESLint from 3.7.x to 3.8.x
2 additional rules are now fixable with standard --fix

`v8.4.0`

Compare Source

Update ESLint from 3.6.x to 3.7.x
5 additional rules are now fixable with standard --fix
Use more conservative semver ranges #654

`v8.3.0`

Compare Source

The last release (8.2.0) added ES7 support. This release (8.3.0) adds ES8
support ...just 3 days later!

This release should eliminate the need to specify babel-eslint as a custom
parser, since standard can now parse ES8 (i.e. ES2017) syntax out of the box.
That means async and await will just work.

Support ES8 (i.e. ES2017) syntax.

`v8.2.0`

Compare Source

For many users, this release should eliminate the need to specify babel-eslint as
a custom parser, since standard can now parse ES7 (i.e. ES2016) syntax out of the
box.

Support ES7 (i.e. ES2016) syntax.
Update ESLint from 3.5.x to 3.6.x
4 additional rules are now fixable with standard --fix

`v8.1.0`

Compare Source

Update ESLint from 3.3.x to 3.5.x
Around 10 additional rules are now fixable with standard --fix

`v8.0.0`

Compare Source

This release contains a bunch of goodies, including new rules that catch potential
programmer errors (i.e. bugs) and enforce additional code consistency.

However, the best feature is surely the new --fix command line flag to
automatically fix problems. If you ever used
standard-format
and ran into issues with the lack of ES2015+ support, you'll be happy about
--fix.

standard --fix is built into standard v8.0.0 for maximum convenience, it
supports ES2015, and it's lightweight (no additional dependencies since it's part
of ESLint which powers standard). Lots of problems are already fixable, and more
are getting added with each ESLint release.

standard also outputs a message ("Run standard --fix to automatically fix
some problems.") when it detects problems that can be fixed automatically so you
can save time!

With standard v8.0.0, we are also dropping support for Node.js versions prior to
v4. Node.js 0.10 and 0.12 are in maintenance mode and will be unsupported at the
end of 2016. Node.js 4 is the current LTS version. If you are using an older
version of Node.js, we recommend upgrading to at least Node.js 4 as soon as
possible. If you are unable to upgrade to Node.js 4 or higher, then we recommend
continuing to use standard v7.x until you are ready to upgrade Node.js.

Important: We will not be updating the standard v7.x versions going forward.
All bug fixes and enhancements will land in standard v8.x.

Full changelog below. Cheers!

New features

Upgrade to ESLint v3 (https://eslint.org/docs/user-guide/migrating-to-3.0.0) #565
- BREAKING: Drop support for node < 4 (this was a decision made by the ESLint team)
Expose ESLint's --fix command line flag #540 standard-engine/#107
- Lightweight, no additional dependencies, fixes dozens of rules automatically

New rules

(Estimated % of affected standard users, based on test suite in parens)

Enforce placing object properties on separate lines (object-property-newline) #524 [2%]
Require block comments to be balanced (spaced-comment "balanced") #572 [2%]
Disallow constant expressions in conditions (no-constant-condition) #563 [1%]
Disallow ren

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

renovate bot force-pushed the renovate/standard-17.x branch from 9bacb8f to a75bdc1 Compare November 20, 2022 10:21

renovate bot changed the title ~~Update dependency standard to v17~~ Update dependency standard to v17 - autoclosed Apr 4, 2023

renovate bot closed this Apr 4, 2023

renovate bot deleted the renovate/standard-17.x branch April 4, 2023 00:41

renovate bot changed the title ~~Update dependency standard to v17 - autoclosed~~ Update dependency standard to v17 Apr 4, 2023

renovate bot reopened this Apr 4, 2023

renovate bot restored the renovate/standard-17.x branch April 4, 2023 09:27

renovate bot force-pushed the renovate/standard-17.x branch from a75bdc1 to a948a54 Compare May 30, 2023 17:33

renovate bot force-pushed the renovate/standard-17.x branch from a948a54 to 23bd69b Compare September 12, 2024 16:05

Update dependency standard to v17

57b5136

renovate bot force-pushed the renovate/standard-17.x branch from 23bd69b to 57b5136 Compare September 13, 2024 14:39

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update dependency standard to v17 #47

Update dependency standard to v17 #47

Uh oh!

renovate bot commented Apr 25, 2022 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Update dependency standard to v17 #47

Are you sure you want to change the base?

Update dependency standard to v17 #47

Uh oh!

Conversation

renovate bot commented Apr 25, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Major changes

Changed features

New features

Changed features

New rules

Changed rules

Major changes

Changed features

New features

Changed features

New rules

Changed rules

Changed rules

New features

New rules

New features

New rules

Changed rules

Major changes

Changed features

Changed rules

Major changes

Changed features

Changed rules

Changed rules

New features

New rules

Changed rules

New features

New rules

Configuration

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate bot commented Apr 25, 2022 •

edited

Loading