dbt-tools-web-pack-npx-smoke

To smoke-test an npm package tarball with npx without publishing, pack the package into a tarball and execute the CLI via npx against the artifact. This validates binary exposure and dependency rewrites before actual npm distribution.

A web package CLI might fail during npx execution after packing due to incorrect bin or dist-serve layouts. Running a Verdaccio-based smoke test validates the tarball packaging and catches dependency rewrite issues before release.

A Verdaccio-based smoke test for npm tarball packaging is a local workflow that builds, publishes, packs, and validates a package artifact against a private registry. It verifies binary exposure and dependency rewrites without touching the public npm registry.

Yes, you need pnpm and Node installed in your repository environment to pack and smoke-test the web package CLI. The workflow requires running from the repository root to correctly execute the Verdaccio-based validation.

Yes, you can validate the bin and dist-serve layout of a package before npm publish by creating a tarball and running a smoke test. This pre-release check identifies packaging failures and verifies CLI distribution quality in CI.

The best way to verify npm distribution quality for a CLI package in CI is running a Verdaccio-based smoke workflow. It packs the package into a tarball and executes the CLI via npx to ensure binary exposure and dependency rewrites function correctly.