What's not working?

I consulted the docs here: https://redwoodjs.com/docs/cli-commands#dev

They mention using the CLI flag --fwd=" ... " to send along flags that control the underlying dev server (webpack I guess?).

In particular, I wanted to:

1. stop it from opening a new web browser
2. bind a different port
3. bind to ALL hosts so I can hit the dev server from my phone (to do remote debugging)

I issued this command:

yarn rw dev web --fwd="--no-open --port=9234 --allowed-hosts=all"

Also tried this variant:

yarn rw dev web --fwd="--no-open --port 9234 --allowed-hosts all"

(spaces instead of =)

None of the 3 flags seem to affect anything, as the browser still opens, the port is still 8910, and I still can't hit the dev-server instance from my phone using my laptop's local LAN IP.

SIDE NOTE: the docs linked above still say to use --open=false for stopping the browser from opening. I tried that, first. But then I found another issue saying that the underlying webpack arguments had changed to --no-open. Docs should be updated there.

To be clear, though, the webpack docs do still say that --allowed-hosts all should be working, but it doesn't seem to be, as I don't think any of those params are getting forwarded (as I asserted above).

How do we reproduce the bug?

Try the above command(s) as I mentioned.

What's your environment? (If it applies)

System:
    OS: Linux 5.15 Debian GNU/Linux 11 (bullseye) 11 (bullseye)
    Shell: 5.1.4 - /bin/bash
  Binaries:
    Node: 19.9.0 - /tmp/xfs-c4e108ca/node
    Yarn: 3.6.1 - /tmp/xfs-c4e108ca/yarn
  npmPackages:
    @redwoodjs/core: 6.2.1 => 6.2.1

Are you interested in working on this?

• I'm interested in working on this