CLI

[vicb]

I think we should do some cleanup on how parse CLI command/flags.

Opening this issue to list some ideas.

See for example #762

Some thoughts:

1. We should document all the commands (build, preview, ...) and what arguments they take

2. getArgs()

As of today we call getArgs() first which compute the args for all the commands.

Maybe what we should do instead is to get the command first by looking at the first argument and let each command parse their arguments.

For ex. we pass the same parseArgs config for all commands when most of the config does only apply to build.

3. compileOpenNextConfig

compileOpenNextConfig is called whatever the command is at the beginning of runCommand.
I think we could just call it for the build command and retrieve the built version for other commands.

(same goes for createOpenNextConfigIfNotExistent)

We should also create a commands/build.ts as we have for all other commands.

[james-elicx]

I was never quite happy with how I implemented multiple commands. Will be happy to revisit it to have better parsing of arguments relevant to each command. Can write some docs for them at the same time.

[vicb]

I was never quite happy with how I implemented multiple commands. Will be happy to revisit it to have better parsing of arguments relevant to each command. Can write some docs for them at the same time.

That would be nice.

For the doc I was thinking that opennextjs-cloudflare command --help (exact syntax TBD) could output some help. That could serve as doc for users and devs?