Skip to content

Extension should recognize other package managers than npm #3854

@wojtekmaj

Description

@wojtekmaj

Existence of any other package manager (recognized by packageManager in package.json, presence of a certain lockfile) is simply ignored and the extension still tries to configure everything, particularly tasks.json, using npm. This leads to creating setups that may simply not work.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions