publish-on-npm
CommunityPublish Electron apps to npm with platform bins
Software Engineering#cross-platform#desktop app#release automation#electron#npm publish#optionalDependencies#launcher bin
Authorwebdevcody
Version1.0.0
Installs0
System Documentation
What problem does it solve?
Publishing an Electron desktop app to npm often results in broken installs, missing binaries, or users downloading the wrong artifacts across platforms and architectures.
Core Features & Use Cases
- Deterministic multi-phase release flow: runs an ordered workflow that prevents partial publishing mistakes by publishing sibling binaries before the root package.
- Per-OS/arch optionalDependencies launcher pattern: packages each platform build into a sibling npm package and pins exact versions from the root so installs resolve correctly.
- Builder detection with safety guardrails: auto-detects electron-builder vs electron-forge, refuses ambiguous setups, and blocks cross-compiling macOS from non-macOS hosts.
- Unpacked-artifact validation: verifies that builds produce unpacked application directories (not installers) before assembling the publishable npm packages.
Quick Start
Ask the skill to publish your Electron desktop app to the npm registry using the platform-specific sibling optionalDependencies launcher pattern.
Dependency Matrix
Required Modules
None requiredComponents
references
💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: publish-on-npm Download link: https://github.com/webdevcody/go-mailing-list/archive/main.zip#publish-on-npm Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.