l-experimental-release

Publish packages to npm under the experimental tag using changeset snapshot commands.

3.0k|186|Updated Oct 1, 2020
One-click install
npx skills add https://github.com/lowdefy/lowdefy --skill l-experimental-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: l-experimental-release
Source: https://github.com/lowdefy/lowdefy/tree/main/.claude/skills/l-experimental-release
Command: npx skills add https://github.com/lowdefy/lowdefy --skill l-experimental-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of publishing experimental or preview releases of packages to npm, ensuring that the latest development versions are available for testing without affecting stable releases.

Core Features & Use Cases

  • Snapshot Versioning: Publishes packages with snapshot versions (e.g., 0.0.0-experimental-{hash}).
  • Tagging: Uses the experimental tag on npm for easy installation of preview versions.
  • Automated Build & Publish: Handles versioning, building, and publishing in a single, streamlined process.
  • Use Case: A developer wants to test a new feature in a library before a formal release. They use this Skill to publish the current branch's state as an experimental npm package, allowing them to install and test it in a separate project.

Quick Start

Use the l-experimental-release skill to publish the current branch to npm under the experimental tag.

Frequently Asked Questions about l-experimental-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish an experimental npm release from a feature branch?

To publish an experimental npm release, the Skill versions packages using changeset snapshot tags and publishes them to npm under the `experimental` tag, allowing feature branch testing without affecting stable releases.

What is the best way to share an npm package preview for testing before a formal release?

The best way to share a package preview is using changeset version --snapshot to generate a version like `0.0.0-experimental-{hash}`, then publishing with the `experimental` tag so consumers can install the preview build.

Does publishing an experimental npm release modify my git history?

No, publishing an experimental npm release does not modify git history. The Skill discards version changes after publishing to maintain a clean git state, leaving your current branch uncommitted changes intact.

Can I use changesets to publish snapshot versions without affecting the latest npm tag?

Yes, you can use changesets to publish snapshot versions without affecting the latest tag. The Skill publishes with `--tag experimental --no-git-checks`, ensuring the `latest` npm dist-tag remains untouched.

What pre-flight checks are needed before publishing an experimental npm package?

Before publishing an experimental npm package, pre-flight checks verify npm login, detect uncommitted changes, and confirm existing changesets. The Skill then prompts for confirmation before versioning and publishing.

Why use an experimental tag instead of latest when publishing npm snapshot releases?

Using an experimental tag instead of latest ensures that snapshot releases do not automatically update production dependencies. Consumers must explicitly target the `experimental` tag to install the preview version.