CardanoSolutions / ogmios

❇️ A WebSocket JSON/RPC bridge for Cardano
https://ogmios.dev
Mozilla Public License 2.0
304 stars 90 forks source link

Unable to install client package through Yarn #136

Closed austinborn closed 2 years ago

austinborn commented 2 years ago

Using yarn v3.0.0:

$ yarn -v
3.0.0

What operating system are you using, and which version?

macOS Monterey 12.0.1

Describe what the problem is?

Cannot install latest ogmios client through yarn:

$ yarn add @cardano-ogmios/client
➤ YN0000: ┌ Resolution step
➤ YN0001: │ Error: json-bigint@github:CardanoSolutions/json-bigint#d277387d: Couldn't resolve "d277387d" as either a commit, a tag, or a head - if a commit, use the 40-characters commit hash
    at a (/Users/austinborn/chainlink/external-adapters-js/.yarn/releases/yarn-3.0.0.cjs:452:11555)
    at $v (/Users/austinborn/chainlink/external-adapters-js/.yarn/releases/yarn-3.0.0.cjs:452:11887)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at async rF.getCandidates (/Users/austinborn/chainlink/external-adapters-js/.yarn/releases/yarn-3.0.0.cjs:452:14098)
    at async Xc.getCandidates (/Users/austinborn/chainlink/external-adapters-js/.yarn/releases/yarn-3.0.0.cjs:294:4907)
    at async Xc.getCandidates (/Users/austinborn/chainlink/external-adapters-js/.yarn/releases/yarn-3.0.0.cjs:294:4907)
    at async /Users/austinborn/chainlink/external-adapters-js/.yarn/releases/yarn-3.0.0.cjs:303:7635
    at async Gl (/Users/austinborn/chainlink/external-adapters-js/.yarn/releases/yarn-3.0.0.cjs:242:3997)
    at async y (/Users/austinborn/chainlink/external-adapters-js/.yarn/releases/yarn-3.0.0.cjs:303:7617)
    at async Promise.all (index 5)
➤ YN0000: └ Completed in 1s 329ms
➤ YN0000: Failed with errors in 1s 338ms

What should be the expected behavior?

The yarn package version should likely specify the full commit hash to successfully install. So in the package.json:


CardanoSolutions/json-bigint#d277387d -> CardanoSolutions/json-bigint#d277387d7750ff4e698677d0aa0db97ebb60c581
KtorZ commented 2 years ago

That's unfortunate indeed. Note that we have created a proper release tag for this package recently, and changed the client's dependencies to use the tag instead so this problem should vanish in the next release.

austinborn commented 2 years ago

Awesome, thank you for the info!