Open optcond opened 1 year ago
Does adding "@types/long": "^4.0.1",
help? Long version 5 changed to ES modules, which might create an incompatibility.
Thanks for the response! I had 2 yarn repos (clean one and my monorepo) and the clean one compiled after I put @types/long version like you've indicated. The monorepo one was still failing despite @types/long with protobuf issue. I am not sure what I did, but it started building even without specifically stating any dependencies in the package.json: I switched nvm to node v18, restarted vscode, removed all dependencies except @cosmjs and it built as is without any errors.
Thanks for your advice and your time.
I am getting the following errors with this setup: yarn@3.3.2 node v16 and v18 typescript 4.9.3 and 4.9.4 ubuntu
Trying to build my own script with imported @cosmjs/proto-signing @cosmjs/stargate (installed via yarn add)
@types/long doesn't resolve the error for long; noImplicitAny silences the error, but protobufjs error still remains saying module not found. Adding with yarn doesn't fix the problem
Any advice appreciated. Thanks.