Skip to content

Latest commit

 

History

History
1305 lines (846 loc) · 73.9 KB

CHANGELOG.md

File metadata and controls

1305 lines (846 loc) · 73.9 KB
Raw

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[17.1.0] - 2023-05-29

[17.0.0] - 2022-04-20

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

[17.0.0-2] - 2022-02-03

  • Fix: Follow up to the fix of #1548 in 17.0.0-1 #1775

[17.0.0-1] - 2022-01-31

  • Fix: Ensure we support all of the latest syntax that ESLint 8 includes, such as top level await #1548

[17.0.0-0] - 2022-01-31

We're finally able to offer a pre-release of ESLint 8 based 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.

This pre-release exists to test out the ESLint 8 related changes and discover possible backwards incompatible changes that comes with it and mitigate unintended such before a stable release.

When you upgrade, consider running standard --fix to automatically format your code to match the current set of rules.

Changed features

  • Update eslint from ~7.18.0 to ^8.8.0
  • Update eslint-config-standard from 16.0.3 to 17.0.0-0 to adapt to ESLint 8
  • Update eslint-config-standard-jsx from 10.0.0 to 11.0.0-0 to adapt to ESLint 8
  • Update standard-engine from ^14 to ^15.0.0-0 to adapt to ESLint 8, see its CHANGELOG

[16.0.4] - 2021-10-03

  • 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

16.0.3 - 2020-11-17

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

16.0.2 - 2020-11-11

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

16.0.1 - 2020-10-30

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

16.0.0 - 2020-10-28

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

15.0.1 - 2020-10-27

15.0.0 - 2020-10-21

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

  • Support ES 2021, the latest version of the ECMAScript specification, which includes support for logical assignment operators and numeric separators #1551
  • Support ES 2020 features such as optional chaining, the nullish coalescing operator, export * as ns from 'source', and import.meta.
  • Support global variables from ES 2017 (Atomics, SharedArrayBuffer), ES 2020 (BigInt, BigInt64Array, BigUint64Array, globalThis), and ES 2021 (FinalizationRegistry, WeakRef). #1436 #1557 eslint-config-standard/#156
  • The documentation is now available in Indonesian 🇮🇩! #1544
    • Thanks to @yoga1234 for the excellent work!
    • Other community contributed translations exist in Spanish, French, Italian, Japanese, Korean, Portuguese, Simplified Chinese, and Taiwanese Mandarin.
    • More translations are always welcome!

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

14.3.4 - 2020-05-11

  • Relax rule: no-return-await #1442

14.3.3 - 2020-03-15

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

14.3.2 - 2020-03-14

  • Update eslint to ~6.8.0

14.3.1 - 2019-09-17

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

14.3.0 - 2019-09-14

  • Update eslint to ~6.4.0

14.2.0 - 2019-09-11

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

14.1.0 - 2019-08-28

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.

14.0.2 - 2019-08-22

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

14.0.1 - 2019-08-22

14.0.0 - 2019-08-19

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

13.1.0 - 2019-07-20

  • Update eslint from ~6.0.1 to ~6.1.0

13.0.2 - 2019-07-12

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

13.0.1 - 2019-07-11

Changed rules

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

13.0.0 - 2019-07-10

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)

12.0.1 - 2018-08-29

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

12.0.0 - 2018-08-28

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.

11.0.0 - 2018-02-18

This release has no new rules, but it does update to the latest version of eslint, version 4, which has some significant changes to existing rules. Most updates make the indentation rules more strict.

Thankfully, most users will just need to run standard --fix to update code to be compliant.

New features

  • Update eslint from ~3.19.0 to ~4.18.0.

    • The indent rule is more strict.
    • The padded-blocks rule is more strict.
    • The space-before-function-paren rule is more strict.
    • The no-multi-spaces rule is more strict.
    • Minor improvements to:
      • no-extra-parens,
      • no-unexpected-multiline,
      • no-regex-spaces, and
      • space-unary-ops

  • Update eslint-plugin-import from ~2.2.0 to ~2.8.0

    • Updated for eslint 4.0 compatibility.
    • Various small bug fixes included related to import/* rules.

  • Update eslint-plugin-node from ~4.2.2 to ~6.0.0

    • The no-deprecated-api rule is updated with Node.js 8 support and improved Node 6 support.

  • Upodate eslint-plugin-promise from ~3.5.0 to ~3.6.0.

  • Update eslint-plugin-react from ~6.10.0 to ~7.6.1

    • Fix jsx-indent crash
    • Fix jsx-indent indentation calculation with nested JSX.
    • Fix jsx-no-undef will not check the global scope by default.
    • Fix jsx-curly-spacing newline with object literals bug.
    • Fix jsx-curly-spacing schema incompatibility with ESLint 4.2.0.
    • Fix alignment bug in jsx-indent.

Changed rules

  • Relax rule: Don't mark Rails Asset Pipeline comments (comments that start with //=) as errors. (spaced-comment) #918

👏 Huge thanks to @Flet for putting together most of this release!

10.0.3 - 2017-08-06

  • Internal changes (incremented dependency versions)

10.0.2 - 2017-04-14

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.

10.0.1 - 2017-04-06

  • Internal changes (incremented dependency versions)

10.0.0 - 2017-04-04

standard just turned 10.0.0! 🎉

As with every new major release, there are lots of new rules in 10.0.0 designed to help catch bugs and make programmer intent more explicit.

standard is more popular than ever – 330,000 downloads per month! It's even more popular – 670,000 downloads per month – if you include the shareable ESLint config that we also publish.

The most important change in 10.0.0 is that using deprecated Node.js APIs is now considered an error. It's finally time to update those dusty old APIs!

Deprecated APIs are problematic because they may print warning messages in the console in recent versions of Node.js. This often confuses users and leads to unnecessary support tickets for project maintainers.

Some deprecated APIs are even insecure (or at least prone to incorrect usage) which can have serious security implications. For that reason, standard now considers usage of Buffer(num) to be an error, since this function returns uninitialized program memory which could contain confidential information like passwords or keys.

Instead of Buffer(num), consider using Buffer.alloc(num) or Buffer.from(obj) which make the programmer's intent clearer. These functions exist in all currently supported versions of Node.js, including Node.js 4.x. For more background, see this Node.js issue.

We also improved some rules to support common patterns in code bases that use React, JSX, and Flow.

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

New features

  • Update ESLint from 3.15.x to 3.19.x.
  • Node.js API: Add standard.lintTextSync method

New rules

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

  • Disallow using deprecated Node.js APIs (node/no-deprecated-api) #693 [13%]
    • Ensures that code always runs without warnings on the latest versions of Node.js
    • Ensures that safe Buffer methods (Buffer.from(), Buffer.alloc()) are used instead of Buffer()
  • Enforce callbacks always called with Node.js-style error first (standard/no-callback-literal) #623 [3%]
    • Functions named callback or cb must be invoked with null, undefined, or an Error as the first argument
    • Disallows using a string instead of an Error object
    • Disallows confusing callbacks that do not follow the standard Node.js pattern
  • Disallow any imports that come after non-import statements (import/first) #806 [1%]
  • Disallow unnecessary return await (no-return-await) #695 [0%]
  • Disallow comma-dangle in functions (comma-dangle) #787 [0%]
  • Disallow repeated exports of names or defaults (import/export) #806 [0%]
  • Disallow import of modules using absolute paths (import/no-absolute-path) #806 [0%]
  • Disallow Webpack loader syntax in imports (import/no-webpack-loader-syntax) #806 [0%]
  • Disallow comparing against -0 (no-compare-neg-zero) #812 [0%]

Changed rules

  • Relax rule: allow using ...rest to omit properties from an object (no-unused-vars) #800
    • This is a common and useful pattern in React/JSX apps!
  • Relax rule: allow Flow import type statements (import/no-duplicates) #599
    • These are no longer considered to be "duplicate imports"
  • Relax rule: Treat process.exit() the same as throw in code path analysis (node/process-exit-as-throw) #699
    • Makes certain other rules work better and give fewer false positives
  • Relax rule: allow Unnecessary Labels (no-extra-label)
    • Redundant, since "no-labels" is already enabled, which is more restrictive

9.0.2 - 2017-03-17

Changed rules

9.0.1 - 2017-03-07

Changed rules

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

9.0.0 - 2017-02-28

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)

Changed rules

8.6.0 - 2016-11-22

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

8.5.0 - 2016-10-25

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

8.4.0 - 2016-10-10

  • 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

8.3.0 - 2016-09-29

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.

8.2.0 - 2016-09-26

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

8.1.0 - 2016-09-17

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

8.0.0 - 2016-08-23

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

New rules

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

Changed rules

  • Relax rule: Allow template literal strings (backtick strings) to avoid escaping #421
  • Relax rule: Do not enforce spacing around * in generator functions (#564 (comment))
    • This is a temporary workaround for babel users who use async generator functions.

7.1.2 - 2016-06-03

  • Fix install errors for some users by updating eslint peer dependency

7.1.1 - 2016-05-26

  • Add back full node 0.10, 0.12 support

7.1.0 - 2016-05-16

  • Upgrade eslint to version 2.10.2.

7.0.1 - 2016-05-04

  • Relax "no-duplicate-imports" rule to not include export so the following is allowed:
import { foo } from 'bar'
export * from 'bar'

7.0.0 - 2016-05-02

Changes

  • Upgrade eslint to version ~2.9.0
  • Remove "rules" configuration option #367 from package.json (Reasoning is here)

New rules

Estimated % of affected standard users, based on test suite

Removed rules

6.0.8 - 2016-03-07

  • Pin eslint to version ~2.2.0
  • Update eslint-plugin-react to version 4.0.0

6.0.7 - 2016-02-18

  • Revert: Use install location of standard as eslint cwd (fixes #429)

6.0.6 - 2016-02-18

  • Use eslint 2.1.0
  • Fix: Use install location of standard as eslint cwd (fixes snazzy/#8)

6.0.5 - 2016-02-12

  • Use eslint 2.0.0 stable

6.0.4 - 2016-02-07

6.0.3 - 2016-02-06

  • Fix "Error: Cannot find module 'eslint-config-standard-jsx'" with npm 2 (node 0.10, 0.12, 4)

6.0.2 - 2016-02-06

  • Internal change: Remove .eslintrc file, and use inline config

6.0.1 - 2016-02-05

  • Internal change: Move .eslintrc file to root folder

6.0.0 - 2016-02-05

The goal of this release is to make standard faster to install, and simpler to use.

Remove standard-format (#340) (#397)

  • Eliminates 250 packages, and cuts install time in half!
  • For npm 2, install time goes from 20 secs —> 10 secs.
  • For npm 3, install time goes from 24 secs —> 12 secs.
  • To continue using standard-format, just install it separately: npm install -g standard-format

React-specific linting rules are removed (#351) (#367) (eslint-config-standard-react/#13)

  • JSX is still supported, and it continues to be checked for style.
  • There were only a few React-specific rules, but they made it extremely difficult for users of alternatives like virtual-dom or deku, and unecessarily tied standard to a single library.
  • JSX rules come from eslint-config-standard-jsx. The eslint-config-standard-react dependency was removed.

New Rules

The percentage (%) of users that rule changes will effect, based on real-world testing of the top ~400 npm packages is denoted in brackets.

Removed Rules

  • parseInt() radix rule because ES5 fixes this issue (#384) (radix) [0%]

Expose eslint configuration via command line options and package.json

For power users, it might be easier to use one of these new hooks instead of forking standard, though that's still encouraged, too!

  • Set eslint "plugins" (#386)
  • Set eslint "rules" (#367)
  • Set eslint "env" (#371)

To set custom ESLint plugins, rules, or envs, use the command line --plugin, --rules, and --env flags.

In package.json, use the "standard" property:

{
  "standard": {
    "plugins": [ "my-plugin" ]
  }
}

Upgrade to ESLint v2

  • There may be slight behavior changes to existing rules. When possible, we've noted these in the "New Rules" and "Removed Rules" section.

Improve test suite

  • Rule changes can be tested against every package on npm. For sanity, this is limited to packages with at least 4 dependents. Around 400 packages.

Known Issues

  • Using prerelease eslint version (2.0.0-rc.0). There may be breaking changes before the stable release.
  • no-return-assign behavior changed with arrow functions (eslint/eslint#5150)

Relevant diffs

5.4.1 - 2015-11-16

view diff

Fixed

  • Fix for standard-engine change. Fix error tagline.

5.4.0 - 2015-11-16

view diff

Added

5.3.1 - 2015-09-18

view diff

Changed

5.3.0 - 2015-09-16

view diff

Changed

5.2.2 - 2015-09-08

view diff

Fixed

  • We have a changelog now, and you're reading it!
  • Minor README update
  • Removed direct dependency on eslint (its now moved to standard-engine)

5.2.1 - 2015-09-03

view diff

Changed

Fixed

5.2.0 - 2015-09-03

view diff

Added

  • [email protected] (history)
    • New rule: Disallow unncessary concatenation of strings
    • New rule: Disallow duplicate name in class members
    • New rule: enforce spaces inside of single line blocks
    • Re-add rule: padded-blocks (Closes #170)

Changed

Fixed

5.1.1 - 2015-08-28

view diff

Fixed

  • Update to RULES.md to remove a missing hyperlink
  • Add atom linter information to README.md
  • Fixed duplicated word in the tagline message on the CLI
  • Removed failing repository from tests (yoshuawuyts/initialize)

5.1.0 - 2015-08-14

view diff

Fixed

Changed

  • Bump eslint from 1.0.0 to 1.2.0 (CHANGELOG)
  • Added more test repositories and disabled some that were failing
  • Update bikeshedding link on README.md

5.0.2 - 2015-08-06

view diff

Changed

5.0.1 - 2015-08-05

view diff

5.0.0 - 2015-08-03

view diff

eslint v1.0.0 is released! eslint added some new rules that are nice, and lots of existing rules have subtle behavior changes designed to catch more errors.

Let's talk about the next version of standard! We bumped the major version to v5.0.0 to pull in these improvements.

New rules:

Changed rules:

4.5.4 - 2015-07-13

view diff

4.5.3 - 2015-07-10

view diff

4.5.2 - 2015-07-02

view diff

4.5.1 - 2015-06-30

view diff

4.5.0 - 2015-06-30

view diff

4.4.1 - 2015-06-29

view diff

4.4.0 - 2015-06-27

view diff

4.3.3 - 2015-06-26

view diff

4.3.2 - 2015-06-23

view diff

4.3.1 - 2015-06-18

view diff

4.3.0 - 2015-06-16

view diff

4.2.1 - 2015-06-12

view diff

4.2.0 - 2015-06-11

view diff

4.1.1 - 2015-06-11

view diff

4.1.0 - 2015-06-10

view diff

4.0.1 - 2015-06-01

view diff

4.0.0 - 2015-05-30

view diff