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
What you expected to see, versus what you actually saw
The file that is required by the .yarnrc.yml file is not installed locally, so when triggering an update and attempting to run yarn --version, I get the error:
*** Dependabot::SharedHelpers::HelperSubprocessFailed Exception: node:internal/modules/cjs/loader:1146
throw err;
^
Error: Cannot find module 'dependabot_tmp_dir/.yarn/releases/yarn-3.8.0.cjs'
at Module._resolveFilename (node:internal/modules/cjs/loader:1143:15)
at Module._load (node:internal/modules/cjs/loader:984:27)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:135:12)
at node:internal/main/run_main_module:28:49 {
code: 'MODULE_NOT_FOUND',
requireStack: []
}
Instead, I would expect that the required file for running yarn would be ported over (or that it would be set up so that it uses a global version).
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Package ecosystem
npm and yarn
Package manager version
yarn 3.8.0
Language version
Ruby 3.3
Manifest location and content before the Dependabot update
.yarnrc.yml
package.json
dependabot.yml content
No response
Updated dependency
No response
What you expected to see, versus what you actually saw
The file that is required by the
.yarnrc.yml
file is not installed locally, so when triggering an update and attempting to runyarn --version
, I get the error:Instead, I would expect that the required file for running yarn would be ported over (or that it would be set up so that it uses a global version).
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
No response
The text was updated successfully, but these errors were encountered: