standard/standard
### [`v16.0.1`](https://togithub.com/standard/standard/blob/master/CHANGELOG.md#1601---2020-10-30)
[Compare Source](https://togithub.com/standard/standard/compare/v16.0.0...v16.0.1)
- Introduce "warning" system for disruptive rules (read more below)
- Change rule to a "warning": Require let or const instead of var ([no-var](https://eslint.org/docs/rules/no-var)) [#633](https://togithub.com/standard/standard/issues/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](https://standardjs.com/#is-there-an-automatic-formatter).
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](https://standardjs.com/#how-do-i-disable-a-rule) at any time, if necessary.
Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Enabled.
:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
:no_bell: 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
coveralls
commented
4 years ago
This PR contains the following updates:
16.0.0->16.0.1Release Notes
standard/standard
### [`v16.0.1`](https://togithub.com/standard/standard/blob/master/CHANGELOG.md#1601---2020-10-30) [Compare Source](https://togithub.com/standard/standard/compare/v16.0.0...v16.0.1) - Introduce "warning" system for disruptive rules (read more below) - Change rule to a "warning": Require let or const instead of var ([no-var](https://eslint.org/docs/rules/no-var)) [#633](https://togithub.com/standard/standard/issues/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](https://standardjs.com/#is-there-an-automatic-formatter). 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](https://standardjs.com/#how-do-i-disable-a-rule) at any time, if necessary.Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Enabled.
:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.