This repository was archived by the owner on Jul 13, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 185
Improve stacktrace for failed dependency loading #397
Comments
Looking at an issue in systemjs/builder, I found that the right way to address that would be here. I think load objects would need to be extended to include their (first?) immediate requester, and their un-normalized requested name (i.e. "requested as") in order to report these errors usefully. I've started (i.e. 15 minutes to fork, clone, write a failing test) work on a PR for this. |
I think this can be done via some reflective lookups in the error handler itself to run a dependency trace just for the error message. |
Thanks @nyarly for your work on this. |
Released in 0.17.4. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Originally posed by @OliverJAsh in systemjs/systemjs#512:
This is what the errors looks like when a dependency fails to load:
Sometimes
dependency
is a nested dependency of a dependency ofrequester
, e.g.requester -> foo -> bar -> dependency
. Is it possible to show the immediate requester (bar
)?The text was updated successfully, but these errors were encountered: