You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
graphweaver start frontend --port 8600 does actually not change the port.
since our company has something else running on 9000 i wanted to change the port via the --port option. this doesnt work. it still wants to run on 9000 and switches to 9001.
(node:15380) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
(Use node --trace-deprecation ... to show where the warning was created)
Port 9000 is in use, trying another one...
Describe the bug
graphweaver start frontend --port 8600 does actually not change the port.
since our company has something else running on 9000 i wanted to change the port via the --port option. this doesnt work. it still wants to run on 9000 and switches to 9001.
this is my console output:
`
npm start frontend --port 8601
(node:15380) [DEP0040] DeprecationWarning: The
punycode
module is deprecated. Please use a userland alternative instead.(Use
node --trace-deprecation ...
to show where the warning was created)Port 9000 is in use, trying another one...
The Graphweaver server has started. 😀😀
The GraphQL API is available at http://localhost:9001/
Admin UI is available at http://localhost:9001/ 🚀
If you are new here, start with Admin UI.
`
To Reproduce
Steps to reproduce the behavior:
npm start frontend --port 8601
Expected behavior
We would expect that the actual port is taken and frontend should start there.
Actual behavior
port still opting out to 9001 => its not taking the input of the --port option
Screenshots or Screencasts
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: