Verify the packed package
Catch missing files, exports, and CLI requirements before you publish, and know what still needs the app test.Run the package check
bashnpx astryx integration verify
integration verify runs npm pack, including lifecycle scripts, unpacks the .tgz file into a temporary app without installing its dependencies, and checks the unpacked integration. It publishes nothing and removes the .tgz file and the temporary app.
- It validates the manifest, every template doc, its source file, and the templates directory.
- It checks that the manifest and every template file are in the
.tgzfile. - It checks that each packed template keeps the same id, type,
name, andreplacesas your working copy. It does not compare template source or other doc fields. - It resolves each template through its public package path in the unpacked package.
- It checks that the resolved template module has a default export.
- It checks the CLI peer that features such as template replacement require.
Each failure prints a [fail] line with its message; add --json to see each issue code. astryx docs cli/integrations/help/troubleshooting lists the common messages and their fixes. Fix every error, and review every warning before publishing.
Know what it does not prove
integration verify checks the packed templates and their public entrypoints. It does not copy a template into an app or run a browser build, so it cannot show the following.
- Whether a relative helper or stylesheet survives the copy.
- Whether the copied file type-checks in every supported app toolchain.
- Whether package-owned CSS, fonts, icons, images, or media load in a browser.
- Whether layout, color modes, keyboard and pointer input, and real content work.
- Whether a template id collides with Core, or whether a
replacestarget exists. Runnpx astryx doctor integration templatesfor those. - How the template scores on quality.