capacitor-platforms

Add and configure Capawesome Electron and Tauri desktop platforms for Capacitor apps.

1|Updated Aug 25, 2026
One-click install
npx skills add https://github.com/involvex/ionic-everywhere --skill capacitor-platforms-involvex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: capacitor-platforms
Source: https://github.com/involvex/ionic-everywhere/tree/main/.agents/skills/capacitor-platforms
Command: npx skills add https://github.com/involvex/ionic-everywhere --skill capacitor-platforms-involvex

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @capawesome/capacitor-electron, @capawesome/capacitor-tauri, and includes references (resource) components.

What problem does it solve? Bringing a Capacitor web app to macOS, Windows, and Linux requires choosing between Electron and Tauri, wiring up platform scaffolds, and navigating plugin compatibility differences. This Skill guides an agent through that entire desktop-platform workflow with the Capawesome platform packages. ## Core Features & Use Cases - Platform Selection Guidance: Compares @capawesome/capacitor-electron and @capawesome/capacitor-tauri on plugin reuse, binary size, OTA updates, and toolchain requirements to pick the right target. - Install, Sync, and Run Workflows: Covers cap add, cap sync, cap run, live reload via server.url, deep links, and packaging with electron-builder or tauri build. - Plugin Compatibility Checks: Explains Electron plugin implementations with web fallback and Tauri's built-in/curated/web-fallback tier model so unsupported plugins are caught early. - Use Case: A team with an existing Ionic/Capacitor app wants a Windows and macOS desktop build; the agent detects their plugins, recommends Electron for native plugin reuse, scaffolds the platform, and packages installers. ## Quick Start Add the Capawesome Electron desktop platform to my Capacitor app and show me how to run and package it.

Frequently Asked Questions about capacitor-platforms

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

FAQPage Schema
How do I add Electron to a Capacitor app?

Install @capawesome/capacitor-electron, run npx cap add @capawesome/capacitor-electron, then install dependencies inside the electron directory. Add a postinstall script in the root package.json so Electron dependencies stay in sync with the main app.

Capacitor Electron vs Tauri: which desktop platform should I choose?

Choose Electron for Capacitor plugin reuse with native Node implementations, web-bundle OTA updates, and a single bundled Chromium. Choose Tauri for binaries around 3-10 MB, lower memory use, and a deny-by-default Rust security model.

Does @capawesome/capacitor-tauri support all Capacitor plugins?

No. Tauri supports built-in plugins like @capacitor/app, curated shims backed by tauri-plugin crates such as Filesystem and Preferences, and any plugin with a web implementation. Plugins needing other native functionality require bespoke Rust code or the Electron platform instead.

Why does npx cap sync electron do nothing?

The Capacitor CLI requires the full package name, so a bare npx cap sync electron or tauri silently does nothing. Use npx cap sync @capawesome/capacitor-electron or npx cap sync @capawesome/capacitor-tauri instead.

Can I use live reload with Capacitor desktop platforms?

Yes. Set server.url in the Capacitor config to your dev server address, then run the platform with npx cap run. Electron applies a dev-only CSP relaxation and reconnects automatically; Tauri launches tauri dev with full HMR.

What are the limitations of the Capacitor Tauri platform?

Tauri has no Node runtime so arbitrary Capacitor plugins cannot be reused, it relies on three different system webviews across operating systems, web assets are compiled into the binary so only full binary updates are possible, and a Rust toolchain is required for development and CI.