-
-
Notifications
You must be signed in to change notification settings - Fork 332
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
assume onPort if -- node is set #530
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can just remove --onPort
.
Remember to adjust the docs.
Thanks for your review @mcollina . Also, if we remove onPort flag, I think the check should not striclty be restricted to |
Ah, that's true. Then, this is good. Can you just update the docs? |
Sure, updating. |
@mcollina Does it look okay to you? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
@mcollina checks on node v14 on mac and node v20 on windows are failing. Can see other merges with these fails too. Any known issues ? |
Drop node 14 and v16 support, I'll bump windows is likely flaky. |
Should I add v22 ? |
yes please |
Done but windows still not happy. I think we need another issue to address that. And if this looks good, can we merge it? |
I'll look into the windows tests asap. |
windows tests are fixed, can you rebase? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Adds support for #180
@mcollina Please review when you have some time.