Skip to content

Publishing fails if package doesn't exist yet #16

Closed
@rikoe

Description

@rikoe

I get the following error when first running my build for my package.

npm ERR! 404 '@scope/package' is not in the npm registry.

The version check seems to fail if the package doesn't exist yet.

I haven't tried this yet, but I can probably disable the version check, publish, and then re-enable the version check, but this would require 3 commits!

Ideally the version check should only affect the publication of the package if the package is already present.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions