Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Newer versions of yarn depend on more files than "yarn.lock". As a result, the tarballs need to include these core files to ensure that any future commands against the tarball contents utilize the right version of
yarn
.Example
Configuring yarn v4 with a "pinned version" requires the ".yarnrc.yml" file along with the
yarnPath
configuration value. If configured to use a specific version of yarn, Yarn will download required files into a "./.yarn/releases/" directory. In the future, any execution ofyarn
will pick up theyarnPath
configuration and use the "./.yarn/releases/" directory contents to download and use the specific version of yarn.Current impacts
Without these changes, modern versions of
yarn
, like Yarn v4, do not properly install their dependencies when packaging for release. For example, if yarn 4 is configured to scope dependency installations to the workspace and use a classic node modules setup, the current build will only copy "yarn.lock" and either not upgrade Yarn to v4 and not copy (respect) the v4 configuration from ".yarnrc.yml" or will properly discover and use yarn v4 viacorepack
from the "package.json" file and "packageManager" value, but will still not copy (respect) the v4 configuration from ".yarnrc.yml".Testing these changes
yarn build
yarn oclif pack win