agentleFS
Cap-goCap-go/capgo-skills/skills/capacitor-plugin-upgrade-v5-to-v6/SKILL.md

capacitor-plugin-upgrade-v5-to-v6

Skill75 starsChanged 34 days agoMITView on GitHub

Upgrades a Capacitor plugin library from v5 to v6 using `npx @capacitor/plugin-migration-v5-to-v6@latest`, then the manual checklist - `@capacitor/*` dev deps to `latest-6`, `compileSdkVersion` replaced by `compileSdk`, compile/target SDK 34 defaults, AGP 8.2.1, Gradle 8.2.1, Kotlin 1.9.10, plus code changes - `addListener` in `definitions.ts` returns only `Promise<PluginListenerHandle>` (drop `& PluginListenerHandle`), remove `CAP_PLUGIN_METHOD(removeAllListeners, ...)` from the `.m` file, and optional experimental SPM support via `Package.swift`. Use when a plugin targets Capacitor 5 and must support 6. Do not use for app upgrades, other major versions, or non-Capacitor libraries.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    definitions.ts: every addListener overload must return only Promise<PluginListenerHandle>:

    line 61
  2. Very specific:

    Update web.ts and README/docgen output to match.

    line 71
  3. Very specific:

    iOS: delete CAP_PLUGIN_METHOD(removeAllListeners, CAPPluginReturnPromise).

    line 72
  4. Distinctive:

    Run the example app on both platforms.

    line 88

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Capacitor Plugin Upgrade v5 to v6

Move a plugin library to Capacitor 6. Source of truth: https://capacitorjs.com/docs/updating/plugins/6-0

When to Use

  • Snapshot shows @capacitor/core 5.x and the plugin must work in Capacitor 6 apps.
  • definitions.ts still declares Promise<PluginListenerHandle> & PluginListenerHandle.
  • The user wants to add SPM support while moving to 6.

Do not use:

  • Upgrading an app -> capacitor-app-upgrade-v5-to-v6.
  • Plugin on 4.x -> capacitor-plugin-upgrade-v4-to-v5 first; on 6.x -> capacitor-plugin-upgrade-v6-to-v7. Multi-hop -> capacitor-plugin-upgrades.
  • Full SPM conversion details -> capacitor-plugin-spm-support.

Live Project Snapshot

Plugin and Capacitor package snapshot: !node -e "const fs=require('fs');if(!fs.existsSync('package.json'))process.exit(0);const pkg=JSON.parse(fs.readFileSync('package.json','utf8'));const out=['package.name='+(pkg.name||''),'package.version='+(pkg.version||'')];for(const section of ['peerDependencies','dependencies','devDependencies']){for(const [name,version] of Object.entries(pkg[section]||{})){if(name.startsWith('@capacitor/'))out.push(section+'.'+name+'='+version)}}console.log(out.join('\n'))"

Example and native project paths: !find . -maxdepth 3 \( -path './example-app' -o -path './ios' -o -path './android' \)

References

FileLoad when
references/android.mdApplying Gradle or Kotlin changes by hand

Preflight

ToolMinimum
Node.js18+
Xcode15.0+
Java17
AGP / Gradle8.2.1 / 8.2.1
Android SDK defaultscompileSdk 34, targetSdk 34, minSdk 22
iOS deployment target13.0 (unchanged)

Procedure

  1. Confirm 5.x and a clean tree.
  2. From the plugin root:

    npx @capacitor/plugin-migration-v5-to-v6@latest

    Review git diff.

  3. Finish manually (references/android.md): dev deps to latest-6, peer @capacitor/core to ^6.0.0, compileSdk (not compileSdkVersion) default 34, targetSdkVersion default 34, AGP 8.2.1, Gradle 8.2.1, Kotlin 1.9.10.
  4. definitions.ts: every addListener overload must return only Promise<PluginListenerHandle>:

      addListener(
        eventName: 'resume',
        listenerFunc: () => void,
    - ): Promise<PluginListenerHandle> & PluginListenerHandle;
    + ): Promise<PluginListenerHandle>;

    Update web.ts and README/docgen output to match. This is a breaking change for consumers who used the sync handle.

  5. iOS: delete CAP_PLUGIN_METHOD(removeAllListeners, CAPPluginReturnPromise); from the plugin .m file. It is now built in for all plugins.
  6. Optional SPM: Capacitor 6 adds experimental SPM. Ask the user if they want it now; if yes follow capacitor-plugin-spm-support (adds Package.swift, CAPBridgedPlugin conformance in Swift).
  7. Upgrade the example app via capacitor-app-upgrade-v5-to-v6, bump the plugin major, note "Requires Capacitor 6".

Verification

grep -n "\"@capacitor/" package.json                               # 6.x
grep -rn "& PluginListenerHandle" src/                             # expect none
grep -rn "removeAllListeners" ios/ --include=*.m 2>/dev/null       # expect none
grep -n "compileSdkVersion project\|gradle:8.2.1" android/build.gradle   # compileSdk + 8.2.1
grep -n "distributionUrl" android/gradle/wrapper/gradle-wrapper.properties   # gradle-8.2.1
npm run build
npm run verify        # if the repo has the template verify scripts

Run the example app on both platforms; add and remove each listener.

Error Handling

ErrorFix
TS: Property 'remove' does not exist on type 'Promise<PluginListenerHandle>' in example/testsawait the addListener call.
AGP deprecation warning on compileSdkVersionUse compileSdk.
removeAllListeners still listed in the .m fileRemove the CAP_PLUGIN_METHOD line (step 5); the method is built in.
Example app ERESOLVE on @capacitor/corePeer range still ^5; set ^6.0.0.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.