-
Notifications
You must be signed in to change notification settings - Fork 30.3k
Type-check run-tests.js and remove unused related flag
#88433
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
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Stats from current PR✅ No significant changes detected📊 All Metrics📖 Metrics GlossaryDev Server Metrics:
Build Metrics:
Change Thresholds:
⚡ Dev Server
📦 Dev Server (Webpack) (Legacy)📦 Dev Server (Webpack)
⚡ Production Builds
📦 Production Builds (Webpack) (Legacy)📦 Production Builds (Webpack)
📦 Bundle SizesBundle Sizes⚡ TurbopackClient Main Bundles: **431 kB** → **431 kB** ✅ -10 B82 files with content-based hashes (individual files not comparable between builds) Server Middleware
Build DetailsBuild Manifests
📦 WebpackClient Main Bundles
Polyfills
Pages
Server Edge SSR
Middleware
Build DetailsBuild Manifests
Build Cache
🔄 Shared (bundler-independent)Runtimes
📝 Changed Files (2 files)Files with changes:
View diffspages-api.ru..time.prod.jsDiff too large to display pages.runtime.prod.jsDiff too large to display |
The file already had the `@ts-check` directive, so the IDE did show errors in that file. But since it was not included in the root `tsconfig.json`, those errors were not reported during CI runs. One issue found this way was that the `related` flag was defined but never used. The referenced script was removed in #67644.
0df5b5c to
939ac92
Compare
Failing test suitesCommit: 939ac92 | About building and testing Next.js
Expand output● runtime prefetching › cache stale time handling › omits short-lived public caches with a short enough staleTime |
Merge activity
|

The file already had the
@ts-checkdirective, so the IDE did show errors in that file. But since it was not included in the roottsconfig.json, those errors were not reported during CI runs.One issue found this way was that the
relatedflag was defined but never used. The referenced script was removed in #67644.