Skip to content

yarn.lock vs. package-lock.json #75

Closed
@Trott

Description

@Trott

This has two competing lock files. Which one is the one to use? README seems to suggest that it's yarn.lock but it's 3 months older than the package-lock.json, so that suggests that maybe the package-lock.json is the one to use?

Activity

mprobst

mprobst commented on Apr 11, 2022

@mprobst
Contributor

I think we're using npm ci, and thus package-lock.json.

https://github.com/angular/clang-format/blob/master/.github/workflows/node.js.yml

Care to send a PR to update the docs and delete yarn.lock?

added a commit that references this issue on Apr 11, 2022
Trott

Trott commented on Apr 11, 2022

@Trott
ContributorAuthor

Care to send a PR to update the docs and delete yarn.lock?

#76

No change to the docs. It turns out that the mentions of yarn were for end users who want to add clang-format to an existing project, not developers looking to install/debug the clang-format code itself.

added a commit that references this issue on Apr 11, 2022
mprobst

mprobst commented on Apr 11, 2022

@mprobst
Contributor

Thanks for the fix @Trott !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      Participants

      @mprobst@Trott

      Issue actions

        yarn.lock vs. package-lock.json · Issue #75 · angular/clang-format