eba9fca3ff
This consolidates our trace handling between turbotrace and the default `nodeFileTrace` handling to prevent over-tracing. With node-file-trace it's extremely more efficient to trace in a single `nodeFileTrace` run so that all resolving/analysis etc can be efficiently cached. Furthermore, this reduces the amount of chunks we need to trace by waiting until post build since automatically statically optimized paths don't need to be traced as they are rendered to purely HTML and never re-rendered. This reduces builds times by upwards of 4 - 5 minutes on larger projects. |
||
|---|---|---|
| .. | ||
| components | ||
| lib | ||
| node_modules/mypackage | ||
| pages | ||
| test | ||
| .gitignore | ||
| jsconfig.json | ||
| next.config.js | ||