Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

graphweaver start frontend --port 8600 does actually not change the port. #1550

Open
gewubuntu opened this issue Jan 24, 2025 · 0 comments
Open

Comments

@gewubuntu
Copy link

gewubuntu commented Jan 24, 2025

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

[email protected] start
graphweaver start frontend 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:

  1. block port 9000
  2. run npm start frontend --port 8601
  3. See the problem that its still trying to run at 9001, which collides with apollo/backend

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

Image

Desktop (please complete the following information):

  • OS and version: Windows 10.0.19045 Build 19045

Additional context
Add any other context about the problem here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant