Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in
Toggle navigation
N
next.js
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Alex
next.js
Commits
bcd9c19a
Unverified
Commit
bcd9c19a
authored
Mar 18, 2026
by
Joseph
Committed by
GitHub
Mar 18, 2026
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
docs: Clarify ignoreBuildErrors behavior (#91367)
Just a complementary note to the TS config reference.
parent
3683192a
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
0 deletions
+2
-0
typescript.mdx
...-api-reference/05-config/01-next-config-js/typescript.mdx
+2
-0
No files found.
docs/01-app/03-api-reference/05-config/01-next-config-js/typescript.mdx
View file @
bcd9c19a
...
...
@@ -29,6 +29,8 @@ Next.js fails your **production build** (`next build`) when TypeScript errors ar
If you'd like Next.js to dangerously produce production code even when your application has errors, you can disable the built-in type checking step.
Note that this completely skips the TypeScript type checking step. It does not run TypeScript and suppress errors, it bypasses the check entirely.
If disabled, be sure you are running type checks as part of your build or deploy process, otherwise this can be very dangerous.
```js filename="next.config.js"
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment