Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[docs] Recommend disabling static analysis to combat build OOM iff CI already handles that #69186

Open
wants to merge 1 commit into
base: canary
Choose a base branch
from

Conversation

eps1lon
Copy link
Member

@eps1lon eps1lon commented Aug 22, 2024

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

@ijjk ijjk added created-by: Next.js team PRs by the Next.js team. Documentation Related to Next.js' official documentation. labels Aug 22, 2024
Copy link
Member Author

eps1lon commented Aug 22, 2024

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @eps1lon and the rest of your teammates on Graphite Graphite

@eps1lon eps1lon marked this pull request as ready for review August 22, 2024 15:23
@eps1lon eps1lon force-pushed the sebbie/08-22-_docs_recommend_disabling_static_analysis_to_combat_build_oom_iff_ci_already_handles_that branch from f5751b0 to 6ab9fd1 Compare August 22, 2024 15:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
created-by: Next.js team PRs by the Next.js team. Documentation Related to Next.js' official documentation.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants