list-npm-package-content

To list npm package contents before publishing, run a script that executes pnpm build and pnpm pack to generate a tarball, then enumerates included files with tar -tzf before removing the temporary archive.

npm publish workflows miss assets or include unexpected files when package.json files field, .npmignore, or .gitignore exclusions are misconfigured. Packing and listing the tarball contents diagnoses the exact inclusion behavior.

Yes, npm pack respects the files field allowlist, .npmignore and .gitignore exclusions, and always includes required metadata files. Generating a tarball and enumerating its contents reflects these exact packaging rules.

The best way to verify tarball contents for release troubleshooting is generating the actual publish tarball via pnpm pack, listing all packaged files with tar -tzf, and deleting the temporary tarball afterward.

Yes, you can use pnpm to debug missing or extra assets by running pnpm build followed by pnpm pack to create the tarball, then inspecting the enumerated file list to identify packaging rule discrepancies.

This local pack verification requires executing pnpm build and pnpm pack within the package directory, generating a temporary tarball file that is removed after enumeration, and depends on the local environment matching publish conditions.