Global variables in html file cause spurious eslint messages because eslint globals can not be configured

[jhorneman]

For reasons I have load a JavaScript file in CRA's index.html which defines a global variable.

CRA's eslint settings have "no-undef" set to error. Any use of the above-mentioned global variable will result in a compile error in the browser, preventing me from working.

Manually editing CRA's eslint settings to have "no-undef" be a warning is only a partial solution: I still get warnings in the console.

Manually editing the globals in CRA's eslint settings solves the problem, but is obviously not very elegant.

Ideally the development server would pick up on a .eslintrc file in the root of the project. (I've tried this, and it didn't work.)

[gaearon]

Any use of the above-mentioned global variable will result in a compile error in the browser, preventing me from working.

You can read it explicitly from the window object, e.g. const $ = window.$.
This makes it obvious it's a global variable.

You can also force ESLint to ignore any line with // eslint-disable-line.

[jhorneman]

D'oh. Thanks :)

On 28 Oct 2016, at 12:53, Dan Abramov notifications@github.com wrote:

Closed #972.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[gaearon]

It would be great to have this documented. Would you like to add this to the User Guide?

[jhorneman]

Sure. I'll send a PR.