You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When importing a module that contains the following code, which throws a SyntaxError such as this.
importNoDefaultfrom'./invalid-module.js'
importShim would throw the error containing the blob url The requested module 'blob:https://xyzcom/df954a0e-1f96-4f52-8521-c2a32ea59bde' does not provide an export named 'default'.
Is there any way to retrieve the original path to the module './invalid-module' in the thrown error rather than the blob url?
The text was updated successfully, but these errors were encountered:
We could implement an ES Module Shims specific exports validation which could allow us to catch this earlier in the pipeline and throw a nicer error. It would have some overhead, but sounds like it would be the right approach here. While inspecting the blob URL does have a source URL, but browser debugging is not great here I know.
I don't have the bandwidth to work on a named exports validation and error phase, but will mark this as an enhancement for the project.
When importing a module that contains the following code, which throws a SyntaxError such as this.
importShim would throw the error containing the blob url
The requested module 'blob:https://xyzcom/df954a0e-1f96-4f52-8521-c2a32ea59bde' does not provide an export named 'default'
.Is there any way to retrieve the original path to the module './invalid-module' in the thrown error rather than the blob url?
The text was updated successfully, but these errors were encountered: