The `globby` dependency is not being installed using the documented installation command about themis-contract HOT 5 CLOSED

Added an instruction to install deps locally first prior to installing in the README.

from themis-contract.

I don't think having the user double install the package is a proper fix. It looks like the problem is a packaging configuration issue, according to the discussion here: oclif/oclif#132

I'm fine with leaving the hack of double installing for now, if the plan is to ditch the prototype code soon. But imo we should either leave this issue open to track the problem (as i suggested in #5) or add a TODO on the readme, noting the borken behavior (or, my preference, both).

from themis-contract.

I spent a couple hours trying to get this fixed, but I haven't made any progress, except to say that it seems to be an issue with the way oclif is packaged. In particular, it seems that our intended installation method doesn't work to install from source. I suspect some magic is happening via npm publish (the recommended release method: https://oclif.io/docs/releasing).

I opened an issue in oclif/example-multi-ts#34 reproducing this.

However, revisiting the docs on releasing, I see that releases that are not via npm all use some variation of oclif-dev pack. I suspect that is what we should be doing in order to release this properly (even if we're not putting out managed packages).

from themis-contract.

In the meantime we can work around this bug by using the Docker image.

from themis-contract.

Irrelevant after rewrite in go.

from themis-contract.