Skip to content

deno pack in project with a package.json file produces tarball with two package.json files #36387

Description

@kcastellino

Version: Deno 2.9.4 (stable, release, x86_64-pc-windows-msvc)
Engine: v8 15.0.245.2-rusty
TSC: typescript 6.0.3

Running deno pack in a Deno project which already includes a package.json file will produce a tarball which includes both the package.json file generated by deno pack, as well as the package.json file included in the project folder.

I presume this stems from #35331 (shipped in Deno 2.9.0), which broadened the set of included files. Nevertheless, the produced tarball has two files with the same name and different contents.

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