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

Local dev server info disappears #664

Closed
abettermap opened this issue Dec 23, 2019 · 2 comments
Closed

Local dev server info disappears #664

abettermap opened this issue Dec 23, 2019 · 2 comments

Comments

@abettermap
Copy link

- 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:

image

- 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:

image

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

  • OSX Mojave 10.14.6
  • iTerm2 3.0.4
  • zsh 5.3 (x86_64-apple-darwin18.0)
  • gatsby 2.18.16 (local)

- Global node modules

  • gatsby-cli@2.8.21
  • netlify-cli@2.25.0
  • npm@6.13.4
  • yarn@1.21.1

- npm scripts block in package.json

"scripts": {
  "build": "gatsby build && (cd lambda && npm install)",
  "develop": "gatsby develop -H 0.0.0.0",
  "format": "prettier --write \"**/*.{js,jsx,json,md}\"",
  "serve": "gatsby serve",
  "test": "echo \"Write tests! -> https://gatsby.dev/unit-testing \""
}

- 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):

image

...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!

@abettermap
Copy link
Author

If it helps I noticed that the server info also appears consistently if I do not specify a functions folder in netlify.toml:

[dev]
  port = 8888
  command = "gatsby develop"

...shows what I'd expect:

image

But as soon as I try to get my functions back:

[dev]
  port = 8888
  command = "gatsby develop"
  functions = "lambda"

...I get the infinite dots and the netlify server never starts (Gatsby server still fine):

image

@abettermap
Copy link
Author

Closing this, found a dupe: #659

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

No branches or pull requests

1 participant