ValidationError: 'port' is required. (But I have one. 🤷‍♂️)

[erikwoods]

Hello! Everything was working fine until recently, when a few updates to Netlify CLI seem to have introduced a new issue for me.

When I run ntl dev, I receive this message:

  ± |master → origin U:2 ✗| → ntl dev
  ◈ Netlify Dev ◈

  ◈ Injected build setting env var:  [ALL_MY_SHIT]
  ◈ Starting Netlify Dev with undefined

  ◈ Lambda server is listening on 34567
  ValidationError: 'port' is required.
      at validateParameters (~/.npm-global/lib/node_modules/netlify-cli/node_modules/wait-port/lib/validate-parameters.js:13:20)
      at Promise (~/.npm-global/lib/node_modules/netlify-cli/node_modules/wait-port/lib/wait-port.js:183:9)
      at new Promise (<anonymous>)
      at waitPort (~/.npm-global/lib/node_modules/netlify-cli/node_modules/wait-port/lib/wait-port.js:173:10)
      at startProxy (~/.npm-global/lib/node_modules/netlify-cli/src/commands/dev/index.js:126:9)
      at DevCommand.run (~/.npm-global/lib/node_modules/netlify-cli/src/commands/dev/index.js:406:31)

And here is my .toml file, which hasn’t changed since:

[build]
  command='npm run init; gulp all'
  functions='lambda'
  publish='build'

[context.production]
  command='npm run init; gulp all -p'

[dev]
  command='gulp dev -dn'
  port=3000
  publish='build'

[perry]

hi there, did you see this thread already?

Netlify Dev Port command not working?

I had a netlify dev server running on a site in one tab and fired up another to test something. I noticed it used the same port as the first site, and on checking the docs saw that I could specify a port. So I then tried: netlify dev -p 4001 and the -p was ignored, as far as I could see. Should that have worked?

Would you give it a try without setting the port and see what happens?

[erikwoods]

@perry unfortunately I get the same exact results when I leave the port out of my .toml

[futuregerald]

Hi @erikwoods, Thanks for writing in. I recommend opening an issue in the repo for the Netlify CLI. You can do this from Issues · netlify/cli · GitHub . You should be able to get help directly from our devs right there. Thanks.

[erikwoods]

@futuregerald I’ve been meaning to do what you recommended in your last comment, but there have been a lot of releases since then (I was using 2.15.0), and I tried out the latest (2.20.2) and it’s working fine.

Edit: false alarm. I didn’t test it properly. I’ll log an issue for this.

Thanks again.