A global from a script tag in index.html is 'not defined' in React
'Widget' is not defined no-undefShort answer
A script in index.html creates a global at runtime, but your tools do not know it exists. ESLint reports it with no-undef until you declare it as a global. If it fails at run time, the script has not run yet: check async and defer, which change when the script executes.
Fix it fast
1Find out which cause you have
Run the check in the browser console on the loaded page. If the name exists there, only the linter is complaining. If it does not, the script has not run or failed to load.
typeof Widget2Match what you see, then jump to its fix
What does the error look like?
'Widget' is not defined no-undef
Cause 1 of 2
ESLint does not know the script's global
1Check
The no-undef rule reports any use of an undeclared variable. A script loaded in index.html is invisible to it.
npx eslint src/App.jsx2Fix
Declare the name as a global in the file with a comment, or add it to the globals key in your ESLint configuration.
/* global Widget */
export default function App() {
return <button onClick={() => Widget.open()}>Open</button>;
}3Verify
Run ESLint again; the no-undef line is gone.
npx eslint src/App.jsxConfirmed by eslint.org
Cause 2 of 2
The script runs after your code, or not in the order you expect
1Check
A script with async runs as soon as it is downloaded and its order is not guaranteed. A script with defer runs after the document is parsed, in document order. A script with neither blocks parsing and runs first.
grep -n "<script" index.html public/index.html2Fix
Load the third-party script without async, or with defer placed before your app's own script, and read the global only inside functions that run later (such as an event handler or an effect).
<script src="https://example.com/widget.js"></script>
<script type="module" src="/src/main.jsx"></script>3Verify
Reload the page and check typeof Widget in the console, before any click.
typeof WidgetConfirmed by developer.mozilla.org
How do I stop it coming back?
- Declare every browser global your code uses in the ESLint config, once, instead of per file.
- Read script globals inside event handlers or effects, never at module top level.
- Prefer an npm package for a library when one exists, so imports replace globals.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- TaskvareA task and project-management suite: React on the web, Flutter on mobile, TypeScript underneath.
Related fixes
Web apps
Module not found for antd/dist/antd.less after upgrading to Ant Design 5
Module not found: Error: Can't resolve 'antd/dist/antd.less'
Ant Design 5 dropped Less and the bundled CSS file for CSS-in-JS, so antd/dist/antd.less no longer exists.
3 causes, each with a fixWeb apps
Astro Code component fails inside a React component
Astro components cannot be rendered directly via function call
Astro components such as Code only exist on the server and render static HTML.
2 causes, each with a fixWeb apps
React shows Attempted import error when importing a component or function
Attempted import error:
The build found the file but not the name you asked for.
2 causes, each with a fixWeb apps
How to catch and handle a 422 from Axios in a Redux thunk
action.error.message is 'Rejected' and action.payload is undefined
A 422 means the server read the request but cannot process its content, so repeating it unchanged fails again.
4 causes, each with a fixWeb apps
axios gets 429 Too Many Requests from a React app
429 (Too Many Requests)
A 429 comes from the server or an API gateway, not from axios: your client sent too many requests in a window.
4 causes, each with a fixWeb apps
Axios request is not cancelled when a React component unmounts
A cancelled request is logged as an error in the catch block
Axios cancels a request when you pass it an AbortSignal and later call abort() on its controller.
4 causes, each with a fix