-
Notifications
You must be signed in to change notification settings - Fork 365
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
waiting for framework port 3000 #4942
Comments
Are you using node 18? If so try to use node 16 for now, this should fix it. We are working on this, see #4845. |
Hi @danez , I'm using node |
Oh @lucasfontesgaspareto I found out that the issue is when you use |
These issues should be fixed now as of version 12.0.2. If it still appears please reopen with an example. |
@danez still get this with:
only fix is: netlify dev --targetPort 5173 |
For those building Astro.js sites, this fixed it for me.
Run command:
|
If anyone else is running into this issue with Astro, adding this to
|
or just update the CLI. |
I did update the CLI but was still experiencing the issue with astro websites that use svelte. |
I am still facing this issue.. any update? |
i managed to fix it by removing the
in my netlify.toml file |
I am still facing this issue and no solution working for me...any updates on this? I'm just using also the latest CLI version |
I'm getting this issue again with Astro 3. As it's with Astro 3 + Node 18, I have created a new issue here: |
Any update on this? I am on the latest Node LTS v21.4.0, and facing this issue. my netlify.toml features [dev] section as following: [dev] |
also facing this issue with expo apps |
are you hosting your expo app on netlify? 🤔 |
Describe the bug
I can't run netlify dev because it says it is waiting for framework port 3000.
Waiting for framework port 3000. This can be configured using the 'targetPort' property in the netlify.toml◈ Command failed with exit code 1: npm run start. Shutting down Netlify Dev server
Steps to reproduce
Configuration
No response
Environment
netlify-cli 10.17.4
The text was updated successfully, but these errors were encountered: