Skip to content

What could possibly trigger "This package doesn't seem to be present in your lockfile" error? #6200

Closed Answered by Kolobamanacas
Kolobamanacas asked this question in Q&A
Discussion options

You must be logged in to vote

@clemyan thanks for pointing this out. To sum up the steps it took to make everything work:

  1. Apart from copying yarn.lock it was also necessary to copy .yarnrc.yml file and .yarn folder as it seems now Yarn checks for packages integrity even when I assume that all packages are already downloaded, checked, built and stored in node_modules.
  2. As Yarn checks for packages integrity, setting CI_JOB_TOKEN in application container also become mandatory, cause without token it has no access to private npm registries.
  3. Yarn 2+ or at least Yarn 4 doesn't support pre- and post- scripts, which I omitted in the original post as I thought of them as unrelated to a question. But in fact we heavily rely on …

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by Kolobamanacas
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants