Skip to content

yarn.lock file does not get created in nearly all the cases  #53936

@SteveW94

Description

@SteveW94

Version

22.5.0

Platform

Windows 11 on my PC
Windows 10 Agent on CI
Ubuntu 22 Agent on CI

Subsystem

No response

What steps will reproduce the bug?

  • Use Node 22.5.0
  • Use a Project with Yarn 1.x
  • Perform "yarn" command.

=> Nearly all cases NO yarn.lock is created as expected.

Also important to note: The exact same steps on the exact same systems just worked fine on Node 22.4.1
Due to this we had to Pin Node to this last working version on all our pipelines etc. :/

How often does it reproduce? Is there a required condition?

Nearly always

What is the expected behavior? Why is that the expected behavior?

yarn.lock file gets created

What do you see instead?

No yarn.lock file gets created at all

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    duplicateIssues and PRs that are duplicates of other issues or PRs.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions