Skip to content
This repository was archived by the owner on Aug 6, 2024. It is now read-only.
This repository was archived by the owner on Aug 6, 2024. It is now read-only.

Don't use yarn internally #413

Description

@dcousens

this issue was transferred from https://github.com/keystonejs/keystone, but GitHub didn't like how I went from discussion(there)->discussion(here)->issue(this)

Originally posted by RodrigoNovais May 4, 2023
I've run npm init keystone-app to setup a new environment and it's dependencies where installed with yarn without my consent.
Would be polite to ask the developers which manager they want to use.
I only have yarn installed in my machine cause I was obligated to use it in previours jobs and would like to avoid it as much as possible.
Since the dependencies where automatically installed via yarn I don't even know if the CLI can initiate a project in a setup with pure npm.

I don't think this is a matter of consent, as this is open source software - but we don't need to be using yarn specifically either, so it's something we could probably add support for if desired.

@RodrigoNovais pull requests are accepted 💛

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions