Have you read Fractal's Code of Conduct? By filing an Issue, you are expected to comply with it, including treating everyone with respect
Do you want to ask a question? Are you looking for support? The Fractal Slack channel is the best place for getting support: https://fractalize.slack.com
404 errors now generate an error for express to process, which bubbles as an event to the vorpal interface in web.start.js. with the latest change of 1.2.0 this causes the fractal dev server (fractal start) to stop after a 404 error.
Stopping after a 404 error is limiting the use cases for fractal, such as situations/states of components in the library that work for an unavailable backend (such as an image not available from a CMS).
I am creating a PR which will reference this issue.
.hbs) with an image tag with a domain relative src that generates the 404fractal startExpected behavior: dev server keeps running
Actual behavior: dev server stops
Reproduces how often: 100%
Any additional information, configuration or data that might be necessary to reproduce the issue.
Please refer to my PR for a potential fix, and description of why this seems to occur: #515
While I have not investigated myself, I have run in to the same issue. #513 and #515, seemingly independent of each other, suggest the same fix鈥攚hich is a good sign.
It seemed the easiest fix to me looking at the project history, only thing is that express documentation suggests a different approach, by fixing it in the server code, see section on how to respond to 404 here: https://expressjs.com/en/starter/faq.html
Which makes sense from my point of view, but fixing the issue in this way requires more knowledge on fractal than I have at the moment, hehe :)
Fixed by #515
Most helpful comment
While I have not investigated myself, I have run in to the same issue. #513 and #515, seemingly independent of each other, suggest the same fix鈥攚hich is a good sign.