Socket
Socket
Sign inDemoInstall

standard

Package Overview
Dependencies
237
Maintainers
16
Versions
183
Alerts
File Explorer

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies

Install
2345
19Next

17.1.0

Diff

voxpelli
published 17.0.0 •

voxpelli
published 17.0.0-2 •

Changelog

Source

[17.0.0-2] - 2022-02-03

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

Changelog

Source

[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
voxpelli
published 17.0.0-0 •

Changelog

Source

[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
voxpelli
published 16.0.4 •

Changelog

Source

[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
feross
published 16.0.3 •

Changelog

Source

[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
feross
published 16.0.2 •

feross
published 16.0.1 •

Changelog

Source

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

feross
published 16.0.0 •

Changelog

Source

[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
2345
19Next
SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc