This repository has been archived by the owner on Aug 18, 2021. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 239
error 'App' is not defined no-undef #29
Comments
Nothing, it's a bug. |
Seems to be a dupe of #8. |
Nope. Actually it's a dupe of #15. |
BenoitZugmeyer
added a commit
to BenoitZugmeyer/babel-eslint
that referenced
this issue
Mar 7, 2015
When specifying "module" to escope sourceType option, defined variables will be stored in "module" scope instead of the "global" scope. Because eslint doesn't support module scopes yet, it will ignore this scope when the rule "no-undef" gets the current scope to check for JSX variables definitions. Fixes babel#15 and babel#29
Probably need to check this with eslint 0.17 changes for jsx and react. |
I am not having the issue anymore with eslint 0.17 and eslint-plugin-react 1.5.0 |
Can you please verify that this issue still exists on 3.0.1? |
Is this still an issue after using |
Not at all. You can close this. Eslint doesn't handle this anymore & the plugin does this like a charm. |
Ok great! |
From eslint docs we can find these rules,
/*global someFunction b:true*/
/*eslint no-undef: "error"*/
var a = someFunction();
b = 10; |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
I get the following error:
Here is my
.eslintrc
file:I use
babel-loader
to run eslint with WebPack. Here is the relevant bit fromwebpack.config.js
:What am I doing wrong?
The text was updated successfully, but these errors were encountered: