Terminal or browser

Module not found: Can't resolve '…'

What it means
The code imports a package or file that isn't there.
Likely causes
  • A new package was added but npm install hasn't run on this computer.
  • A file was renamed or moved and an import still points to the old place.
Prevention
Install dependencies after every pull.

Copy for your agent

I get “Module not found”. Run npm install, and if it persists, find the import that points to a missing file and fix it.

Full help article“Module not found” after pulling changes

Last reviewed Nov 8, 2026