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 v17 #43

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Sep 5, 2022

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
standard (source) ^11.0.0 -> ^17.0.0 age adoption passing confidence

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

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

v16.0.4

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.3

Compare Source

  • Update eslint from ~7.12.1 to ~7.13.0
  • Relax rule: Enforce default parameters to be last #​1414

v16.0.2

Compare Source

  • Allow standard to run on Node 11, even though it's not officially supported #​1597

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)

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

v15.0.0

Compare Source

We're super excited to announce standard 15!

As with every new major release, there are lots of new rules in 15.0.0 designed
to help catch bugs and make programmer intent more explicit. This release brings
support for ES 2021, the latest version of the ECMAScript specification, as well
as many quality-of-life improvements, including ESLint v7.

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.

New features
Changed features
  • BREAKING: Node.js 8 is no longer supported
    • Node.js 8 is EOL and will no longer be receiving security updates.
    • To prevent breaking CI for projects which still support Node 8, standard silently passes when run by an unsupported version of Node
  • Update eslint from ~6.8.0 to ~7.11.0
New rules

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

Changed rules
  • Relax rule: Allow function declarations in nested blocks #​1406
  • Relax rule: Removed redundant no-negated-in-lhs rule, already enforced by no-unsafe-negation eslint-config-standard/#​160

v14.3.4

Compare Source

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

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

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)

Changed rules

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)

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)

Changed rules

None.


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 renovate bot added the maintenance label Sep 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants