| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
Fix sherlock workflow again (#5788) **What's the problem this PR addresses?** <!-- Describe the rationale of your PR. --> <!-- Link all issues that it closes. (Closes/Resolves #xxxx.) --> After upgrading alpine for the sherlock workflow in #5718, the workflow still fails due to newer versions of alpine no longer having the `python2` package. Fixes #5709 **How did you fix it?** <!-- A detailed description of your implementation. --> Since we removed the old website in #5742, berry no longer depends on `sharp` so I just removed all the alpine packages needed to build `sharp` including `python2` **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> | 2 年前 | |
chore: update benchmark dependencies (#5390) | 3 年前 | |
chore: fix scripts/bin/yarnpkg symlink (#4647) | 4 年前 | |
fix(compat): Use cygpath for MINGW (Git Bash) (#4409) | 4 年前 | |
Update npm publish command in release script Removed '--staged' option from npm publish command. | 4 个月前 | |
Fixes global cache (#5739) **What's the problem this PR addresses?** The cache fix merged in https://github.com/yarnpkg/berry/pull/5730 had a bug that caused the global cache to be skipped when a package had no checksum - which happens when there are no lockfile in the project. This was detected by the perf regression visible on the dashboard: <img width="1381" alt="image" src="https://github.com/yarnpkg/berry/assets/1037931/11aed9d5-7946-418d-806a-6df78aee4734"> **How did you fix it?** I fixed the condition (it was "use the cache if there's a checksum and it's compatible", it should have been "use the cache if there's no checksum, or it's a compatible one") and added tests to avoid further regressions. **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. | 3 年前 | |
Enables postinstall scripts for pnpm (#6902) ## What's the problem this PR addresses? It came to me that since pnpm no longer runs postinstall scripts by default, the benchmark was a little skewed since Yarn (and npm) do. The benchmarks are intended to compare apples to apples, so either postinstalls should be disabled in Yarn / npm as well, or they should be enabled in pnpm. I think it makes more sense to enable them, as it can uncover bugs that would otherwise be hidden away. ## How did you fix it? Enabled the postinstall scripts in the package manager benchmarks. To be fair it probably doesn't change much, if anything - the full cold Gatsby benchmark shows around 2 seconds of removed install time around Feb 3rd 2025 which I think is caused by the lack of postinstall, although I'm not certain, but that's about it. Pnpm remains really fast, kudos! <img width="145" height="93" alt="Screenshot 2025-09-18 at 10 43 02" src="https://github.com/user-attachments/assets/3f9a362a-5c71-41c1-99b2-b2bc930ca796" /> Curiously the same change occurs in the "Recurrent calls" benchmark which probably shouldn't need to run postinstall scripts. Does pnpm have a bug causing it to rebuild postinstall scripts when they aren't needed? ## 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. | 1 年前 | |
build: explicitly set `noEmit: false` in the build script (#6266) **What's the problem this PR addresses?** https://github.com/yarnpkg/berry/pull/6133 (cc @clemyan) enabled `noEmit` by default which caused `yarn pack` to not get any build output. Fixes https://github.com/yarnpkg/berry/issues/6265 **How did you fix it?** Explicitly set `noEmit: false` in the build script. **Checklist** - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). - [x] I have set the packages that need to be released for my changes to be effective. - [x] I will check that all automated PR checks pass before the PR gets reviewed. | 2 年前 | |
feat: Tolerate string literals w/ `ppath.join` / `ppath.resolve` (#5250) * Allows generic as parameters for ppath.join / ppath.resolve * Removes "as" from callsites * Versions * Fixes lint * Replaces "(join\(.*`) as Filename" * Fixes lint | 3 年前 | |
Waits for the manifests to be written before running the second loops (#5871) **What's the problem this PR addresses?** I forgot to add a `Promise.all`, so the `package.json` files could end up corrupted when the constraints engine had to perform multiple iterations of the loop. Fixes #5853 **How did you fix it?** Adds `Promise.all` before running subsequent iterations. **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. | 2 年前 | |
ci: enable PnP ESM loader in all e2e tests (#4088) | 4 年前 | |
test: transpile using esbuild (#5581) **What's the problem this PR addresses?** We use esbuild to build and run Yarn from sources but not for our test files. Follow-up to https://github.com/yarnpkg/berry/pull/5180 **How did you fix it?** Use esbuild to transpile files in our testing setup. **Checklist** - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). - [x] I have set the packages that need to be released for my changes to be effective. - [x] I will check that all automated PR checks pass before the PR gets reviewed. | 2 年前 | |
Enables all official plugins by default (#4253) * wip * Enables all plugins by default * Lazy-loads packages * Only adds @types/ packages if the project has a tsconfig * Removes debug * Fixes lint * Adds a configuration option for @types auto-adds * Fixes tests * Removes plugin configuration from the tests * Fixes linting * Removes plugins from the scripts directory * Removes checked-in plugins * Removes plugins from the yaml database * Removes the update-local scripts * Removes the plugin build from the CI * Disables auto types removal if tsEnableAutoTypes is set * Updates readme * Simplifies rc build * Fixes plugins.yml * Fixes tests * Fixes tests * Adds debug workflow * Removes yup * Cancels the debug job on repeated triggers | 4 年前 | |
chore: add script to generate e2e status list (#6434) **What's the problem this PR addresses?** The e2e status table in our README.md needs to be kept up to date manually whenever we add or remove an e2e test and there is no automated check to ensure that it's correct. **How did you fix it?** Add a script to generate an e2e status list and add a CI check for it. **Checklist** - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). - [x] I have set the packages that need to be released for my changes to be effective. - [x] I will check that all automated PR checks pass before the PR gets reviewed. | 1 年前 | |
Rename the `berry` references into `yarnpkg` (#395) * Renames everything to the yarnpkg scope * More renaming * Fixes snapshots * Updates the README * Fixes the merge conflict resolution test * Updates the documentation | 7 年前 | |
Migrates to Clipanion 3 (#2370) * Migrates to Clipanion 3 * Removes yup entirely * Uncomments debug * Bumps clipanion * Update packages/plugin-essentials/sources/commands/run.ts Co-authored-by: Paul Soporan <paul.soporan@gmail.com> * Versions * Updates the internal builtins * Adds missing path * Bumps clipanion * Bumps typanion & clipanion * Fixes incorrect paths * Fixes tests * Fixes regex Co-authored-by: Paul Soporan <paul.soporan@gmail.com> | 5 年前 | |
Migrates to Clipanion 3 (#2370) * Migrates to Clipanion 3 * Removes yup entirely * Uncomments debug * Bumps clipanion * Update packages/plugin-essentials/sources/commands/run.ts Co-authored-by: Paul Soporan <paul.soporan@gmail.com> * Versions * Updates the internal builtins * Adds missing path * Bumps clipanion * Bumps typanion & clipanion * Fixes incorrect paths * Fixes tests * Fixes regex Co-authored-by: Paul Soporan <paul.soporan@gmail.com> | 5 年前 | |
feat: builder improvements (#1486) * chore: upgrade to webpack 5 * build: use fork-ts-checker-webpack-plugin * docs: add builder documentation * chore: set versions * chore: fixes * fix: add clipanion command to builder * chore: update PnP hook * chore: update gatsby * chore: fix gatsby * chore: update some dependencies * chore: add redirect * chore: fix gatsby and update releases * ci: add typecheck to chores * chore: fix gatsby * chore: upgrade babel * chore: enable isolatedModules and fix errors * docs: add missing comma * chore: update pnp hook * chore: update jest and update @babel/core resolution in lockfile * chore: update pnp hook * fix: fix errors * refactor: cast -> identity | 6 年前 | |
feat(pnpify): improve pnpify (#1446) * feat(pnpify): improve pnpify * test: fix tests * docs: update `.vscode/pnpify` references to `.yarn/pnpify` * refactor: change logic * refactor: small tweaks * refactor: tweaks * refactor: not so small tweaks * chore: add redirect * test: fix tests * refactor: change editors to rest arguments * docs: fix wrong link * docs: update .yarn/pnpify gitignore details Co-authored-by: Maël Nison <nison.mael@gmail.com> * Update packages/yarnpkg-pnpify/sources/generateSdk.ts Co-authored-by: Maël Nison <nison.mael@gmail.com> * Update packages/yarnpkg-pnpify/sources/generateSdk.ts Co-authored-by: Maël Nison <nison.mael@gmail.com> * Update packages/yarnpkg-pnpify/sources/generateSdk.ts Co-authored-by: Maël Nison <nison.mael@gmail.com> * refactor: remove versions * refactor: change variable names * refactor: add back line separators * chore: run pnpify sdk * refactor: remove null * refactor: refactor EDITOR_SDKS * chore: update versions * chore: fix versions * chore: fix constraints * fix: fix miscUtils * feat: remove existing SDKs inside old .vscode/pnpify folder * refactor: chalk -> configuration.format * refactor: base -> onlyBase * refactor: EditorsFile.hasEditorsFile * fix: fix error * Update packages/yarnpkg-pnpify/sources/generateSdk.ts Co-authored-by: Kristoffer K. <merceyz@users.noreply.github.com> * Update packages/yarnpkg-pnpify/sources/sdks/vscode.ts Co-authored-by: Kristoffer K. <merceyz@users.noreply.github.com> * refactor: editor -> integration * refactor: better error messages Co-authored-by: Maël Nison <nison.mael@gmail.com> Co-authored-by: Kristoffer K. <merceyz@users.noreply.github.com> | 6 年前 | |
Split sdks and nm into separate packages from @yarnpkg-pnpify (#3069) * Splits pnpify into nm, sdks and pnpify * Fixes constraints * Fixes type errors * Refactors plugin-node-modules into plugin-nm * refactor: refactor @yarnpkg/pnpify and @yarnpkg/sdks * chore: update clipanion * Renames plugin-node-modules to plugin-nm in version files * Revert "chore: update clipanion" This reverts commit e30c72566a2d132aa0c098a7bf430742f909b28c. * Revert accidental revert * chore: run an install * fix: fix definitions command * chore: fix typedoc * test: fix tests * Update packages/yarnpkg-sdks/sources/commands/SdkCommand.ts Co-authored-by: Maël Nison <nison.mael@gmail.com> * Update packages/yarnpkg-sdks/sources/generateSdk.ts Co-authored-by: Maël Nison <nison.mael@gmail.com> * refactor: use builtin definitions command * refactor: uniformize --clipanion=definitions * chore: fix website * chore: remove accidental dependencies on tslib * chore: run an install * chore: readme * chore: typedoc * chore: rename more references * chore: outdated file references * chore: changelog * refactor: change sdk version suffix * refactor: make it a fixed version * Replaces plugin-node-modules ->plugin-nm in versions * Adds note about plugin-node-modules renaming * Update packages/gatsby/content/getting-started/editor-sdks.md Co-authored-by: Maël Nison <nison.mael@gmail.com> Co-authored-by: Paul Soporan <paul.soporan@gmail.com> Co-authored-by: Maël Nison <nison.mael@gmail.com> | 5 年前 | |
Bumps TypeScript to 5.9 (#6889) ## What's the problem this PR addresses? I'm looking at migrating to TypeScript-go whenever it supports PnP; to that end we first need to upgrade to the latest stable TypeScript releases. ## How did you fix it? Mostly just a matter of upgrading `@types/node` and updating the various types in FakeFS that got changed. ## 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. | 1 年前 | |
Implements a check utility (#578) * wip * Fixes build * Bumps everything (probably overkill) * More fixes * Removes Node 8 from the tests * Dont minify files * Fixes builder on Windows * Fixes things | 6 年前 | |
Reworks actions | 7 年前 | |
Migrates the "typescript" dependencies to a catalog (#6969) ## What's the problem this PR addresses? We don't currently use / dogfood the `catalog:` specifier. As a result we didn't notice that the compat plugin was incorrectly ordered; we want to apply it before performing the compat changes, but the current code was going the other way around. Fixes #6920 ## How did you fix it? - Make the monorepo use `catalog:` for the `typescript` package. - Fixes the local development setup to load plugins in the same order as the CLI bundle. - Reorders the plugins so that `catalog:` is resolved before the compatibility patches are applied. ## 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. | 11 个月前 | |
deps: update to `esbuild-wasm@0.23.0` (#6387) **What's the problem this PR addresses?** - We haven't updated esbuild for a few years so we're a bit behind on new features, bugfixes, and improvements. - We're building Yarn with one esbuild version and running from sources/tests with another. **How did you fix it?** Update to the latest version. **Checklist** - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). - [x] I have set the packages that need to be released for my changes to be effective. - [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> | 2 年前 | |
test: transpile using esbuild (#5581) **What's the problem this PR addresses?** We use esbuild to build and run Yarn from sources but not for our test files. Follow-up to https://github.com/yarnpkg/berry/pull/5180 **How did you fix it?** Use esbuild to transpile files in our testing setup. **Checklist** - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). - [x] I have set the packages that need to be released for my changes to be effective. - [x] I will check that all automated PR checks pass before the PR gets reviewed. | 2 年前 | |
test: transpile using esbuild (#5581) **What's the problem this PR addresses?** We use esbuild to build and run Yarn from sources but not for our test files. Follow-up to https://github.com/yarnpkg/berry/pull/5180 **How did you fix it?** Use esbuild to transpile files in our testing setup. **Checklist** - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). - [x] I have set the packages that need to be released for my changes to be effective. - [x] I will check that all automated PR checks pass before the PR gets reviewed. | 2 年前 | |
Sync master with the changes from cherry-pick/3.4 | 3 年前 | |
Sync master with the changes from cherry-pick/3.4 | 3 年前 | |
Update submit-bench-data.js | 6 年前 | |
ci: fix the typescript e2e test (#4888) | 4 年前 | |
Split sdks and nm into separate packages from @yarnpkg-pnpify (#3069) * Splits pnpify into nm, sdks and pnpify * Fixes constraints * Fixes type errors * Refactors plugin-node-modules into plugin-nm * refactor: refactor @yarnpkg/pnpify and @yarnpkg/sdks * chore: update clipanion * Renames plugin-node-modules to plugin-nm in version files * Revert "chore: update clipanion" This reverts commit e30c72566a2d132aa0c098a7bf430742f909b28c. * Revert accidental revert * chore: run an install * fix: fix definitions command * chore: fix typedoc * test: fix tests * Update packages/yarnpkg-sdks/sources/commands/SdkCommand.ts Co-authored-by: Maël Nison <nison.mael@gmail.com> * Update packages/yarnpkg-sdks/sources/generateSdk.ts Co-authored-by: Maël Nison <nison.mael@gmail.com> * refactor: use builtin definitions command * refactor: uniformize --clipanion=definitions * chore: fix website * chore: remove accidental dependencies on tslib * chore: run an install * chore: readme * chore: typedoc * chore: rename more references * chore: outdated file references * chore: changelog * refactor: change sdk version suffix * refactor: make it a fixed version * Replaces plugin-node-modules ->plugin-nm in versions * Adds note about plugin-node-modules renaming * Update packages/gatsby/content/getting-started/editor-sdks.md Co-authored-by: Maël Nison <nison.mael@gmail.com> Co-authored-by: Paul Soporan <paul.soporan@gmail.com> Co-authored-by: Maël Nison <nison.mael@gmail.com> | 5 年前 | |
Upgrades Eslint to v9 (#6694) ## What's the problem this PR addresses? We're still relying on ESLint 8, which isn't supported anymore. Fixes #6687, #6689 Supercedes #6693 ## How did you fix it? This PR upgrades ESLint to its latest version, switching to the stylistic rules when needed. No rules were removed. ## 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. | 1 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 2 年前 | ||
| 3 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 4 个月前 | ||
| 3 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 3 年前 | ||
| 2 年前 | ||
| 4 年前 | ||
| 2 年前 | ||
| 4 年前 | ||
| 1 年前 | ||
| 7 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 6 年前 | ||
| 6 年前 | ||
| 5 年前 | ||
| 1 年前 | ||
| 6 年前 | ||
| 7 年前 | ||
| 11 个月前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 6 年前 | ||
| 4 年前 | ||
| 5 年前 | ||
| 1 年前 |