Well, this is something that will land you in a dangerous situation. But sometimes deploying your build becomes more important than fixing the type error which you are getting and you are not able to fix.
If you are having a NextJs app, and you want to ignore eslint errors, type errors during build creation , just as the below rules in your next.config file
<pre><code class="lang-plaintext">module.exports = {

 eslint: {
 // Dangerously allow production builds to successfully complete even if your project has eslint errors.
 ignoreDuringBuilds: true,
 },
 typescript: {
 // Dangerously allow production builds to successfully complete even if your project has type errors.
 ignoreBuildErrors: true,
 }

}
</code></pre>
For now you can ignore the errors, but do not forget to solve them later :)
Thats it for the day. Keep exploring!!

Well, this is something that will land you in a dangerous situation. But sometimes deploying your build becomes more important than fixing the type error which you are getting and you are not able to fix.

If you are having a NextJs app, and you want to ignore eslint errors, type errors during build creation , just as the below rules in your next.config file

```plaintext
module.exports = {

  eslint: {
    // Dangerously allow production builds to successfully complete even if your project has eslint errors.
    ignoreDuringBuilds: true,
  },
  typescript: {
    // Dangerously allow production builds to successfully complete even if your project has type errors.
    ignoreBuildErrors: true,
  }

} 
```

For now you can ignore the errors, but do not forget to solve them later :)

Thats it for the day. Keep exploring!!

How to ignore eslint errors, type errors in nextjs build!