Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot read property 'UriResolver' of undefined #85

Closed
haraldini opened this issue Feb 25, 2019 · 9 comments
Closed

Cannot read property 'UriResolver' of undefined #85

haraldini opened this issue Feb 25, 2019 · 9 comments

Comments

@haraldini
Copy link

haraldini commented Feb 25, 2019

Just did a simple out of the box yarn install on an existing project. npx waffle just throws this error on a very basic test: Cannot read property 'UriResolver' of undefined

@snario
Copy link
Contributor

snario commented Feb 25, 2019

Also getting this @marekkirejczyk

@marekkirejczyk
Copy link
Contributor

Looking into it

@snario
Copy link
Contributor

snario commented Feb 26, 2019

@marekkirejczyk
Copy link
Contributor

I have hard times reproduction. I already looked into @snario repo, I think it might be related to truffle-flattener that requires a different version of @resolver-engine/imports-fs.

@haraldini Can you link repo, or yarn.lock file, so I can look into it?

I'll dig deeper tomorrow.

@haraldini
Copy link
Author

I moved on and didn't keep a snapshop I'm afraid. I was using ZepKit as a starting point if that that might help somewhat: truffle unbox zeppelinos/zepkit

@Amxx
Copy link

Amxx commented Jun 29, 2019

Also getting the same error is some cases:
$ waffle waffle.js
→ ok
$ yarn build ("build": "waffle waffle.json")
→ not ok

Happens on kitsune-contract and universalloginsdk

@Amxx
Copy link

Amxx commented Jun 29, 2019

@snario 's fix works for me

@cehali
Copy link
Contributor

cehali commented Aug 20, 2019

Hi,
I recreated this error and it turns out that it is a problem with zos-lib. Zos-lib requires truffle-flattener which requires an older version of @resolver-engine/core. Openzeppelin had the same problem: OpenZeppelin/openzeppelin-sdk#1059. Funny thing is that using npm instead of yarn install the newest version of @resolver-engine/core. So there are two solutions, either you can use npm instead of yarn (I believe it is not desired) or you can add "@resolver-engine/core": "^0.3.3" to your dependency to force yarn to install the newest and compatible version. I added this dependency to Amxx code and I could build and run tests without problem mentioned in this issue.

@marekkirejczyk
Copy link
Contributor

Closing, please reopen if it is still an issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants