I introduced an artificial delay into bos-loader to reproduce this consistently. On page load, we quickly get an error when a local only component is not found. A few seconds later, the bos-loader fetch resolves and we end up with the component UI on screen, but the error is not dismissed.
I would expect that having a bos loader URL set would cause block the initial render from web engine until the request to bos-loader has resolved
Not sure if this is the same issue as #386
I introduced an artificial delay into bos-loader to reproduce this consistently. On page load, we quickly get an error when a local only component is not found. A few seconds later, the bos-loader fetch resolves and we end up with the component UI on screen, but the error is not dismissed.
I would expect that having a bos loader URL set would cause block the initial render from web engine until the request to bos-loader has resolved
https://github.com/near/bos-web-engine/assets/24904709/ff08e222-ef7a-4b5d-972d-aa13e9082b39