Turborepo cant unmarshall yarn lock generated under (crlf) windows on linux (lf) about turbo

[Yuyz0112]

Also run into this issue, in my case, change the yarn.lock file from CRLF to LF fixes the problem.

[amlcodes]

running into this in a dockerfile

[TheKnarf]

This is still a problem, just hit it today and was not able to find a solution. Ended up removing turbo prune from my Dockerfile as it didn't work.

Can this issue be reopened?

[jaredpalmer]

Thanks for the write up. Investigating

[jaredpalmer]

@Floffah will give it a shot

[weyert]

Reproducible steps for turborepo-repository:

brew install dos2unix
unix2dos yarn.lock
yarn build

Runing yarn build now gives the following response on maCOS:

❯ yarn build                   
yarn run v1.22.17
$ ./turbow.sh run build --scope=docs
unmarshal
 ERROR  yarn.lock: yaml: line 6: mapping values are not allowed in this context
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

[bel7aG]

yarn -O install

[jaredpalmer]

@Yuyz0112 is the fix here as simple as add \r\n in lockfile parsing?

[Floffah]

@Yuyz0112 is the fix here as simple as add \r\n in lockfile parsing?

if you push a version (even just as a commit not a publish) i could try it and see if it fixes my problem because its likely the same

[Yuyz0112]

@jaredpalmer

Looks like the CRLF has a ^M after each line, so it breaks the first YAML field. I'm using vscode's toolbar to convert CRLF to LF.

[weyert]

@Floffah I am trying to assist in solve this problem. Do I understand you correctly that the problem is reproducible in your earlier mentioned repo? https://github.com/floffah/collaborated

[Floffah]

@Floffah I am trying to assist in solve this problem. Do I understand you correctly that the problem is reproducible in your earlier mentioned repo? https://github.com/floffah/collaborated

Yes, the vercel deployments have failed with it for the past few commits

The problem may be to do with crlf in development being deployed to a lf based platform with the same crlf lock file

[weyert]

@Floffah I have been able to reproduce it locally, I am getting the following:

❯ yarn build:simple                                                                                             
yarn run v1.22.17
$ yarn turbo run build --only
$ /Users/weyert/Development/Projects/Opensource/turborepo/repros/collaborated/node_modules/.bin/turbo run build --only
unmarshal
 ERROR  yarn.lock: yaml: line 6: mapping values are not allowed in this context
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Working on a fix now :)

[jaredpalmer]

What is the suggested workaround here?

[weyert]

I was able to get it mostly working by switching to #13#10 for splitting lines but then I went down a rabbit hole of using Scanner instead. And then I got stuck on which data you exactly need from the lock file for the tool

[borislemke]

Running into the same issue. Our original yarn.lock file is generated by yarn version 3.2.1, but when creating a prune of one of the packages, the resulting lock file is version 1.

Original file:

# This file is generated by running "yarn install" inside your project.
# Manual changes might be lost - proceed with caution!

__metadata:
  version: 6
  cacheKey: 8

by prune:

# THIS IS AN AUTOGENERATED FILE. DO NOT EDIT THIS FILE DIRECTLY.
# yarn lockfile v1
...

yarn fails

$ yarn        
Syntax Error: Expected "\n", "\r", or "\r\n" but ":" found.

Steps taken:

yarn --version
# 3.2.1
npx turbo prune --scope=@some/package
cd out
yarn install # fails

[nathanhammond]

Berry (Yarn 3) support is "best effort" at this time. Watch for PRs from @chris-olszewski.