Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Bug] Preserve comments and styling in YAML configuration

See original GitHub issue

Whenever I update Yarn 2 or I want to test a branch with yarn set version from sources it changes the yarnrc.yml.

The order of the fields changes and the commented lines disappear, is it possible to keep the file as close as possible to the state in which the user left it?

Issue Analytics

State:
Created 3 years ago
Reactions:7
Comments:6 (2 by maintainers)

Top GitHub Comments

7reactions

borekbcommented, Sep 8, 2020

@paul-soporan I just came to search the issues after Yarn deleted my comments from .yarnrc.yml file (which made a bit angry to be honest 😄; I hate when tools silently drop my data) so it’s great to see your thoughtful comment above.

I’ll just say a few things:

Reordering .yarnrc.yml is unpleasant. In fact, we usually run a command like yarn set version, then copy the relevant line, revert the whole file and re-add manually. Doesn’t feel right.
Data loss is plan unacceptable, IMO.
Bundle size wouldn’t be a problem if the binary wasn’t committed to a Git repo – I guess we’re waiting for #969 or pmm so generally yeah, you probably need to worry about bundle size and make difficult tradeoffs.

0reactions

belgattitudecommented, Mar 12, 2022

@lensbart

The road i tried didn’t give what i hoped for.

bundle size is okay, but too slow in my tests

https://github.com/yarnpkg/berry/pull/4135#discussion_r810542028

Another idea welcome