I have a package.json that I've organised to keep the dependencies grouped (based on keeping the vanilla react-native dependencies separate from our custom ones, to help with upgrading). I've upgraded this to use yarn 3.6.4 and now when I run yarn install (even if the current node_modules is in sync with the yarn.lock, so effectively a no-op) the listings for dependencies and devDependencies are reordered alphabetically, with any manual grouping stripped out.
My expectation is that the package.json file is respected in all ways as much as possible, including formatting, and it feels like this is a regression from previous versions of yarn.
Self-service
Describe the bug
I have a
package.json
that I've organised to keep the dependencies grouped (based on keeping the vanilla react-native dependencies separate from our custom ones, to help with upgrading). I've upgraded this to use yarn 3.6.4 and now when I runyarn install
(even if the currentnode_modules
is in sync with theyarn.lock
, so effectively a no-op) the listings fordependencies
anddevDependencies
are reordered alphabetically, with any manual grouping stripped out.My expectation is that the
package.json
file is respected in all ways as much as possible, including formatting, and it feels like this is a regression from previous versions of yarn.To reproduce
Starting with a
package.json
like so:run
yarn install
, which modifiespackage.json
to:Environment
Additional context
No response