Time out during "Waiting for framework port" when index results in 404
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 474
- Avg merge
- 23h 30m
- Merged PRs (30d)
- 53
Description
Describe the bug
My Gatsby page doesn't have a page at index, which seems for the CLI to not notice when the framework port becomes available using the dev command. As soon as I add an index.js, the CLI works as intended.
Steps to reproduce
- Create a new Gatsby site
- Remove the index.js file
- Start the Netlify dev server using
netlify dev - See that "Waiting for framework port 8000" message is being shown even when the Gatsby development server is already available at "localhost:8000"
- Add an index.js file and see that the CLI works as intended
Configuration
No response
Environment
System:
OS: Windows 10 10.0.19045
CPU: (8) x64 Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
Memory: 4.19 GB / 31.94 GB
Binaries:
Node: 18.16.0 - C:\Program Files\nodejs\node.EXE
npm: 8.16.0 - C:\Program Files\nodejs\npm.CMD
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with a Gatsby site that has no index.js, then run netlify dev and observe the framework-port detection while the development server returns 404 at localhost:8000. Trace the CLI's framework-port availability check; done means it recognizes the running server despite the index route returning 404, while still working when index.js exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100