From c1c0d2567baf7ad975483dda3f6912bf7e076620 Mon Sep 17 00:00:00 2001 From: Dominic Griesel Date: Fri, 5 Jul 2024 11:27:18 +0200 Subject: [PATCH] chore: mention yarn and corepack in v13 migration guide --- docs/getting-started/migrating-to-v13.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/getting-started/migrating-to-v13.md b/docs/getting-started/migrating-to-v13.md index 77a9aaefb81b..ba364284ce67 100644 --- a/docs/getting-started/migrating-to-v13.md +++ b/docs/getting-started/migrating-to-v13.md @@ -125,3 +125,7 @@ It is recommended to check if `node.protocol === Protocols.ZWaveLongRange` or `i - The `noBulkSupport` property of `ConfigurationMetadata` has been removed. There is no replacement, as it was never meant to be user-facing - The `enableSoftReset` property of the `ZWaveOptions` has been removed. Use `features.softReset` instead. - The `mandatorySupportedCCs` and `mandatorControlledCCs` properties of the `DeviceClass` class have been removed. There is no replacement. + +## Migrated to Yarn 4 and Corepack + +The repository has been migrated to Yarn v4 and now uses [Corepack](https://github.com/nodejs/corepack) to automatically install the correct package manager version, without having to check it into git. This should work out of the box, unless `yarn` was previously installed globally as a system package on Linux. In that case, you may have to uninstall the Linux package and remove any additions to the `PATH` environment variable.