<!-- [][ember-observer-badge-url]
[ember-observer-badge-url]: https://emberobserver.com/addons/ember-cli-eslint -->
ESLint for Ember CLI apps and addons
ESLint 3 (for Node 4 and above):
ember install ember-cli-eslint@3
ESLint 2 (for Node 0.10 and above):
ember install ember-cli-eslint@2
After installation, an .eslintrc.js
file will be placed in both the root of
your project and the /tests
directory.
Furthermore, a .eslintignore
file can be used to exclude files from
linting while the linter is running. Its syntax is identical to
.gitignore
files.
Congratulations! You've made the leap into the next generation of JavaScript
linting. At the moment, however, ember-cli
defaults to generating
applications and addons with a jshint
configuration.
If you notice the two awkwardly running side by side, click here!
As of ember-cli v.2.5.0
,
jshint
is provided through its own ember-cli-jshint
addon.
Running npm uninstall --save-dev ember-cli-jshint
, in addition to removing
any .jshintrc
files from your project should guarantee that its behavior
is disabled.
Controlling linting is a bit trickier on versions of ember-cli
prior to
2.5.0
. Within your ember-cli-build.js
file, ember-cli-qunit
or
ember-cli-mocha
can be configured to have their default linting process
disabled during:
module.exports = function(defaults) {
const app = new EmberApp(defaults, {
'ember-cli-qunit': {
useLintTree: false
}
});
};
or
module.exports = function(defaults) {
const app = new EmberApp(defaults, {
'ember-cli-mocha': {
useLintTree: false
}
});
};
Alongside this setting, the hinting
property can then be used to
enable/disable globally:
const isTesting = process.env.EMBER_ENV === 'test';
module.exports = function(defaults) {
const app = new EmberApp(defaults, {
hinting: !isTesting,
});
};
ESLint will be run by ember-cli-qunit
or ember-cli-mocha
automatically
when you run ember test
. If ESLint is not being run automatically, try
updating your ember-cli
and/or ember-cli-qunit
/ember-cli-mocha
dependencies.
Please note that if you are using this to lint files which are part of the build
process (ie. index.js, ember-cli-build.js, config/), whether in an application or
as part of an addon, they will not be linted. It is recommended that eslint
is
setup separately to lint these files and can be setup as an npm script and run as
part of a CI process.
git clone
this repositorynpm install
bower install
ember server
- Visit your app at http://localhost:4200.
npm test
(Runsember try:testall
to test your addon against multiple Ember versions)ember test
ember test --server
ember build
For more information on using ember-cli, visit https://ember-cli.com/.
This project is licensed under the MIT License.