Closed simonaco closed 3 years ago
Hey @simonaco thank you for reporting this issue. The good news is that we've already fixed it in https://github.com/Azure/static-web-apps-cli/pull/281 (issue https://github.com/Azure/static-web-apps-cli/issues/275). However, we haven't published a release to npm yet. cc @anthonychu.
Just as an FYI, here are the steps I followed (using v 0.7.2 - currently in main branch):
install Gatsby: npm install -g gatsby-cli
gatsby new blog https://github.com/gatsbyjs/gatsby-starter-blog
cd blog
swa start http://localhost:8000 --run "npm start"
(I am not using SWA API)http://localhost:4280
As you can see from my screenshots
Hey @simonaco, We have an upcoming release this week and you should see it in the latest npm package soon! 😄
This is awesome! Thank you @Reshmi-Sriram 👍
Hii @simonaco we've done a new release today and previous changes have been included in this, please check once.
thank you @Reshmi-Sriram @sgollapudi77 . I just tested with a simple Gatsby app and one API endpoint and I'm still seeing issues, please check this screen recording swa-cli doesn't start
sample repo is here https://github.com/simonaco/swa-cli-297
Thank you @manekinekko for debugging with me. It seems like the issue was related to how I was starting the CLI. When using this command, swa start http://localhost:8000/ --api http://localhost:7071 --run "npm start" I need to have the functions server started.
Alternatively I can use this command to instruct the CLI to start the functions dev server: swa start http://localhost:8000/ --api api --run "npm start"
Describe the bug Swa cli fails to start with error message [swa] Could not connect to "http://localhost:8000/". Is the server up and running? after successful start of gatsby dev server
To Reproduce Steps to reproduce the behavior:
Expected behavior Expectation is that swa cli detects that gatsby has started
Screenshots