Skip to content

[compatibility]: npm 12 throws new error due to updated restrictions #605

Description

@eduardoRoth
Image

This error typically occurs in newer versions of npm (v12+) where pulling external dependencies directly from Git repositories has been locked down by default to prevent supply chain vulnerabilities.

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