# .jshintrc predef errors

**URL:** <https://discuss.emberjs.com/t/jshintrc-predef-errors/13683>\
**Category:** Ember CLI\
**Created:** [September 28, 2017, 4:02pm UTC](https://discuss.emberjs.com/t/jshintrc-predef-errors/13683 "2017-09-28T16:02:41Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![haldiggs](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/haldiggs/32/9852_2.png) [@haldiggs](https://discuss.emberjs.com/u/haldiggs)\
**Post date:** [September 28, 2017, 4:02pm UTC](https://discuss.emberjs.com/t/jshintrc-predef-errors/13683/1 "2017-09-28T16:02:41Z")

</div>

Sorry I know there are past issues that describe how to set this file up and I have been successful in past ember versions.

ember-cli: 2.14.2 ember-source: “~2.14.1”

After upgrading I started getting the “predef” errors like the .jshintrc is not being fully read.

```
"predef": [
	"document",
	"window",
	"-Promise",
	"$",
	"COMMONJS"
],

```

error ‘COMMONJS’ is not defined no-undef

error ‘$’ is not defined no-undef

Were there any changes? I’m just not sure what to try.

---

<div class="post-metadata">

**Author:** ![broerse](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/broerse/32/9497_2.png) [@broerse](https://discuss.emberjs.com/u/broerse)\
**Post date:** [September 28, 2017, 7:10pm UTC](https://discuss.emberjs.com/t/jshintrc-predef-errors/13683/2 "2017-09-28T19:10:23Z")

</div>

I believe in ember-cli 2.12.0 we switched to .eslintrc.js

You need to do something like this

> <https://github.com/ember-redux/ember-redux/pull/76/commits/b0d83e4e05a85ed25fddf84ad7c909e371414e43>
>
> another to trigger travis correctly :)

---

<div class="post-metadata">

**Author:** ![haldiggs](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/haldiggs/32/9852_2.png) [@haldiggs](https://discuss.emberjs.com/u/haldiggs)\
**Post date:** [September 29, 2017, 3:28pm UTC](https://discuss.emberjs.com/t/jshintrc-predef-errors/13683/3 "2017-09-29T15:28:31Z")

</div>

Yikes! I definitely skipped that step 🤔… I wonder why Ember keeps doing stuff like this. We have a perfectly good industry use of jshintrc but I’m guessing it wasn’t good enough… sigh

thanks!

---

<div class="post-metadata">

**Author:** ![lux](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/lux/32/13396_2.png) [@lux](https://discuss.emberjs.com/u/lux)\
**Post date:** [September 30, 2017, 1:57am UTC](https://discuss.emberjs.com/t/jshintrc-predef-errors/13683/4 "2017-09-30T01:57:40Z")

</div>

@haldiggs But, whats the problem? You don’t have to use eslint! You can use `ember-cli-jshint` as long as you wish. They just changed the blueprint, so the default for new projects and the official recommendation. However its up to you if you follow this recommendation or not. Also you can switch later at any time. Actually a lot of people switched to eslint before they changed the blueprint.