[Bug?]: YAMLException: bad indentation of a mapping entry at line

Self-service

• I’d be willing to implement a fix

Describe the bug

Trying install package or importing a plugin through the commands yarn install & yarn plugin import typescript` throws the following error:

YAMLException: bad indentation of a mapping entry at line 4, column 15:
      dependencies:
                  ^
      dependencies:
                  ^
    at Bq (E:\Projects\frontend\blog\.yarn\releases\yarn-3.0.2.cjs:24:789)
    at $e (E:\Projects\frontend\blog\.yarn\releases\yarn-3.0.2.cjs:24:891)
    at ABe (E:\Projects\frontend\blog\.yarn\releases\yarn-3.0.2.cjs:31:1922)
    at Dc (E:\Projects\frontend\blog\.yarn\releases\yarn-3.0.2.cjs:31:4422)
    at gBe (E:\Projects\frontend\blog\.yarn\releases\yarn-3.0.2.cjs:31:6569)
    at Dq (E:\Projects\frontend\blog\.yarn\releases\yarn-3.0.2.cjs:32:260)
    at xq (E:\Projects\frontend\blog\.yarn\releases\yarn-3.0.2.cjs:32:481)
    at hBe (E:\Projects\frontend\blog\.yarn\releases\yarn-3.0.2.cjs:32:759)
    at twe (E:\Projects\frontend\blog\.yarn\releases\yarn-3.0.2.cjs:255:142)
    at Kr (E:\Projects\frontend\blog\.yarn\releases\yarn-3.0.2.cjs:255:490)

To reproduce

Follow the steps provide in the migration guide & then try to “install” the list of packages or “import” a plugin. And it throws the error mentioned above.

Environment

  System:
    OS: Windows 10 10.0.19043
    CPU: (2) x64 Intel(R) Pentium(R) CPU G3220 @ 3.00GHz
  Binaries:
    Node: 16.7.0 - ~\AppData\Local\Temp\xfs-0697d3cd\node.CMD
    Yarn: 3.0.2 - ~\AppData\Local\Temp\xfs-0697d3cd\yarn.CMD
    npm: 7.19.1 - C:\Program Files\nodejs\npm.CMD

Additional context

Screenshot attached for further reference:

[kahboom]

Just in case anyone else ends up with this same problem, this keeps happening to to me after merging in Dependabot PRs. The workaround is to delete the yarn.lock file that I did not modify myself (nor would), and run yarn install again. Just seems a bit odd considering there was definitely no merge conflict reported or I wouldn’t have even been able to merge the PR… strange times.

EDIT: Another, simpler way that doesn’t involve deleting the yarn.lock file, is to merge one PR, pull changes, run yarn install to regenerate the lock file, push again to kick off another Dependabot build. Rinse and repeat for each PR. 😅 At least for now until yarn v2 and v3 are supported by Dependabot.

[shishkin]

… this keeps happening to to me after merging in Dependabot PRs.

Apparently, Dependabot doesn’t support yarn v2 & v3.