[Feature]: support more command-line flags

[hardfist]

What problem does this feature solve?

Rspack currently missing some cli flags which cause some migration pain for users, see https://birtles.blog/2024/08/14/lessons-learned-switching-to-rspack/#command-line-flags

Rspack CLI includes a built-in dev server but unfortunately, the command-line flags differ from webpack-dev-server in a few places, notably missing options like --port and --hot/--no-hot.
To handle such cases I ended up using various --env values and checking them in rspack.config.js’s configuration function. This seems like a potentially unnecessary point of friction that could be eased in a future release.

we can align more flags to make migration easier

What does the proposed API of configuration look like?

seems no need to support all flags(some flags are rarely used and hard to understand), but we can support some common flags like

--port
--hot | --no-hot
--host

[shulaoda]

Can you answer my question? I see these two variables below, but it doesn't seem to have been actually used?

rspack/packages/rspack-cli/src/commands/serve.ts

Lines 46 to 47 in fd631fa

	const usedPorts: number[] = [];
	const servers: RspackDevServerType[] = [];

[hardfist]

Can you answer my question? I see these two variables below, but it doesn't seem to have been actually used?

rspack/packages/rspack-cli/src/commands/serve.ts

Lines 46 to 47 in fd631fa

	const usedPorts: number[] = [];
	const servers: RspackDevServerType[] = [];

it's used here, if multi compiler specify same port, it will throw error

[shulaoda]

it's used here, if multi compiler specify same port, it will throw error

rspack/packages/rspack-cli/src/commands/serve.ts

Lines 101 to 107 in fd631fa

	if (usedPorts.find(port => portNumber === port)) {
	throw new Error(
	"Unique ports must be specified for each devServer option in your rspack configuration. Alternatively, run only 1 devServer config using the --config-name flag to specify your desired config."
	);
	}
	usedPorts.push(portNumber);

But it doesn't seem to be used anywhere else except here. usedPorts seems to be absolutely empty.

[hardfist]

it's used here, if multi compiler specify same port, it will throw error

rspack/packages/rspack-cli/src/commands/serve.ts

Lines 101 to 107 in fd631fa

	if (usedPorts.find(port => portNumber === port)) {
	throw new Error(
	"Unique ports must be specified for each devServer option in your rspack configuration. Alternatively, run only 1 devServer config using the --config-name flag to specify your desired config."
	);
	}
	usedPorts.push(portNumber);

But it doesn't seem to be used anywhere else except here. usedPorts seems to be absolutely empty.

why，the push will update usedports

[shulaoda]

why the push will update usedports

This is where I am confused, this code seems meaningless.

[hardfist]

if you have two compiler and both use same port，during loop the usedports is updated so it can be used to detect conflict in next iteration