v2.1.3

What's Changed

• Fix: "Unable to locate the project file" after upgrading ts-standard to v12 (#494)
• Fix: "TypeError: callback is not a function" error message (#465)

New Contributors

• @pedro-w made their first contribution in #494

Full Changelog: v2.1.2...v2.1.3

v2.1.2

What's Changed

• Fix: Publishing issue on the VSCode Marketplace (#444)

Full Changelog: v2.1.1...v2.1.2

v2.1.1

What's Changed

• Fix: Detect brackets in filename and folders (#443)

New Contributors

• @josegutierro and @AndreiMariusHogas their first contribution in #443

Full Changelog: v2.1.0...v2.1.1

v2.1.0

• Feature: Add support for standard-engine@15 (#376)

New Contributors

• @NemoStein made their first contribution in #376

Full Changelog: v2.0.1...v2.1.0

v2.0.1

• Fix: Crash if a package.json file does not have a devDependencies property. (#310)
• Chore: Add automated tests (#297)

New Contributors

• @Eomm made their first contribution in #294
• @Flet made their first contribution in #310

Full Changelog: v2.0.0...v2.0.1

v2.0.0

• Feature: Better options default to reduce configurations overhead for users so that they can use the extension fast without too much configurations and still following "best practices" by encouraging local installation per project. (#263)

Now the extension will be automatically be enabled in projects that has one of the engines (standard, semistandard, standardx or ts-standard) installed in devDependencies in package.json.

Note: This feature is only working if you have only one open folder in your VSCode workspace.
Note 2: If you still want to enable the extension globally you can set the new option : "standard.enableGlobally": true (by default it is set to false).

BREAKING CHANGE: This feature changed the default settings, before: "standard.usePackageJson": false, after: "standard.usePackageJson": true

BREAKING CHANGE: By default (if you don't set "standard.enableGlobally": true), the extension will not lint your files if you haven't got a package.json containing one of the engines installed in devDependencies.

v1.5.1

• Fix: Find babel config files with @babel/eslint-parser (#207)

v1.5.0

• Feature: Add treatErrorsAsWarnings to forces all warnings and errors from standard to become warnings (#108)
• Fix: Detect brackets in filename (#126 and #139)

Now standardEnabled context variable

We've added a clause context to detect if standard is enabled.

Now for example we can use the context in our key bindings, e.g:

{
    "key": "ctrl+shift+i",
    "command": "standard.executeAutofix",
    "when": "standardEnabled && editorTextFocus && !editorReadonly"
}

No more globally StandardJS!

New features

• This version add a new usePackageJson setting default to false, when set to true, JavaScript Standard Style will only be activated if you have standard or semistandard installed under your project root. 264c442 - @Bojan