TypeScript cannot find the module @tanstack/react-query
Cannot find module '@tanstack/react-query' or its corresponding type declarations.Short answer
Either the package is not installed under this exact name, or the editor cannot see it. Install @tanstack/react-query with your package manager. If you use Yarn Plug'n'Play, the editor's TypeScript needs the Yarn SDK, so the command-line build passes while VS Code still shows the error.
Fix it fast
1Find out which cause you have
Check whether the package is in package.json and whether tsc itself reports the error, or only the editor does.
grep -n "react-query" package.json npx tsc --noEmit2Match what you see, then jump to its fix
What does the error look like?
Cannot find module '@tanstack/react-query' or its corresponding type declarations.
Cause 1 of 2
The package is not installed under this name
1Check
The install page names the package @tanstack/react-query. If it is missing from package.json, or listed under a different name, TypeScript has nothing to resolve.
grep -n "react-query" package.json2Fix
Install the package with the manager your project uses, then reinstall dependencies.
npm i @tanstack/react-query
# or: pnpm add @tanstack/react-query
# or: yarn add @tanstack/react-query3Verify
Compile the project again.
npx tsc --noEmitConfirmed by tanstack.com
Cause 2 of 2
Yarn Plug'n'Play: the editor does not load the PnP loader
1Check
Yarn PnP works by generating a Node.js loader, and many editor tools run packages without using it, so they cannot resolve modules.
ls .pnp.cjs2Fix
Generate the editor SDK, install the ZipFS extension, and choose the workspace TypeScript version in VS Code. The SDK command reads the root package.json, so typescript must be listed there.
yarn dlx @yarnpkg/sdks vscode
# then in VS Code: ctrl+shift+p > Select TypeScript Version > Use Workspace Version3Verify
Reopen the file; the error is gone and imports from @tanstack/react-query resolve.
yarn tsc --noEmitConfirmed by yarnpkg.com
How do I stop it coming back?
- Add typescript to the root package.json of every Yarn PnP repo.
- Commit the generated .yarn/sdks and .vscode/settings.json files so the team shares the editor setup.
- Keep TypeScript on a version that TanStack Query supports; its docs name the minimum.
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