You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Do you want to request a feature or report a bug?
Bug
- What is the current behavior?
The Server now ready box is only visible briefly then disappears, so I can't see which port the dev environment is being served on:
- If the current behavior is a bug, please provide the steps to reproduce. netlify dev command
- What is the expected behavior?
The Server now ready box should remain visible like this:
The only way I was able to determine the port was to do a screen recording and pause the video while the server info flashed briefly!
- Local Environment Information
Paste the results of netlify status --verbose here:
──────────────────────┐
Current Netlify User │
──────────────────────┘
Name: Jason Lampel
Email: jason@abettermap.com
Teams:
jason-mh-kuwe's team: Collaborator
- Theories/troubleshooting
It looks like Gatsby CLI output and Netlify CLI output might be competing for space. No idea if this is a thing but the info kinda bounces back and forth between the two, and the fact that the server info DOES appear for a sec seems odd.
Also worth noting is that I had some success with netlify dev --live in which I was able to see the expected server info (without a screen recording, ha):
...BUT, that is only the case if I already have netlify dev running. I think what happens is that the output has to pause in order for me to respond to the "Port already in use, do you want to use a different port?" prompt. It allows the live server info to appear and remain visible.
For now my workaround is screen recordings and pausing at the right spot, or run netlify dev twice so the prompt allows the server info to stay up.
Happy to troubleshoot, thanks in advance for any help!
The text was updated successfully, but these errors were encountered:
- Do you want to request a feature or report a bug?
Bug
- What is the current behavior?
The
Server now ready
box is only visible briefly then disappears, so I can't see which port the dev environment is being served on:- If the current behavior is a bug, please provide the steps to reproduce.
netlify dev
command- What is the expected behavior?
The
Server now ready
box should remain visible like this:The only way I was able to determine the port was to do a screen recording and pause the video while the server info flashed briefly!
- Local Environment Information
Paste the results of
netlify status --verbose
here:──────────────────────┐ Current Netlify User │ ──────────────────────┘ Name: Jason Lampel Email: jason@abettermap.com Teams: jason-mh-kuwe's team: Collaborator
- Other env info
- Global node modules
-
npm scripts
block in package.json- Related issues
- Theories/troubleshooting
It looks like Gatsby CLI output and Netlify CLI output might be competing for space. No idea if this is a thing but the info kinda bounces back and forth between the two, and the fact that the server info DOES appear for a sec seems odd.
Also worth noting is that I had some success with
netlify dev --live
in which I was able to see the expected server info (without a screen recording, ha):...BUT, that is only the case if I already have
netlify dev
running. I think what happens is that the output has to pause in order for me to respond to the "Port already in use, do you want to use a different port?" prompt. It allows the live server info to appear and remain visible.For now my workaround is screen recordings and pausing at the right spot, or run
netlify dev
twice so the prompt allows the server info to stay up.Happy to troubleshoot, thanks in advance for any help!
The text was updated successfully, but these errors were encountered: