-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
fix(node): use consistent default port #16491
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
Some frontend generators use port |
If we do that, we would also need to change the default port for the e2e. I see one place that 3333 is hard-coded as the port. I don't think that's safe, given that a backend project could be running off any port, even if we change the default. It also assumes the url will be the same name as the backend project. From my very limited perspective, it would be a better idea to change those frontend generators to accept something like a I think the problems with that generator exist no matter if we change the defaults here. I could change the default port in those frontend generators to also be 3000 to get everything lined up and at least working out of the box. |
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Current Behavior
The Node application generator has two different default ports: 3000 in the
schema.json
and 3333 in the generator itself. This results in a failing e2e test after generation.Expected Behavior
The default port is consistent.