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

1. Load the blitz
2. Run npm start. Observe the dev server starts and you can see the Greenwood logo in the header
   
3. Make and save any change to a file (like editing the name field in package.json)
   
4. This will cause a fork
5. Run the npm start command again, now the image in the header is not loading
   

Expected behavior

It would be great if the image continued to load. 😃

Screenshots

Provided in the Steps to reproduce section 👆

Platform

• OS: macOS
• Browser: Chrome
• Version: 96

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!