This module provides a hands-off wrapper around ESLint and the video.js organization's shared ESLint config. It checks ("lints") your code to verify that it complies with our organization's agreed-upon standards.
npm install videojs-standard
Or, if you prefer to install it globally:
npm install -g videojs-standard
This will put the
vjsstandard program on your PATH, meaning you can call it from anywhere and it'll run.
If you are using our plugin generator, you will already have videojs-standard available within your project! Running
npm run lintwill run your plugin project through videojs-standard!
$ vjsstandard~/dev/my-code/src/index.js527:1 warning Line 527 exceeds the maximum line length of 90 max-len
vjsstandard will accept any number of file identifier arguments. These can be glob patterns. Some examples:
$ vjsstandard foo.js src/**/*.js
If not provided,
Produces a report that only includes errors; not warnings.
Produces a report that only includes warnings; not errors.
Instead of producing a report on the errors and warnings found in files, this will attempt to use ESLint's auto-formatting capabilities to overwrite existing files to resolve rules violations.
Outputs help on using videojs-standard.
Outputs the version number of videojs-standard.
Sometimes you need to ignore files because they represent preprocessed or minified assets, which are not appropriate for linting.
File glob patterns can be ignored by adding them to your project's
package.json as a part of a
This project should almost never change.
A rule should only change if there is a very compelling reason that the video.js core contributors have agreed upon by discussion.
Because this project can cause builds to fail, we want to avoid any potentially breaking changes outside of major versions. Because this project is mostly a collection of dependencies, any change to those dependencies will require a version change in this project equal to the highest version change in dependencies.
Combined with the rules outlined in eslint-config-videojs, this should allow common version ranges (
^) to never introduce a change that could break someone's build due to linter errors!
Apache-2.0. Copyright (c) Brightcove, Inc.