TypeScript does not know the property you added to window
Property 'myAppConfig' does not exist on type 'Window & typeof globalThis'.Short answer
TypeScript only knows the properties of Window it was given. A value added by a script tag, an SDK or your own code is unknown to it. Declare it once by merging into the Window interface inside declare global, in a file that is a module, and make sure tsconfig includes the file.
Fix it fast
1Find out which cause you have
Find where the property is read and whether any declaration file mentions Window already.
grep -rn "interface Window\|declare global" src/ *.d.ts2Match what you see, then jump to its fix
What does the error look like?
Property 'myAppConfig' does not exist on type 'Window & typeof globalThis'.Property 'dataLayer' does not exist on type 'Window'.
Cause 1 of 2
The property was never declared on Window
1Check
Interfaces with the same name merge their members into one interface, and global augmentation adds declarations to the global scope from inside a module.
grep -rn "window\.myAppConfig" src/2Fix
Add a declaration file that augments the global Window interface. The export {} line makes the file a module, which declare global requires.
// src/global.d.ts
export {};
declare global {
interface Window {
myAppConfig: { apiUrl: string };
}
}3Verify
Type-check the project.
npx tsc --noEmitConfirmed by typescriptlang.org
Cause 2 of 2
The declaration exists but tsconfig does not include it
1Check
A declaration only applies when the compiler reads the file. Check which files tsconfig includes.
npx tsc --listFilesOnly | grep global.d.ts2Fix
Put the file under a folder listed in include, or add it explicitly, then restart the editor's TypeScript server.
{
"include": ["src", "src/global.d.ts"]
}3Verify
The file now shows in the listing and the error is gone.
npx tsc --listFilesOnly | grep global.d.ts && npx tsc --noEmitConfirmed by vite.dev
How do I stop it coming back?
- Keep all global augmentations in one global.d.ts file.
- Declare the property as optional (?) if it may not exist at runtime.
- Do not cast window to any; the declaration documents what exists.
- Declare only what you use, and check for it at runtime when a script may fail to load.
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
TypeScript refuses JSX because the jsx option is not set
TS17004: Cannot use JSX unless the '--jsx' flag is provided.
TypeScript compiles JSX only when you name the file with a .tsx extension and enable the jsx compiler option.
2 causes, each with a fixWeb apps
TypeScript rejects a component that returns an array or other non-Element
Its return type 'Element[]' is not a valid JSX element.
TypeScript before 5.1 required every component to return JSX.Element or null, so arrays, strings and Promises were rejected even though React renders them.
2 causes, each with a fixWeb apps
ESLint says it cannot resolve a path to a module that does exist
Unable to resolve path to module 'react'. import/no-unresolved
import/no-unresolved fails when eslint-plugin-import cannot find the file or package on disk with its resolver.
4 causes, each with a fixWeb apps
ESLint reports no-unused-vars for React components and imports that are used
no-unused-vars reported for a component that is rendered as a JSX tag
ESLint's core no-unused-vars does not see variables used only as JSX tags, so a component imported and rendered as <Hello /> looks unused.
3 causes, each with a fixWeb apps
TypeScript rejects MUI Data Grid columns that set a type
A TypeScript error inside a column's renderCell callback
A columns array declared without a type is inferred with type as a plain string, which the Data Grid's column type union does not accept.
2 causes, each with a fixWeb apps
The renderInput prop stopped working on the MUI X DatePicker
The custom TextField (variant, size, helperText) is ignored
renderInput was removed from the MUI X date pickers in version 6.
3 causes, each with a fix