-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see whatβs changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: yarnpkg/berry
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: d2afdfcf8819c449dc9784959ab5beb1389a4b26
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: yarnpkg/berry
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 68e10d099fb6bee03e4450bc516c0c04e24bcb96
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 10 commits
- 21 files changed
- 9 contributors
Commits on Aug 24, 2024
-
Configuration menu - View commit details
-
Copy full SHA for d12fd9b - Browse repository at this point
Copy the full SHA d12fd9bView commit details
Commits on Aug 25, 2024
-
feat(builder): transform
node:
imports as needed (#6356)## What's the problem this PR addresses? <!-- Describe the rationale of your PR. --> <!-- Link all issues that it closes. (Closes/Resolves #xxxx.) --> Yarn plugins used to be forbidden to import/require built-in modules prefixed with `node:`. see #6135 see #5417 Fixes #5637 The yarn plugin builder should be aware of this fact and produce bundled code, that does not contain any `node:` prefixed import/require. This is especially important when building plugins with 3rd party dependencies, where the plugin author cannot "fix" the imports to yarn's needs. ## How did you fix it? <!-- A detailed description of your implementation. --> I enabled the plugin-compiler to generate the plugin-code as needed: I utilized the capability of `esbuild` to strip these `node:` prefixes from import/require instructions. Therefore, I added config options to the plugin build process to instruct `esbuild` to do so. This is a fix of the plugin builder, which enables plugin authors to compile their work in a backwards-compatible way, so that the build result is runnable in old/unpatched versions of yarn. Unpatched regarding #5997 ## Related The #5997 tries to address the issue from the plugin-runtime side. This would enable "broken" plugins to be runnable in all future/patched versions of yarn-core. ## Additionally This very PR aims to enable plugin authors to create plugins that are runnable with unpatched versions of yarn-core. It is considered a friction-free backwards-compatible solution on all ends. Yet it does not replace #5997. ## Checklist <!--- Don't worry if you miss something, chores are automatically tested. --> <!--- This checklist exists to help you remember doing the chores when you submit a PR. --> <!--- Put an `x` in all the boxes that apply. --> - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). <!-- See https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released for more details. --> <!-- Check with `yarn version check` and fix with `yarn version check -i` --> - [x] I have set the packages that need to be released for my changes to be effective. <!-- The "Testing chores" workflow validates that your PR follows our guidelines. --> <!-- If it doesn't pass, click on it to see details as to what your PR might be missing. --> - [x] I will check that all automated PR checks pass before the PR gets reviewed. --------- Signed-off-by: Jan Kowalleck <jan.kowalleck@gmail.com> Co-authored-by: MaΓ«l Nison <nison.mael@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for b2f315f - Browse repository at this point
Copy the full SHA b2f315fView commit details -
| Package name | Version | | --- | --- | | `@yarnpkg/builder` | `4.2.0` |
Configuration menu - View commit details
-
Copy full SHA for 50ac1e4 - Browse repository at this point
Copy the full SHA 50ac1e4View commit details -
Configuration menu - View commit details
-
Copy full SHA for cadd19e - Browse repository at this point
Copy the full SHA cadd19eView commit details -
fix(core): determine if a module is a builtin using
module.isBuiltin
(#5997) **What's the problem this PR addresses?** <!-- Describe the rationale of your PR. --> `builder plugin` may output `node:process` instead of `process` in the generated file. When executing `yarn.`, it will report an error like: ``` This plugin cannot access the package referenced via node:process which is neither a builtin, nor an exposed entry ``` ** Environment ``` β― yarn tsc --version Version 5.3.2 ``` <!-- Link all issues that it closes. (Closes/Resolves #xxxx.) --> ... **How did you fix it?** <!-- A detailed description of your implementation. --> **Checklist** <!--- Don't worry if you miss something, chores are automatically tested. --> <!--- This checklist exists to help you remember doing the chores when you submit a PR. --> <!--- Put an `x` in all the boxes that apply. --> - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). <!-- See https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released for more details. --> <!-- Check with `yarn version check` and fix with `yarn version check -i` --> - [x] I have set the packages that need to be released for my changes to be effective. <!-- The "Testing chores" workflow validates that your PR follows our guidelines. --> <!-- If it doesn't pass, click on it to see details as to what your PR might be missing. --> - [x] I will check that all automated PR checks pass before the PR gets reviewed. --------- Co-authored-by: MaΓ«l Nison <nison.mael@gmail.com> Co-authored-by: Kristoffer K. <merceyz@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 3b156c9 - Browse repository at this point
Copy the full SHA 3b156c9View commit details -
feat(shell): add unset command (#6430)
## What's the problem this PR addresses? <!-- Describe the rationale of your PR. --> <!-- Link all issues that it closes. (Closes/Resolves #xxxx.) --> Fixes #4447. ## How did you fix it? <!-- A detailed description of your implementation. --> I fixed it by adding an `unset` built-in. ## Checklist <!--- Don't worry if you miss something, chores are automatically tested. --> <!--- This checklist exists to help you remember doing the chores when you submit a PR. --> <!--- Put an `x` in all the boxes that apply. --> - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). <!-- See https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released for more details. --> <!-- Check with `yarn version check` and fix with `yarn version check -i` --> - [x] I have set the packages that need to be released for my changes to be effective. <!-- The "Testing chores" workflow validates that your PR follows our guidelines. --> <!-- If it doesn't pass, click on it to see details as to what your PR might be missing. --> - [x] I will check that all automated PR checks pass before the PR gets reviewed. --------- Co-authored-by: merceyz <merceyz@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 10d16c3 - Browse repository at this point
Copy the full SHA 10d16c3View commit details
Commits on Sep 12, 2024
-
fix(nm): Stop hoisting rounds only when nothing were hoisted (#6495)
## What's the problem this PR addresses? <!-- Describe the rationale of your PR. --> <!-- Link all issues that it closes. (Closes/Resolves #xxxx.) --> Fixes #6493 Fixes #6494 ## How did you fix it? <!-- A detailed description of your implementation. --> Issue: #6493. Sometimes hoisting algorithm was stopped too early, because it wasn't able to determine correctly stop condition. I made it safer but possibly one round slower by stopping only when nothing was hoisted during the last round. Issue: #6494. Hoisting avoided hoisting to non-root workspace previously, I have removed this limitation, because it made inner workspaces meaningless. ## Checklist <!--- Don't worry if you miss something, chores are automatically tested. --> <!--- This checklist exists to help you remember doing the chores when you submit a PR. --> <!--- Put an `x` in all the boxes that apply. --> - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). <!-- See https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released for more details. --> <!-- Check with `yarn version check` and fix with `yarn version check -i` --> - [x] I have set the packages that need to be released for my changes to be effective. <!-- The "Testing chores" workflow validates that your PR follows our guidelines. --> <!-- If it doesn't pass, click on it to see details as to what your PR might be missing. --> - [x] I will check that all automated PR checks pass before the PR gets reviewed.
Configuration menu - View commit details
-
Copy full SHA for a22486f - Browse repository at this point
Copy the full SHA a22486fView commit details
Commits on Sep 13, 2024
-
Avoid crash in simplifyRanges by removing subsets up front (#6459)
## What's the problem this PR addresses? Resolves #6373. The problem is that `simplifyRanges` doesn't correctly reduce redundant OR ranges. For example, `~1.0.1 || ~1.0.2` should be simplified to `~1.0.1`. As the algorithm runs, it will effectively calculate every _combination_ of terms in such ranges. For example, given two ranges like `~1.0.1 || ~1.0.2`, the `nextAlternatives` array will end up with 2*2 = 4 entries; if you have 100 such ranges you'll end up with 2^100 entries. Growing exponentially like this it's not hard to crash the process. Arguably packages should not specify peer deps with this sort of redundant range, but sometimes they do (I'm working on cleaning up my project now that I know what the problem is!) Regardless, yarn shouldn't crash when it happens. ## How did you fix it? At the beginning of `simplifyRanges`, I reduce any range of this sort by splitting it apart and using `sember.subset` to check if one part of the range is a subset of another, in which case it can be excluded from the simplified range. I short circuit if the range only has one term, to avoid any excess parsing. I think this is the right fix, but I'm happy to take feedback or hand it off if someone knows better. (Maybe @arcanis as author of this code?) ## Checklist <!--- Don't worry if you miss something, chores are automatically tested. --> <!--- This checklist exists to help you remember doing the chores when you submit a PR. --> <!--- Put an `x` in all the boxes that apply. --> - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). <!-- See https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released for more details. --> <!-- Check with `yarn version check` and fix with `yarn version check -i` --> - [x] I have set the packages that need to be released for my changes to be effective. <!-- The "Testing chores" workflow validates that your PR follows our guidelines. --> <!-- If it doesn't pass, click on it to see details as to what your PR might be missing. --> - [x] I will check that all automated PR checks pass before the PR gets reviewed.
Configuration menu - View commit details
-
Copy full SHA for 758a8be - Browse repository at this point
Copy the full SHA 758a8beView commit details -
fix(ci): add workaround for Parcel not working with Yarn PnP (#6447)
## What's the problem this PR addresses? It seems like the issue (parcel-bundler/parcel#9114) is stuck on Parcel's side with no interest of it being fixed. ## How did you fix it? While this is not ideal, that leaves us with two choices: add a workaround and continue testing Parcel, or remove E2E tests for Parcel altogether. I chose the former. ## Checklist <!--- Don't worry if you miss something, chores are automatically tested. --> <!--- This checklist exists to help you remember doing the chores when you submit a PR. --> <!--- Put an `x` in all the boxes that apply. --> - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). <!-- See https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released for more details. --> <!-- Check with `yarn version check` and fix with `yarn version check -i` --> - [x] I have set the packages that need to be released for my changes to be effective. <!-- The "Testing chores" workflow validates that your PR follows our guidelines. --> <!-- If it doesn't pass, click on it to see details as to what your PR might be missing. --> - [x] I will check that all automated PR checks pass before the PR gets reviewed.
Configuration menu - View commit details
-
Copy full SHA for 58475b9 - Browse repository at this point
Copy the full SHA 58475b9View commit details
Commits on Sep 14, 2024
-
| Package name | Version | | --- | --- | | `@yarnpkg/cli` | `4.5.0` | | `@yarnpkg/shell` | `4.1.0` | | `@yarnpkg/nm` | `4.0.3` | | `@yarnpkg/plugin-nm` | `4.0.4` | | `@yarnpkg/pnpify` | `4.1.2` | | `@yarnpkg/core` | `4.1.3` |
Configuration menu - View commit details
-
Copy full SHA for 68e10d0 - Browse repository at this point
Copy the full SHA 68e10d0View commit details
There are no files selected for viewing
Large diffs are not rendered by default.
Large diffs are not rendered by default.