Skip to content

[QUESTION](libnpmpublish) Migration from v3 to v4 #4248

@wesleytodd

Description

@wesleytodd

What / Why

Looks like the CHANGELOG.md was not updated when 4.x was released, and from reading the new source it looks like the signature changed and now expects the tarball pack do be done outside of this lib. Are there docs on a migration for folks using the v3 version? Additionally is there any way to leverage npm lib's to replicate the old behavior where starting from a directory and a package.json we can get the proper tarball (by proper I mean exactly like npm creates it) outside of the cli? Maybe libnpmpack?

Where

  • n/a

Who

References

  • n/a

Metadata

Metadata

Assignees

No one assigned

    Labels

    Needs Triageneeds review for next stepsws:libnpmpublishRelated to the libnpmpublish workspace.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions