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

Add flag for disabling port switching #579

Merged
merged 2 commits into from Mar 3, 2021
Merged

Conversation

jespertheend
Copy link
Contributor

@@ -370,6 +370,7 @@ const loadConfig = async (cwd, entry, args) => {
'--no-etag': Boolean,
'--symlinks': Boolean,
'--cors': Boolean,
'--no-port-switching': Boolean,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you add documentation for this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've added it to --help. Would you like to have it added somewhere else as well?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

True, that will probably suffice. Thank you.

@leerob leerob changed the title add option for disabling port switching Add flag for disabling port switching Mar 3, 2021
@leerob leerob merged commit a85bd9d into vercel:master Mar 3, 2021
@JamesHenry
Copy link

JamesHenry commented Jun 2, 2021

@leerob Sorry to be commenting on a merged PR, but it seems a shame to open an issue just for this:

It looks like there hasn't been a release of the library for a year now - please could you cut one so that we can easily make use of this change via NPM?

Thanks!

@JamesHenry
Copy link

JamesHenry commented Jun 2, 2021

Hmm additionally @jespertheend was it your intention that this doesn't exit with code 1?

Having installed it via the git commit and run it, it always seems to hit INFO: Gracefully shutting down. Please wait... and exits with code 0 which is unintuitive I think

My mistake, does seem to be non-zero. Thanks for adding this!

@jespertheend
Copy link
Contributor Author

Ah interesting, I hadn’t even thought about that to be honest. Non-zero seems more intuitive yeah. I was just reusing the shutting down code that was already in place I believe. So it should behave the same as when an error other than EADDRINUSE is thrown.

@leerob
Copy link
Member

leerob commented Jun 8, 2021

This has now been released 👍

@JamesHenry
Copy link

Thanks @leerob, just installed it instead of the commit reference and everything looks good!

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

Successfully merging this pull request may close these issues.

None yet

3 participants