Guide npm package publishing with package.json configuration and provenance tracking.
npx skills add https://github.com/mcclowes/lea --skill npm-publishing
Please help me install this Agent Skill. Skill: npm-publishing Source: https://github.com/mcclowes/lea/tree/main/.claude/skills/npm-publishing Command: npx skills add https://github.com/mcclowes/lea --skill npm-publishing
Guidance for publishing npm packages with proper versioning, exports, and provenance to ensure safe, reproducible releases.
Prepare a package.json and perform a dry-run publish to verify configuration.
High-intent search queries and answers about installing and using this skill.
Semantic versioning for npm packages involves incrementing version numbers in package.json following major.minor.patch format based on changes, then using `npm publish` to release. Set version manually or use `npm version` to auto-increment and create git tags for trackable releases.
The exports field defines entry points for ESM and CommonJS consumers, replacing the main field. It ensures users import the correct module format and prevents access to internal files, enabling modern packaging with explicit public APIs and dual-module support.
Run `npm publish --dry-run` to simulate publication without uploading, validating package.json syntax, access permissions, and file inclusion. This catches configuration errors early and confirms your package meets npm registry requirements before actual release.
Npm provenance tracks the build environment and attestation of package origin for security. Enable it by publishing from trusted environments with `npm publish --provenance` to generate cryptographic evidence that proves package authenticity and reproducibility.
Yes, scoped packages use the `@scope/package-name` format in package.json. Configure `publishConfig.access` to 'public' for public scopes, then run `npm publish` with appropriate registry credentials and permissions for your organization scope.
oakossConfigure npm package.json exports, dual ESM/CJS builds, and publishing workflows.
tnezCreate and publish new npm package versions with changelog updates.
raphaelchristiAutomate npm package releases with changelog generation and GitHub publishing.
snhrmAutomate package updates across npm, yarn, pnpm, and bun.
