Back to 🔧 Developer Experience

Debug 'Module Not Found' After Git Pull

DebuggingGitDependenciesTroubleshooting
---
description: Fix dependency issues after pulling changes from Git
---

1. **Clear Node Modules Cache**:
- Remove cached modules and reinstall.
// turbo
- Run rm -rf node_modules .next && npm install

2. **Check for Lockfile Conflicts**:
- Look for merge conflicts in package-lock.json.
// turbo
- Run git diff package-lock.json
- If conflicted, regenerate: rm package-lock.json && npm install

3. **Install Missing Peer Dependencies**:
- Check for peer dependency warnings.
// turbo
- Run npm install --legacy-peer-deps

4. **Fix Monorepo Workspace Issues**:
- If using pnpm workspaces, reinstall from root.
// turbo
- Run pnpm install --force

5. **Update TypeScript Paths**:
- Regenerate path mappings if tsconfig changed.
// turbo
- Run npx tsc --noEmit

6. **Pro Tips**:
- Use npm ci instead of npm install in CI/CD for reproducible builds.
- Check if .npmrc or .yarnrc was updated.
- Restart your IDE/TypeScript server after reinstalling.
By Antigravity Team

How to Use This Workflow

Option A: Project-Specific (Recommended)

  1. Click "Download" above
  2. In your project, create the directory: .agent/workflows/
  3. Save the file as debug-module-not-found-after-git-pull.md
  4. In Antigravity, type /debug_module_not_found_after_git_pull or just describe what you want to do

Learn more about workflows →

Related Workflows

Recommended Rules

View more rules →

Recommended MCP Servers

View more MCP servers →

Take It Further

Maximize your productivity with these powerful resources

📋

Define Your Standards

Set up coding standards to ensure this workflow produces consistent, high-quality results.

Browse Rules Library
📖

Master Workflows

Learn how to create custom workflows, use Turbo Mode, and build your automation library.

Complete Guide