[petebacondarwin]

cf dev --port 8787 --host 127.0.0.1 currently fails when a framework development command is detected, including projects created by cf init. Forward server arguments through the existing project-command runner, preserve argument boundaries and arguments after --, and update help and generated metadata. Frameworks retain their existing --mode support checks.

Validation:

• pnpm check passed.
• 128 related tests passed; 6 Windows-only tests skipped on macOS. Coverage includes Vite, Astro, vinext, the fallback server, and paths containing spaces.
• Includes a patch changeset.

Fixes #223.

[pkg-pr-new]

npm i https://pkg.pr.new/cf@286

commit: 1249285

[ask-bonk]

LGTM

github run

[github-actions]

cf --help startup

	mean	stddev	min	max
PR	214.8 ms	6.7 ms	206.0 ms	226.8 ms
base	214.1 ms	6.1 ms	202.2 ms	224.0 ms

Δ (PR vs base): — +0.7 ms (+0.3%)

Measured with hyperfine on ubuntu-latest (3 warmup runs, 20 timed runs). CI numbers carry ±a few ms of runner jitter; treat small deltas as noise.

[ask-bonk]

Autoconfig selects package scripts as commands such as npm run dev when a project defines one. Appending the server flags directly produces npm run dev --port 8787, but npm's documented invocation is npm run-script <command> [-- <args>]; consequently the script never receives --port or --host. The new tests only exercise direct npx vite/npx astro commands because their fixtures have no scripts, so this common framework path remains broken. Insert the script-runner separator before forwarded arguments.

Suggested change

	args: [...modeArgs, ...implArgs],
	args: [
	...(details.devCommand.match(/^(?:npm|pnpm|yarn|bun) run\b/)
	? ["--"]
	: []),
	...modeArgs,
	...implArgs,
	],

[ask-bonk]

Review: 1 findings.

🤖 I've done a thorough review of your PR.
Forwards cf dev arguments to detected framework servers and updates tests/metadata.

1. Blocking: Posted one inline suggestion for script-runner argument forwarding.

github run