-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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: --host
flag logs when no network IPs are found
#3547
Conversation
🦋 Changeset detectedLatest commit: 93b94dc The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
--host
flag logs when no network IPs are found
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!
if (networkLogging === 'host-to-expose') { | ||
network = `${networkPrefix}${dim('use --host to expose')}`; | ||
} else if (networkLogging === 'visible') { | ||
const ipv4Networks = Object.values(os.networkInterfaces()) |
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.
wow, fancy
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
* feat: add fallback log if no network interfaces found * fix: extra newline on missing network log * chore: changeset
Changes
unable to find network to expose
message when no network IPs are foundTesting
None added, since testing would require stubbing Node's
os
package to return an empty array. I attempted to use Sinon for this, and discovered it can't support ESM 😢 Would love to improve our testing infra for cases like this!Docs
N/A