Getting Started with YAML yarn install --force --frozen-lockfile ERROR

Questions
1

I’m trying to set everything up and run the app by following the instructions listed here: https://docs.daml.com/getting-started/index.html
I have had no issues until I cd into the ui folder and run the yarn install --force --frozen-lockfile command. The errors I’m getting are as follows:

error Couldn't find package "@daml/types@1.5.0" required by "@daml.js/create-daml-app@file:../daml.js/create-daml-app-0.1.0" on the "npm" registry.
Error: Couldn't find package "@daml/ledger@1.5.0" required by "@daml.js/create-daml-app@file:../daml.js/create-daml-app-0.1.0" on the "npm" registry.
Error: Couldn't find package "@mojotech/json-type-validation@^3.1.0" required by "@daml.js/create-daml-app@file:../daml.js/create-daml-app-0.1.0" on the "npm" registry.
Error: Couldn't find package "@daml/ledger@1.5.0" required by "@daml.js/d14e08374fc7197d6a0de468c968ae8ba3aadbf9315476fd39071831f5923662@file:../daml.js/d14e08374fc7197d6a0de468c968ae8ba3aadbf9315476fd39071831f5923662" on the "npm" registry.
Error: Couldn't find package "@mojotech/json-type-validation@^3.1.0" required by "@daml.js/d14e08374fc7197d6a0de468c968ae8ba3aadbf9315476fd39071831f5923662@file:../daml.js/d14e08374fc7197d6a0de468c968ae8ba3aadbf9315476fd39071831f5923662" on the "npm" registry.
Error: Couldn't find package "@daml/types@1.5.0" required by "@daml.js/d14e08374fc7197d6a0de468c968ae8ba3aadbf9315476fd39071831f5923662@file:../daml.js/d14e08374fc7197d6a0de468c968ae8ba3aadbf9315476fd39071831f5923662" on the "npm" registry.

I have the following versions of prerequisites installed:
Node: v14.13.0
Npm: v6.14.8
Yarn: v1.22.5

It seems like none of the packages are being found and I don’t know why. I would greatly appreciate any help on this issue. Thank you!

2 Likes
2

Hi @psyak10,

This looks like a network issue between your computer and NPM, especially since some of the missing packages have nothing to do with DAML (mojotech/json-type-validation). I’m not sure how best to try and debug this, except for “can you try now?”, hoping the issue was transient.

Are you perhaps behind a corporate proxy? Can you access the NPM website?

2 Likes