Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency standard to v13 #87

merged 1 commit into from Jul 18, 2019


Copy link

renovate bot commented Jul 10, 2019

This PR contains the following updates:

Package Type Update Change
standard (source) devDependencies major 12.0.1 -> 13.0.2

Release Notes



Compare Source

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


Compare Source

Changed rules
  • Relax rule: Only enforce const in destructuring when all variables are constant #​1325


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 @​Munieru 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)

Renovate configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Enabled.

♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".

🔕 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 has been generated by Renovate Bot. View repository job log here.


This comment has been minimized.

Copy link

coveralls commented Jul 10, 2019

Coverage Status

Coverage remained the same at 100.0% when pulling 443ccf3 on renovate/standard-13.x into e460663 on master.

@renovate renovate bot force-pushed the renovate/standard-13.x branch from 1dcf09e to d3a40b6 Jul 11, 2019
@renovate renovate bot force-pushed the renovate/standard-13.x branch from d3a40b6 to 443ccf3 Jul 12, 2019
@zrrrzzt zrrrzzt merged commit 060051f into master Jul 18, 2019
1 of 3 checks passed
1 of 3 checks passed
continuous-integration/travis-ci/pr The Travis CI build could not complete due to an error
continuous-integration/travis-ci/push The Travis CI build could not complete due to an error
coverage/coveralls Coverage remained the same at 100.0%
@renovate renovate bot deleted the renovate/standard-13.x branch Jul 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
3 participants
You can’t perform that action at this time.