You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following dependency does not get migrated correctly when running a yarn install:
"@typescript/lib-dom@npm:@types/web":
version "0.0.61"
resolved "https://registry.yarnpkg.com/@types/web/-/web-0.0.61.tgz#29bb8951e17b7597084c7a4cccd5072711b0ac09"
integrity sha512-lQ4M3OSh8eFj55fz1RJsLhCubET/7duOXoKcxVaUXYXyxikD9BA+WWrqAn5CjJxrc82b7zFY4OCVIeVdkPLaGg==
During the process, yarn will try to migrate but fail because of the wrong URL:
$ yarn install --immutable
➤ YN0070: Migrating from Yarn 1; automatically enabling the compatibility node-modules linker 👍
➤ YN0000: ┌ Resolution step
Resolution step
➤ YN0035: @typescript/lib-dom@npm:@types/web: The remote server failed to provide the requested resource
➤ YN0035: Response Code: 404 (Not Found)
➤ YN0035: Request Method: GET
➤ YN0035: Request URL: https://registry.yarnpkg.com/@typescript%2flib-dom
➤ YN0000: └ Completed in 51s 800ms
➤ YN0000: Failed with errors in 51s 805ms
I assume this is related to the issue #5085 so I attempted to transform the URL manually (similar to here), but I'm not sure how it has to look like.
Manually converting the entry to for example this:
"@typescript/lib-dom@types/web":
version "0.0.61"
resolved "@typescript/lib-dom@types/web@npm:0.0.61::__archiveUrl=https%3A%2F%2Fregistry%2Eyarnpkg%2Ecom%2F%40types%2Fweb%2F%2D%2Fweb%2D0%2E0%2E61%2Etgz"
integrity sha512-lQ4M3OSh8eFj55fz1RJsLhCubET/7duOXoKcxVaUXYXyxikD9BA+WWrqAn5CjJxrc82b7zFY4OCVIeVdkPLaGg==
Does not fix the issue unfortunately. I'm receiving the unsupported resolver error. I tried different combinations of version/package name with and without :npm in the name, etc. Then again, this was fairly random - I'm quite unfamiliar with the format.
Self-service
Describe the bug
The following dependency does not get migrated correctly when running a yarn install:
During the process, yarn will try to migrate but fail because of the wrong URL:
I assume this is related to the issue #5085 so I attempted to transform the URL manually (similar to here), but I'm not sure how it has to look like.
Manually converting the entry to for example this:
Does not fix the issue unfortunately. I'm receiving the unsupported resolver error. I tried different combinations of version/package name with and without :npm in the name, etc. Then again, this was fairly random - I'm quite unfamiliar with the format.
To reproduce
echo '"@typescript/lib-dom@npm:@types/web":
version "0.0.61"
resolved "https://registry.yarnpkg.com/@types/web/-/web-0.0.61.tgz#29bb8951e17b7597084c7a4cccd5072711b0ac09"
integrity sha512-lQ4M3OSh8eFj55fz1RJsLhCubET/7duOXoKcxVaUXYXyxikD9BA+WWrqAn5CjJxrc82b7zFY4OCVIeVdkPLaGg==' > yarn.lock; yarn set version stable; yarn install --immutable
Environment
Additional context
This is how the entry is supposed to look like when created with yarn3:
The text was updated successfully, but these errors were encountered: