Skip to content

[BUG] npm publish with <tarball> parameter recreates tarball #4533

@gstamac

Description

@gstamac

Is there an existing issue for this?

  • I have searched the existing issues

This issue exists in the latest npm version

  • I am using the latest npm

Current Behavior

If I create a tarball with npm pack and then call npm publish my-package.tgz it recreates the tarball and includes my-package.tgz in that tarball. This started happening since v8.5.0 (also tried v8.5.3). Before v8.5.0 npm publish my-package.tgz would simply publish my-package.tgz as is.

Expected Behavior

Publish tarball as is.

Steps To Reproduce

  1. Windows and Linux (same behaviour locally, gitlab CI and github CI)
  2. Default config
  3. Run 'npm pack' and 'npm publish my-package.tgz`
  4. See the published package includes my-package.tgz

Environment

  • npm: 8.5.3
  • Node.js: v16.13.2
  • OS Name: Windows 10 and Linux (pipeline)
  • System Model Name:
  • npm config:
; "user" config from ...

//registry.npmjs.org/:_authToken = (protected)

; node bin location = C:\Program Files\nodejs\node.exe
; cwd = C:\Work\GlobaliD\atlas\packages\atlas-common
; HOME = ...

Metadata

Metadata

Assignees

No one assigned

    Labels

    Bugthing that needs fixingPriority 2secondary priority issueRelease 8.xwork is associated with a specific npm 8 release

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions