50bd10f5f8
* Use Better Telemetry Directory So, as it turns out, storing in `node_modules` is a bad idea. Both npm and Yarn will remove additional files when you run `npm install` or `yarn install`. Instead, we'll store this inside of Next.js' `distDir`. This should also be cached by users, if it's not, it probably won't be any worse as compared to `node_modules`. * Fix directory name * Fix build setup * Record when export session is started * Move more into branch
54 lines
1.3 KiB
JavaScript
Executable file
54 lines
1.3 KiB
JavaScript
Executable file
#!/usr/bin/env node
|
|
import { existsSync } from 'fs'
|
|
import arg from 'next/dist/compiled/arg/index.js'
|
|
import { resolve } from 'path'
|
|
|
|
import { cliCommand } from '../bin/next'
|
|
import build from '../build'
|
|
import { printAndExit } from '../server/lib/utils'
|
|
|
|
const nextBuild: cliCommand = argv => {
|
|
const args = arg(
|
|
{
|
|
// Types
|
|
'--help': Boolean,
|
|
// Aliases
|
|
'-h': '--help',
|
|
},
|
|
{ argv }
|
|
)
|
|
|
|
if (args['--help']) {
|
|
printAndExit(
|
|
`
|
|
Description
|
|
Compiles the application for production deployment
|
|
|
|
Usage
|
|
$ next build <dir>
|
|
|
|
<dir> represents where the compiled dist folder should go.
|
|
If no directory is provided, the dist folder will be created in the current directory.
|
|
You can set a custom folder in config https://github.com/zeit/next.js#custom-configuration, otherwise it will be created inside '.next'
|
|
`,
|
|
0
|
|
)
|
|
}
|
|
|
|
const dir = resolve(args._[0] || '.')
|
|
|
|
// Check if the provided directory exists
|
|
if (!existsSync(dir)) {
|
|
printAndExit(`> No such directory exists as the project root: ${dir}`)
|
|
}
|
|
|
|
build(dir)
|
|
.then(() => process.exit(0))
|
|
.catch(err => {
|
|
// tslint:disable-next-line
|
|
console.error('> Build error occurred')
|
|
printAndExit(err)
|
|
})
|
|
}
|
|
|
|
export { nextBuild }
|