mirror of
https://github.com/terribleplan/next.js.git
synced 2024-01-19 02:48:18 +00:00
b91a960182
As I detailed in [this thread on Spectrum](https://spectrum.chat/?t=3df7b1fb-7331-4ca4-af35-d9a8b1cacb2c), the dev experience would be a lot nicer if the server started listening as soon as possible, before the slow initialization steps. That way, instead of manually polling the dev URL until the server's up (this can take a long time!), I can open it right away and the responses will be delivered when the dev server is done initializing. This makes a few changes to the dev server: * Move `HotReloader` creation to `prepare`. Ideally, more things (from the non-dev `Server`) would be moved to a later point as well, because creating `next({ ... })` is quite slow. * In `run`, wait for a promise to resolve before doing anything. This promise automatically gets resolved whenever `prepare` finishes successfully. And the `next dev` and `next start` scripts: * Since we want to log that the server is ready/listening before the intensive build process kicks off, we return the app instance from `startServer` and the scripts call `app.prepare()`. This should all be backwards compatible, including with all existing custom server recommendations that essentially say `app.prepare().then(listen)`. But now, we could make an even better recommendation: start listening right away, then call `app.prepare()` in the `listen` callback. Users would be free to make that change and get better DX. Try it and I doubt you'll want to go back to the old way. :)
82 lines
2.4 KiB
JavaScript
Executable file
82 lines
2.4 KiB
JavaScript
Executable file
#!/usr/bin/env node
|
|
import { resolve, join } from 'path'
|
|
import arg from 'arg'
|
|
import { existsSync } from 'fs'
|
|
import startServer from '../server/lib/start-server'
|
|
import { printAndExit } from '../server/lib/utils'
|
|
|
|
const args = arg({
|
|
// Types
|
|
'--help': Boolean,
|
|
'--port': Number,
|
|
'--hostname': String,
|
|
|
|
// Aliases
|
|
'-h': '--help',
|
|
'-p': '--port',
|
|
'-H': '--hostname'
|
|
})
|
|
|
|
if (args['--help']) {
|
|
console.log(`
|
|
Description
|
|
Starts the application in development mode (hot-code reloading, error
|
|
reporting, etc)
|
|
|
|
Usage
|
|
$ next dev <dir> -p <port number>
|
|
|
|
<dir> represents where the compiled folder should go.
|
|
If no directory is provided, the folder will be created in the current directory.
|
|
You can set a custom folder in config https://github.com/zeit/next.js#custom-configuration.
|
|
|
|
Options
|
|
--port, -p A port number on which to start the application
|
|
--hostname, -H Hostname on which to start the application
|
|
--help, -h Displays this message
|
|
`)
|
|
process.exit(0)
|
|
}
|
|
|
|
const dir = resolve(args._[0] || '.')
|
|
|
|
// Check if pages dir exists and warn if not
|
|
if (!existsSync(dir)) {
|
|
printAndExit(`> No such directory exists as the project root: ${dir}`)
|
|
}
|
|
|
|
if (!existsSync(join(dir, 'pages'))) {
|
|
if (existsSync(join(dir, '..', 'pages'))) {
|
|
printAndExit('> No `pages` directory found. Did you mean to run `next` in the parent (`../`) directory?')
|
|
}
|
|
|
|
printAndExit('> Couldn\'t find a `pages` directory. Please create one under the project root')
|
|
}
|
|
|
|
const port = args['--port'] || 3000
|
|
startServer({dir, dev: true}, port, args['--hostname'])
|
|
.then(async (app) => {
|
|
console.log(`> Ready on http://${args['--hostname'] || 'localhost'}:${port}`)
|
|
await app.prepare()
|
|
})
|
|
.catch((err) => {
|
|
if (err.code === 'EADDRINUSE') {
|
|
let errorMessage = `Port ${port} is already in use.`
|
|
const pkgAppPath = require('find-up').sync('package.json', {
|
|
cwd: dir
|
|
})
|
|
const appPackage = require(pkgAppPath)
|
|
if (appPackage.scripts) {
|
|
const nextScript = Object.entries(appPackage.scripts).find(scriptLine => scriptLine[1] === 'next')
|
|
if (nextScript) {
|
|
errorMessage += `\nUse \`npm run ${nextScript[0]} -- -p <some other port>\`.`
|
|
}
|
|
}
|
|
|
|
console.error(errorMessage)
|
|
} else {
|
|
console.error(err)
|
|
}
|
|
process.nextTick(() => process.exit(1))
|
|
})
|