Closed KerenLerner closed 1 year ago
I think this is fine to fix the issue we're having, but I'd like to dig more into why / where this issue is happening.
Thanks for taking a look James. It was happening whenever we try to read
a file that doesn't exist (say, a typo in the path to an SVG).
Handle
read
exceptions more gracefully. Without this change, when a template tries toread
a file that doesn't exist (e.g. an svg file), the entire page will fail to render, instead displaying this error message in the browser:With this change, the page simply loads without the asset that doesn't exist and logs an error to the console.