jp
error handling with lazy
thanks for looking into it! i did pretty much the same workaround, but provided a fallback node with an error message just to see something in the dom. that might already be enough for now to show a reload button or something of the sort if it did happen on the live site
10 replies
error handling with lazy
that makes sense, but i thought because of the lazy import, it's effectively moved to runtime either way. an app might change routes and lazy load a component that fails to load for whatever reason. if that's not considered recoverable, then it makes sense not to bother handling it. for the dev server case, it's nice to be able to catch everything with no unhandled promise failures. i ended up making a custom lazy that takes a fallback to show it when imports fail, so at least the dev server survives small errors
10 replies