Merged
Conversation
|
@arcanis Hello it seems like latest version of yarn brings regression, it cannot find nearest package.json file. So having package.json in root of the project and trying to run Downgrade to |
Member
Author
|
Can you give me a reproduction? According to your post the following should crash, but doesn't for me: |
|
Dockerfile |
|
Sorry for bothering. #7939 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #8793
Fixes #8965
Fixes #9005
Punycode is now embed within the bundle, as it has been deprecated by Node.js and will be removed in a future version.
A message will be displayed when Yarn 1.22 notices that the local project has a
package.jsonfile referencing a non-1.x Yarn release. The message will explain that the project is intended to be used with Corepack.I removed the
yarn-error.loggeneration. Given that we don't process non-critical 1.x bug reports, they are now mostly an annoyance.The
yarn set version x.y.zcommand will now install the exactx.y.zversion (prior to this change it used to first install the latest version, and only in a second step would it downgrade tox.y.z; this was causing issues when we bump the minimal Node.js version we support, as runningyarn set version 3.6.4wouldn't work on Node 16).Prevents crashes when reading from an empty
.yarnrc.ymlfile.