vercel[bot]
commented
2 years ago This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployments, click below or on the icon next to each commit.
vue2 – ./
🔍 Inspect: https://vercel.com/mcaj-git/vue2/CuiVKy12kJGPo91MLyekArDGvSZf
✅ Preview: Failed
poc-vue3 – ./
🔍 Inspect: https://vercel.com/mcaj-git/poc-vue3/5NSSTBkoWWybuEY9zTTS5zwrWY9H
✅ Preview: Failed
poc – ./
🔍 Inspect: https://vercel.com/mcaj-git/poc/8W3sRuFQLzbdCF6tkEbG8PQrW7fX
✅ Preview: Failed
lgtm-com[bot]
This PR contains the following updates:
3.1.1->3.2.3Release Notes
yarnpkg/berry
### [`v3.2.3`](https://togithub.com/yarnpkg/berry/blob/HEAD/CHANGELOG.md#323) [Compare Source](https://togithub.com/yarnpkg/berry/compare/7a42886db3ad437b5f0c2dc6e12c2cd9b894070d...3f3b8a529b32fe3a92a19724df54434c9e1958fa) ##### Bugfixes - When Corepack is enabled Yarn will now use the current CLI to prepare external Yarn classic projects, matching the behaviour of when Corepack is disabled. ##### Compatibility - Updates the PnP compatibility layer for TypeScript 4.8.1-rc - The ESM loader now supports unflagged JSON modules. ### [`v3.2.2`](https://togithub.com/yarnpkg/berry/blob/HEAD/CHANGELOG.md#322) [Compare Source](https://togithub.com/yarnpkg/berry/compare/d157755d585627623dfeebff154842dfe29eb871...7a42886db3ad437b5f0c2dc6e12c2cd9b894070d) ##### Compatibility - The patched filesystem now supports `ftruncate`. - The patched filesystem now supports `fchmod`. - The patched filesystem now supports `throwIfNoEntry`. - The PnP filesystem now handles most of the FileHandle methods - Updates the PnP compatibility layer for TypeScript 4.8 Beta - The `npm_package_json` environment variable is now set by Yarn. ### [`v3.2.1`](https://togithub.com/yarnpkg/berry/blob/HEAD/CHANGELOG.md#321) [Compare Source](https://togithub.com/yarnpkg/berry/compare/58dd22e47eb46da5c2c32377ed5f749754b9ea64...d157755d585627623dfeebff154842dfe29eb871) ##### Installs - The pnpm linker no longer tries to remove `node_modules` directory, when `node-modules` linker is active - The node-modules linker does not fail anymore if portal dependency points to an external project with multiple interdependent workspaces - The node-modules linker has received various improvements: - applies hoisting algorithm on aliased dependencies - reinstalls modules that have their directories removed from node_modules by the user - improves portal hoisting - supports `supportedArchitectures` ##### Bugfixes - The PnP ESM loader is now able to handle symlinked extensionless entrypoints. ### [`v3.2.0`](https://togithub.com/yarnpkg/berry/blob/HEAD/CHANGELOG.md#320) [Compare Source](https://togithub.com/yarnpkg/berry/compare/8a82356039ae60f859daa8e6bda3ca681e7c2b0e...58dd22e47eb46da5c2c32377ed5f749754b9ea64) Various improvements have been made in the core to improve performance. Additionally: ##### Commands - The `yarn workspaces foreach run` command is now able to run binaries. - The `yarn npm info` command now supports displaying information about a tagged version of a package (e.g. `yarn npm info vue@next`). - A new `yarn explain` command has been added. It can be used to explain an error code, or list all available error codes. - For example, try to run `yarn explain YN0002`. - The `yarn npm publish` command now accepts a new `--otp` option, to set the One-Time Password from the CLI. - A better error message will also be shown when a query fails due to an invalid OTP. - `yarn upgrade-interactive` now has improved paging: - Yarn will display as many suggestions as can fit in the viewport (rather than a fixed-size list). - The suggestions that fit in the viewport will be fetched in the foreground and will load one-by-one. - The suggestions that don't will be fetched in the background and will be loaded in batches to increase responsiveness and reduce input lag. - Most notably, you won't have to wait for all of the suggestions to be fetched (which took a very long time before on large monorepos) before you can start navigating through the list. ##### Installs - The node-modules linker now tolerates if `node_modules` is a symbolic link, and doesn't recreate it. - On top of the `cpu` and `arch` fields, Yarn now support a new `libc` field which can be used in tandem with `optionalDependencies` to avoid downloading packages that have been linked against incompatible standard libraries (we currently support two values: `glibc` and `musl`). - The pnpm linker has received various improvements: - It will now remove the `node_modules/.store` and `node_modules` folders if they are empty. - It now supports running binaries of soft links. - It will now create self-references for packages that don't depend on other versions of themselves. - It will now remove scope folders (e.g. `node_modules/@yarnpkg`) if they are empty or after removing a scoped dependency. - All `.pnp.cjs` files with inlined data will now store the data in a JSON string literal instead of an object literal [to improve startup performance](https://v8.dev/blog/cost-of-javascript-2019#json). ##### Compatibility - The shell now treats backslashes same as Bash (so it mostly ignore them). - Could potentially be a breaking change, but the old behavior caused portability issues with a few packages, so we had to make this change (especially since the portable shell is intended to help portability). - The shell now supports `${FOO:+}`. - The PnP filesystem now handles `read` and `readSync` using options. - The PnP filesystem now handles UNC paths using forward slashes. - The PnP filesystem now sets the proper `path` property on streams created by `createReadStream()` and obtained from zip archives. - The PnP runtime now throws an `ERR_REQUIRE_ESM` error when attempting to require an ES Module, matching the default Node.js behaviour. - Updates the PnP compatibility layer for TypeScript 4.6 Beta (it's possible we'll need to publish another patch update once the 4.6 enters stable). ##### Bugfixes - `@yarnpkg/pnpify` now escapes paths correctly. - The ESM loader is now enabled regardless of the entrypoint module type, this fixes support for dynamic imports in commonjs modules when the entrypoint is also commonjs. - The ESM loader is now able to resolve relative imports with search parameters. - The `node` field inside the `npm_config_user_agent` Yarn sets will now include a leading `v`. - Yarn is now able to recover from a corrupted install state. - Yarn is now able to migrate classic lockfiles containing unconventional tarball URLs. - The nm linker hoists portals after hoisting their dependencies first. - Fixed a crash caused by a bad interaction between aliased packages and peer dependencies. - The ESBuild plugin will no longer allow access to Node.js builtins if the `platform` isn't set to Node. - SemVer ranges with build metadata can now be resolved. - The `YARN_IGNORE_NODE` environment variable will now be parsed using the same mechanism as env variable configuration settings (i.e. both `1`/`0` and `true`/`false` will be accepted) ##### ZipFS Extension - You can now unmount zip folders by right-clicking on their workspaces. ##### Miscellaneous Features - Reporting for Git errors has been improved. - The resolution step now has a progress indicator. - The experimental ESM loader warning emitted by Node.js is now suppressed. - Private registries can now be authenticated using private keys and certificates. - A new `wrapNetworkRequest` hook now lets you wrap network requests (for example to log them).Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.