Skip to content

Shouldn't alpine be a peer dependency? #2

@mtimofiiv

Description

@mtimofiiv

From NPM package.json docs:

[A peer dependency is when] you want to express the compatibility of your package with a host tool or library, while not necessarily doing a require of this host. This is usually referred to as a plugin. Notably, your module may be exposing a specific interface, expected and specified by the host documentation.

This seems to fit this template pretty well. Should alpinejs be specified as a peerDependency instead?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    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