-
Notifications
You must be signed in to change notification settings - Fork 201
Error "Cannot read property 'UriResolver' of undefined" in v2.4 #1061
Comments
Hello @hickscorp! Sadly, this issue was introduced after releasing
or
|
Hey @hickscorp, this issue has been fixed in 2.4.1. I'm closing it, but please comment if you stumble upon it again. Thanks for the report! |
@spalladino This issue might be closed now, but a new one surfaced. Should I open a new issue?
|
@hickscorp no need, already reproduced it. Expect a new patch soon! |
@hickscorp actually, I have a hunch that the error may only happen in verbose mode. Could you check removing the |
Unfortunatelly our tooling changed too much (We've been a bit lost between the |
We've updated our dependencies and all of a sudden ZOS starts to fail, even when called without any arguments:
Doing a bit of research showed another project (
cryptopunkers
) with the same error - given who handled the issue, I'm wondering whether a bad dependency made its way into ZOS ;)As I'm not sure what exactly got broken, a hint on what dependencies to force would be great until resolution!
The text was updated successfully, but these errors were encountered: