Thanks for your suggestion. Unfortunately, I’ve had issues related to developing my colonyJS project that arose from misalignment with
ethers as well as the
node version itself in the past, which Ryan helped me resolve. So for the benefit of us masses out here I think it is worth explicitly mentioning known working versions of these as well so that we can absolutely rule out dependency issues when upgrading colony.
As a side note, I’ve had a frustrating past couple of weeks getting all of the following upgraded and working together. They had been working, but with various breaking API changes happening on the bleeding edge, waiting a year to upgrade is not a good idea either. It’s damned if you do and damned if you don’t. Various dependencies are now clashing resulting in having to spend 80% of my time not actually developing, but resolving dependency problems with unclear failure errors.
- Web3 (which must be held back for Truffle at v1 beta.37)
- Zos, zos-lib and oppenzeppelin-eth because I am writing a supplemental contract that is using those libraries
And Colony, including a change in how roles are handled through colonyJS, which has multiple ripple effects through my project because my custom contract checks to see if you have the right Colony role before allowing certain functions.
I would like to get back to “real” development!