How to Ignore TypeScript Errors During Vercel Build

Introduction

You are 5 minutes away from a demo. You push your code. Vercel fails. "Type 'string | null' is not assignable to type 'string'."

You know the code works. You just haven't fixed the types yet. But Vercel's default setting is "Zero Tolerance"—if there is one TS error, the deploy fails.

Here is the emergency switch to force the deployment through.

The Emergency Switch

How do I disable TypeScript checks in Vercel?

To disable TypeScript checks during the Vercel build, you need to modify your next.config.js (or .mjs) file. Add the typescript object with ignoreBuildErrors: true. This tells the build process to complete even if the type checker reports issues.

// next.config.mjs
/** @type {import('next').NextConfig} */
const nextConfig = {
  typescript: {
    // !! WARN !!
    // Dangerously allow production builds to successfully complete even if
    // your project has type errors.
    // !! WARN !!
    ignoreBuildErrors: true,
  },
  eslint: {
    // Bonus: Ignore lint errors too
    ignoreDuringBuilds: true,
  },
};

export default nextConfig;

Is This A Bad Idea?

Short answer: Yes, but...

Long answer: TypeScript is there to catch bugs. If you ignore errors, you might deploy code that crashes at runtime (like trying to .map() over a null value).

When to use this:

1. MVP Demos: You need it live now.
2. Legacy Migrations: You are converting a JS project to TS and have 500 errors.
3. Prototyping: The logic is sound, but the types are messy.

When NOT to use this:

1. Enterprise Production: Never.
2. Payment Logic: Never.

FlowQL: The Path to Type Safety

At FlowQL, we often inherit codebases where this setting was turned on 6 months ago and never turned off. The result is a fragile app that developers are afraid to touch.

We help teams execute "Type Safety Sprints"—cleaning up the any types and removing the ignoreBuildErrors crutch so you can deploy with real confidence.

Conclusion

Your Action Plan:

1. Edit: next.config.mjs
2. Deploy: Get your feature live.
3. Refactor: Create a ticket to turn this setting OFF next week.

Ship now, fix later. [Book a session with FlowQL] when "later" becomes "now."