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

Clean-up error when starting next with non-existent dir #34830

Merged
merged 1 commit into from Feb 25, 2022

Conversation

ijjk
Copy link
Member

@ijjk ijjk commented Feb 25, 2022

This ensures we show a proper error when a non-existent directory is passed to Next.js as the current error shown is quite noisy.

before before
after after

stderr: true,
})
expect(output.stderr).toContain(
'Invalid project directory provided, no such directory'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the case when no command is provided, we could also print a help screen.

For example next buidl could print:

Invalid project directory provided `buildl`, no such directory.

Did you mean to run a subcommand instead?

next build
next start
next export

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, maybe we can add detecting mis-spellings of the main commands here, will investigate in a follow-up

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Opened PR adding this here #34836

Copy link
Member

@styfle styfle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! This is a big improvement 🎉

@ijjk
Copy link
Member Author

ijjk commented Feb 25, 2022

Stats from current PR

Default Build (Decrease detected ✓)
General Overall increase ⚠️
vercel/next.js canary ijjk/next.js fix/invalid-project-dir Change
buildDuration 15.6s 15.7s ⚠️ +88ms
buildDurationCached 6.1s 6.1s -16ms
nodeModulesSize 367 MB 367 MB ⚠️ +573 B
Page Load Tests Overall decrease ⚠️
vercel/next.js canary ijjk/next.js fix/invalid-project-dir Change
/ failed reqs 0 0
/ total time (seconds) 2.935 2.971 ⚠️ +0.04
/ avg req/sec 851.72 841.47 ⚠️ -10.25
/error-in-render failed reqs 0 0
/error-in-render total time (seconds) 1.33 1.336 ⚠️ +0.01
/error-in-render avg req/sec 1879.42 1871.06 ⚠️ -8.36
Client Bundles (main, webpack)
vercel/next.js canary ijjk/next.js fix/invalid-project-dir Change
450.HASH.js gzip 179 B 179 B
framework-HASH.js gzip 42 kB 42 kB
main-HASH.js gzip 27.8 kB 27.8 kB
webpack-HASH.js gzip 1.44 kB 1.44 kB
Overall change 71.5 kB 71.5 kB
Legacy Client Bundles (polyfills)
vercel/next.js canary ijjk/next.js fix/invalid-project-dir Change
polyfills-HASH.js gzip 31 kB 31 kB
Overall change 31 kB 31 kB
Client Pages
vercel/next.js canary ijjk/next.js fix/invalid-project-dir Change
_app-HASH.js gzip 1.36 kB 1.36 kB
_error-HASH.js gzip 194 B 194 B
amp-HASH.js gzip 312 B 312 B
css-HASH.js gzip 326 B 326 B
dynamic-HASH.js gzip 2.57 kB 2.57 kB
head-HASH.js gzip 350 B 350 B
hooks-HASH.js gzip 919 B 919 B
image-HASH.js gzip 5.05 kB 5.05 kB
index-HASH.js gzip 263 B 263 B
link-HASH.js gzip 2.26 kB 2.26 kB
routerDirect..HASH.js gzip 321 B 321 B
script-HASH.js gzip 383 B 383 B
withRouter-HASH.js gzip 318 B 318 B
85e02e95b279..7e3.css gzip 107 B 107 B
Overall change 14.7 kB 14.7 kB
Client Build Manifests
vercel/next.js canary ijjk/next.js fix/invalid-project-dir Change
_buildManifest.js gzip 460 B 460 B
Overall change 460 B 460 B
Rendered Page Sizes
vercel/next.js canary ijjk/next.js fix/invalid-project-dir Change
index.html gzip 530 B 530 B
link.html gzip 544 B 544 B
withRouter.html gzip 526 B 526 B
Overall change 1.6 kB 1.6 kB

Default Build with SWC (Increase detected ⚠️)
General Overall increase ⚠️
vercel/next.js canary ijjk/next.js fix/invalid-project-dir Change
buildDuration 18.9s 19.2s ⚠️ +366ms
buildDurationCached 6.1s 6.1s -15ms
nodeModulesSize 367 MB 367 MB ⚠️ +573 B
Page Load Tests Overall increase ✓
vercel/next.js canary ijjk/next.js fix/invalid-project-dir Change
/ failed reqs 0 0
/ total time (seconds) 2.947 2.972 ⚠️ +0.02
/ avg req/sec 848.3 841.09 ⚠️ -7.21
/error-in-render failed reqs 0 0
/error-in-render total time (seconds) 1.347 1.33 -0.02
/error-in-render avg req/sec 1855.58 1879.61 +24.03
Client Bundles (main, webpack)
vercel/next.js canary ijjk/next.js fix/invalid-project-dir Change
450.HASH.js gzip 179 B 179 B
framework-HASH.js gzip 42.1 kB 42.1 kB
main-HASH.js gzip 27.8 kB 27.8 kB
webpack-HASH.js gzip 1.44 kB 1.44 kB
Overall change 71.6 kB 71.6 kB
Legacy Client Bundles (polyfills)
vercel/next.js canary ijjk/next.js fix/invalid-project-dir Change
polyfills-HASH.js gzip 31 kB 31 kB
Overall change 31 kB 31 kB
Client Pages
vercel/next.js canary ijjk/next.js fix/invalid-project-dir Change
_app-HASH.js gzip 1.35 kB 1.35 kB
_error-HASH.js gzip 180 B 180 B
amp-HASH.js gzip 305 B 305 B
css-HASH.js gzip 321 B 321 B
dynamic-HASH.js gzip 2.56 kB 2.56 kB
head-HASH.js gzip 342 B 342 B
hooks-HASH.js gzip 911 B 911 B
image-HASH.js gzip 5.08 kB 5.08 kB
index-HASH.js gzip 256 B 256 B
link-HASH.js gzip 2.28 kB 2.28 kB
routerDirect..HASH.js gzip 314 B 314 B
script-HASH.js gzip 375 B 375 B
withRouter-HASH.js gzip 309 B 309 B
85e02e95b279..7e3.css gzip 107 B 107 B
Overall change 14.7 kB 14.7 kB
Client Build Manifests
vercel/next.js canary ijjk/next.js fix/invalid-project-dir Change
_buildManifest.js gzip 459 B 459 B
Overall change 459 B 459 B
Rendered Page Sizes
vercel/next.js canary ijjk/next.js fix/invalid-project-dir Change
index.html gzip 533 B 533 B
link.html gzip 547 B 547 B
withRouter.html gzip 527 B 527 B
Overall change 1.61 kB 1.61 kB
Commit: d57aea7

@ijjk ijjk merged commit d118d02 into vercel:canary Feb 25, 2022
@ijjk ijjk deleted the fix/invalid-project-dir branch February 25, 2022 22:08
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants