You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The value must be a reference to a Node.js module that implements
standard-engine. The above example is for
@novemberborn/as-i-preach.
When set, the standard-engine value takes precedence over any other linters
discovered in the devDependencies.
The package.json file is discovered by walking up the file system, starting at
the file being linted. The first package.json file found is the one that's
used. The linter is invoked with its working directory set to the directory the
package.json file is in. The package.json file's location and contents are
cached.
If you have a project setup with multiple package.json files you can tell
linter-js-standard-engine to ignore nested package.json files and keep
walking up the file system:
{
"standard-engine": {
"skip": true
}
}
This object format can also be used to specify the linter:
Run Standard Engine: Fix File to automatically fix linting issues.
Restart
Run Standard Engine: Restart to clear internal caches and restart linters.
What about linter-js-standard?
If you're using standard, semistandard or happiness then you could use
another package called
linter-js-standard.
The advantage of using linter-js-standard-engine however is that it utilizes
the linter that is installed in your project, rather than bundling a particular
linter version. We also support more linters, including any custom linter that's
based on standard-engine.