Resolving ESLint and TypeScript issues in V0 exports

Why V0 exports produce ESLint and TypeScript errors

V0's internal sandbox runs with its own TypeScript and ESLint configuration that is more permissive than a standard Next.js project created with create-next-app. When you export V0 code via GitHub or ZIP and open it in your local IDE, stricter linting rules flag issues that V0's sandbox allowed. The most common problems are missing @types packages for libraries V0 used, the @/ path alias not being configured in tsconfig.json, unused imports and variables that V0 generated but never cleaned up, and implicit 'any' types on function parameters and API responses. These are linting and type-safety issues, not build failures — the code may still compile but your IDE shows red underlines everywhere.

• V0's sandbox includes type definitions that are not installed in the exported project's node_modules
• The @/ import alias is configured in V0's sandbox but not in the exported tsconfig.json
• V0 generates unused imports and variables that ESLint's no-unused-vars rule flags
• Function parameters and API response types default to implicit 'any' without explicit annotations
• V0 uses React 19 types internally but the exported project may target an older React version

Error messages you might see

Before you start

• V0 code exported via GitHub integration or ZIP download
• The exported project opened in a local IDE with TypeScript and ESLint enabled
• Node.js and npm installed for managing dependencies

How to fix it

{
  "compilerOptions": {
    "target": "es5",
    "lib": ["dom", "dom.iterable", "esnext"],
    "strict": true
  }
}

{
  "compilerOptions": {
    "target": "es5",
    "lib": ["dom", "dom.iterable", "esnext"],
    "strict": true,
    "baseUrl": ".",
    "paths": {
      "@/*": ["./*"]
    }
  }
}

// TypeScript error on import:
// Could not find a declaration file for module 'canvas-confetti'
import confetti from "canvas-confetti";

// After adding @types/canvas-confetti to devDependencies
// in package.json: "@types/canvas-confetti": "^1.6.4"
import confetti from "canvas-confetti"; // No error

try {
  await fetchData();
} catch (error) {
  // ESLint: 'error' is defined but never used
  console.log("Failed to fetch");
}
function handleChange(event: React.ChangeEvent<HTMLInputElement>) {
  // ESLint: 'event' is defined but never used
  setLoading(true);
}

try {
  await fetchData();
} catch (_error) {
  // Underscore prefix tells ESLint this is intentionally unused
  console.log("Failed to fetch");
}
function handleChange(_event: React.ChangeEvent<HTMLInputElement>) {
  // Or better — remove the parameter if not needed:
  // function handleChange() {
  setLoading(true);
}

const handleSubmit = (e) => {
  e.preventDefault();
  // ts(7006): Parameter 'e' implicitly has an 'any' type
};
const handleClick = (item) => {
  setSelected(item);
};

const handleSubmit = (e: React.FormEvent<HTMLFormElement>) => {
  e.preventDefault();
};
interface Item {
  id: string;
  name: string;
}
const handleClick = (item: Item) => {
  setSelected(item);
};

Complete code example

1{
2  "compilerOptions": {
3    "target": "es2017",
4    "lib": ["dom", "dom.iterable", "esnext"],
5    "allowJs": true,
6    "skipLibCheck": true,
7    "strict": true,
8    "noEmit": true,
9    "esModuleInterop": true,
10    "module": "esnext",
11    "moduleResolution": "bundler",
12    "resolveJsonModule": true,
13    "isolatedModules": true,
14    "jsx": "preserve",
15    "incremental": true,
16    "plugins": [
17      {
18        "name": "next"
19      }
20    ],
21    "baseUrl": ".",
22    "paths": {
23      "@/*": ["./*"]
24    }
25  },
26  "include": ["next-env.d.ts", "**/*.ts", "**/*.tsx", ".next/types/**/*.ts"],
27  "exclude": ["node_modules"]
28}

Best practices to prevent this

• Always configure the @/ path alias in tsconfig.json immediately after exporting V0 code — it is required for all V0-generated imports
• Run the TypeScript compiler with --noEmit to check for type errors without building: npx tsc --noEmit
• Install @types packages for every third-party library V0 used — check package.json dependencies and search for matching @types
• Set skipLibCheck: true in tsconfig.json to bypass type errors in node_modules that you cannot fix
• Prefix intentionally unused catch block variables with an underscore to satisfy no-unused-vars without suppressing the rule globally
• For exported projects with many linting issues, RapidDev can audit and fix all TypeScript and ESLint errors efficiently

Still stuck?

Copy one of these prompts to get a personalized, step-by-step explanation.

Related error patterns

Explore related guides

Guides from other topics that help with this issue