-
Notifications
You must be signed in to change notification settings - Fork 27.2k
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
fix(next-lint): update option --report-unused-disable-directives to --report-unused-disable-directives-severity #64405
Conversation
This option accepts an argument, but was not looking for one which resulted in unexpected behavior.
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
Tests Passed |
Stats from current PRDefault BuildGeneral Overall increase
|
vercel/next.js canary | coltonehrman/next.js fix/next-cli-lint | Change | |
---|---|---|---|
buildDuration | 14s | 14s | N/A |
buildDurationCached | 8.4s | 6.2s | N/A |
nodeModulesSize | 199 MB | 199 MB | |
nextStartRea..uration (ms) | 402ms | 399ms | N/A |
Client Bundles (main, webpack)
vercel/next.js canary | coltonehrman/next.js fix/next-cli-lint | Change | |
---|---|---|---|
2453-HASH.js gzip | 31.4 kB | 31.4 kB | N/A |
3304.HASH.js gzip | 181 B | 181 B | ✓ |
3f784ff6-HASH.js gzip | 53.7 kB | 53.7 kB | ✓ |
8299-HASH.js gzip | 5.1 kB | 5.1 kB | N/A |
framework-HASH.js gzip | 45.2 kB | 45.2 kB | ✓ |
main-app-HASH.js gzip | 242 B | 242 B | ✓ |
main-HASH.js gzip | 32.2 kB | 32.2 kB | N/A |
webpack-HASH.js gzip | 1.68 kB | 1.68 kB | N/A |
Overall change | 99.3 kB | 99.3 kB | ✓ |
Legacy Client Bundles (polyfills)
vercel/next.js canary | coltonehrman/next.js fix/next-cli-lint | Change | |
---|---|---|---|
polyfills-HASH.js gzip | 31 kB | 31 kB | ✓ |
Overall change | 31 kB | 31 kB | ✓ |
Client Pages
vercel/next.js canary | coltonehrman/next.js fix/next-cli-lint | Change | |
---|---|---|---|
_app-HASH.js gzip | 196 B | 197 B | N/A |
_error-HASH.js gzip | 184 B | 184 B | ✓ |
amp-HASH.js gzip | 505 B | 505 B | ✓ |
css-HASH.js gzip | 324 B | 325 B | N/A |
dynamic-HASH.js gzip | 2.5 kB | 2.5 kB | N/A |
edge-ssr-HASH.js gzip | 258 B | 258 B | ✓ |
head-HASH.js gzip | 352 B | 352 B | ✓ |
hooks-HASH.js gzip | 370 B | 371 B | N/A |
image-HASH.js gzip | 4.27 kB | 4.27 kB | ✓ |
index-HASH.js gzip | 259 B | 259 B | ✓ |
link-HASH.js gzip | 2.67 kB | 2.67 kB | N/A |
routerDirect..HASH.js gzip | 314 B | 312 B | N/A |
script-HASH.js gzip | 386 B | 386 B | ✓ |
withRouter-HASH.js gzip | 309 B | 309 B | ✓ |
1afbb74e6ecf..834.css gzip | 106 B | 106 B | ✓ |
Overall change | 6.63 kB | 6.63 kB | ✓ |
Client Build Manifests
vercel/next.js canary | coltonehrman/next.js fix/next-cli-lint | Change | |
---|---|---|---|
_buildManifest.js gzip | 483 B | 485 B | N/A |
Overall change | 0 B | 0 B | ✓ |
Rendered Page Sizes
vercel/next.js canary | coltonehrman/next.js fix/next-cli-lint | Change | |
---|---|---|---|
index.html gzip | 529 B | 528 B | N/A |
link.html gzip | 541 B | 541 B | ✓ |
withRouter.html gzip | 524 B | 523 B | N/A |
Overall change | 541 B | 541 B | ✓ |
Edge SSR bundle Size
vercel/next.js canary | coltonehrman/next.js fix/next-cli-lint | Change | |
---|---|---|---|
edge-ssr.js gzip | 95.6 kB | 95.6 kB | N/A |
page.js gzip | 3.06 kB | 3.06 kB | ✓ |
Overall change | 3.06 kB | 3.06 kB | ✓ |
Middleware size
vercel/next.js canary | coltonehrman/next.js fix/next-cli-lint | Change | |
---|---|---|---|
middleware-b..fest.js gzip | 622 B | 625 B | N/A |
middleware-r..fest.js gzip | 155 B | 156 B | N/A |
middleware.js gzip | 25.5 kB | 25.5 kB | N/A |
edge-runtime..pack.js gzip | 839 B | 839 B | ✓ |
Overall change | 839 B | 839 B | ✓ |
Next Runtimes
vercel/next.js canary | coltonehrman/next.js fix/next-cli-lint | Change | |
---|---|---|---|
app-page-exp...dev.js gzip | 171 kB | 171 kB | ✓ |
app-page-exp..prod.js gzip | 97.4 kB | 97.4 kB | ✓ |
app-page-tur..prod.js gzip | 99.2 kB | 99.2 kB | ✓ |
app-page-tur..prod.js gzip | 93.4 kB | 93.4 kB | ✓ |
app-page.run...dev.js gzip | 144 kB | 144 kB | ✓ |
app-page.run..prod.js gzip | 91.9 kB | 91.9 kB | ✓ |
app-route-ex...dev.js gzip | 21.4 kB | 21.4 kB | ✓ |
app-route-ex..prod.js gzip | 15.2 kB | 15.2 kB | ✓ |
app-route-tu..prod.js gzip | 15.2 kB | 15.2 kB | ✓ |
app-route-tu..prod.js gzip | 14.9 kB | 14.9 kB | ✓ |
app-route.ru...dev.js gzip | 21.1 kB | 21.1 kB | ✓ |
app-route.ru..prod.js gzip | 14.9 kB | 14.9 kB | ✓ |
pages-api-tu..prod.js gzip | 9.55 kB | 9.55 kB | ✓ |
pages-api.ru...dev.js gzip | 9.82 kB | 9.82 kB | ✓ |
pages-api.ru..prod.js gzip | 9.55 kB | 9.55 kB | ✓ |
pages-turbo...prod.js gzip | 22.5 kB | 22.5 kB | ✓ |
pages.runtim...dev.js gzip | 23.1 kB | 23.1 kB | ✓ |
pages.runtim..prod.js gzip | 22.5 kB | 22.5 kB | ✓ |
server.runti..prod.js gzip | 51.3 kB | 51.3 kB | ✓ |
Overall change | 948 kB | 948 kB | ✓ |
build cache
vercel/next.js canary | coltonehrman/next.js fix/next-cli-lint | Change | |
---|---|---|---|
0.pack gzip | 1.59 MB | 1.58 MB | N/A |
index.pack gzip | 107 kB | 106 kB | N/A |
Overall change | 0 B | 0 B | ✓ |
Diff details
Diff for middleware.js
Diff too large to display
@coltonehrman Thanks for this |
No problem! :) I'd be happy to add a test as well I just wasn't sure the best way to go about that. Are there any CLI/lint command test setups I can follow? |
@coltonehrman it should be a Boolean actually |
I tried it as a boolean and got this error:
|
@coltonehrman Interesting—are their |
Very likely lol |
@coltonehrman Looks like this needs to be re-named to https://eslint.org/docs/latest/use/command-line-interface#--report-unused-disable-directives-severity |
What version of ESLint is Next.js using? Maybe the APIs are different? |
@coltonehrman It doesn't seem like that was updated → https://eslint.org/docs/v8.x/use/command-line-interface#--report-unused-disable-directives-severity. Next.js is still on v8. |
The docs don't seem to be in sync with the behavior then (or even perhaps the version of ESLint Next.js is using has a bug). The flag that is suppose to be boolean doesn't appear to support a boolean value when ran and results in an error. However, as you pointed out, it does appear that the |
@coltonehrman I'll push up the changes to make this |
@samcx Just out of curiosity, what is the reason for taking over control of the lint command via Next.js vs passing through options to the underlying tool (ie: ESLint)? I feel like this would cause more issues and be harder to maintain. |
@coltonehrman That's a good question—I think the idea is we give you good defaults. So when you simply do |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
…-report-unused-disable-directives-severity (#64405) ## Why? The Option name and type has been incorrect for `--report-unused-disable-directives` (it's likely that #61877 exposed this. For correctness, we have updated the name to `--report-unsed-disable-directives-severity` → https://eslint.org/docs/v8.x/use/command-line-interface#--report-unused-disable-directives-severity. - Fixes #64402 --------- Co-authored-by: samcx <sam@vercel.com>
Why?
The Option name and type has been incorrect for
--report-unused-disable-directives
(it's likely that #61877 exposed this.For correctness, we have updated the name to
--report-unsed-disable-directives-severity
→ https://eslint.org/docs/v8.x/use/command-line-interface#--report-unused-disable-directives-severity.