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
Noticed that if I made changes to a blitz, thus causing a fork, and then re-ran the same npm start command, that the image in the header was not loading anymore.
I can make as many changes as I want and keep running npm start and everything is fine, but as soon as I save and get into a fork, the image loading breaks.
Thanks in advance for any help / guidance!
The text was updated successfully, but these errors were encountered:
@thescientist13 thanks for submitting this report! As you determined, this is the same underlying issue as #677 so I will close this report, and we can follow #677 for updates. Cheers!
Describe the bug
Noticed that if I made changes to a blitz, thus causing a fork, and then re-ran the same
npm start
command, that the image in the header was not loading anymore.Link to the blitz that caused the error
https://stackblitz.com/github/ProjectEvergreen/greenwood-getting-started
Steps to reproduce
npm start
. Observe the dev server starts and you can see the Greenwood logo in the headername
field in package.json)npm start
command again, now the image in the header is not loadingExpected behavior
It would be great if the image continued to load. 😃
Screenshots
Provided in the Steps to reproduce section 👆
Platform
Additional context
The image is referenced in a folder called /assets and is served by a simple Koa server from src/components/header/header.js.
Not sure if this is related to #208 ?
I can make as many changes as I want and keep running
npm start
and everything is fine, but as soon as I save and get into a fork, the image loading breaks.Thanks in advance for any help / guidance!
The text was updated successfully, but these errors were encountered: