[Bug]This package doesn't seem to be present in your lockfile; try to make an install to update your resolutions

[LvChengbin]

This package doesn't seem to be present in your lockfile; try to make an install to update your resolutions

I got this error message after upgrading yarn to version 2.3.3 and removing the yarn.lock file.
It seems that yarn didn't generate a new lockfile after running yarn command.

I tried to debug with berry sources, but this issue isn't reproducible with 2.3.3-git.20201118.af1c837d.

[merceyz]

Please follow the issue template, there isn't much we can do based on this limited amount of information.

I tried to debug with berry sources, but this issue isn't reproducible with

So what you're saying is that it got fixed already?

[SmileyJames]

I am also experiencing this issue. I am attempting to migrate a yarn 1 project to yarn 2, following this guide: https://yarnpkg.com/getting-started/migration

yarn install doesn't generate a yarn.lock as promised

I am experiencing a minor error when executing yarn install, but the command as a whole exits with code 0

Then attempting to execute a yarn run commnd generates: "Internal Error: root@workspace:.: This package doesn't seem to be present in your lockfile; try to make an install to update your resolutions"

[merceyz]

I am experiencing a minor error when executing yarn install, but the command as a whole exits with code 0

Could you share said error?

[SmileyJames]

➤ YN0001: │ HTTPError: @my-scope/my-component@npm:^0.0.108: Response code 404 (Not Found)
    at se.<anonymous> (/Users/me/Code/my-project/.yarn/releases/yarn-berry.cjs:23:10082)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
➤ YN0000: └ Completed in 2s 242ms
➤ YN0000: Failed with errors in 2s 248ms

[merceyz]

That means the install failed and thus there is no lockfile, you need to setup the auth so Yarn can download the dependency.
https://yarnpkg.com/configuration/yarnrc#npmScopes.npmAuthToken or https://yarnpkg.com/configuration/yarnrc#npmAuthToken

This is mentioned as step 4 in the migration guide https://yarnpkg.com/getting-started/migration#step-by-step

[SmileyJames]

@merceyz Firstly, thanks for your help. The registry we are using is certificate protected. My old .yarnrc has registry, caFilePath, cert and key config
I can see new config options for registry and caFilePath, but cert and key do not seem to be available in the new yml format.

Does yarn 2 support certificate protected registries at this time?

[merceyz]

No, not at the moment. A PR adding support for those would be welcome

[SmileyJames]

Thank you for all your help! From my perspective this issue can be closed, although OP may disagree.

[yarnbot]

Hi! 👋

This issue looks stale, and doesn't feature the reproducible label - which implies that you didn't provide a working reproduction using Sherlock. As a result, it'll be closed in a few days unless a maintainer explicitly vouches for it or you edit your first post to include a formal reproduction (you can use the playground for that).

Note that we require Sherlock reproductions for long-lived issues (rather than standalone git repositories or similar) because we're a small team. Sherlock gives us the ability to check which bugs are still affecting the master branch at any given point, and decreases the amount of code we need to run on our own machines (thus leading to faster bug resolutions). It helps us help you! 😃

If you absolutely cannot reproduce a bug on Sherlock (for example because it's a Windows-only issue), a maintainer will have to manually add the upholded label. Thanks for helping us triaging our repository! 🌟

[SmileyJames]

Thank you for closing

We managed to resolve this issue by migrating our infrastructure from mTLS to OAuth provided by GitHub.

Soon we will be using Yarn 2

[evertoncruz]

I am also experiencing this issue. I am attempting to migrate a yarn 1 project to yarn 2, following this guide: https://yarnpkg.com/getting-started/migration

yarn install doesn't generate a yarn.lock as promised

I am experiencing a minor error when executing yarn install, but the command as a whole exits with code 0

Then attempting to execute a yarn run commnd generates: "Internal Error: root@workspace:.: This package doesn't seem to be present in your lockfile; try to make an install to update your resolutions"

Thank you !!! Work for me!!!