[docs] Recommend disabling static analysis to combat build OOM iff CI already handles that #69186
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Preview
Larger apps may encounter OOM in builds during static analysis (eslint+ts). Most larger apps already have a dedicated CI which is better suited for these tasks.
This may result in deploy of broken builds but so is deploying without waiting for tests.
The added section specifically talks about OOM and recommends manual promotion after static analysis. How to do CI/CD properly is its own industry though so we shouldn't be too opinionated in smaller sections and just describe what tools are available.
Closes https://linear.app/vercel/issue/NEXT-3690