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

capacitor-plugin-upgrade-v4-to-v5

Skill75 starsChanged 34 days agoMITView on GitHub

Upgrades a Capacitor plugin library from v4 to v5 using `npx @capacitor/plugin-migration-v4-to-v5@latest`, then the manual checklist - `@capacitor/*` dev deps to `latest-5`, compile/target SDK 33 defaults, AGP 8.0.0, Gradle 8.0.2, `namespace` in build.gradle instead of manifest `package`, Java 17, Jetifier removal, Kotlin 1.8.20 with `kotlin-stdlib`, plus code changes - `CAPBridgedPlugin` requirements moved to instance level (`pluginId` -> `identifier`, `pluginMethods` typed `[CAPPluginMethod]`) and Android `PluginCall.getObject()` / `getArray()` may return null. Use when a plugin's peer dependency is Capacitor 4 and it must support 5, or apps on v5 fail with "Namespace not specified" in the plugin module. 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

3 rules. About 0 are common, 1 is distinctive, and 2 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.

  • 2

    Very specific

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

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

    iOS code: if the plugin conforms to CAPBridgedPlugin manually (no CAP_PLUGIN macro), move requirements to instance level, rename pluginId …

    line 62
  2. Very specific:

    Update the example app (if present) to Capacitor 5 via capacitor-app-upgrade-v4-to-v5.

    line 64
  3. Distinctive:

    Run the example app on both platforms and exercise every method.

    line 81

≈ “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 v4 to v5

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

When to Use

  • Snapshot shows @capacitor/core 4.x in peer/dev deps and the plugin must work in Capacitor 5 apps.
  • A Capacitor 5 app fails building this plugin with Namespace not specified or Java 17 errors.
  • The plugin manually conforms to CAPBridgedPlugin or calls getObject() / getArray().

Do not use:

  • Upgrading an app -> capacitor-app-upgrade-v4-to-v5.
  • Plugin already on 5 -> capacitor-plugin-upgrade-v5-to-v6. Multi-hop -> capacitor-plugin-upgrades.

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, manifest, Java or Kotlin changes by hand

Preflight

ToolMinimum
Node.js16+
Xcode14.1+
Java17 (AGP 8)
AGP / Gradle8.0.0 / 8.0.2
Android SDK defaultscompileSdk 33, targetSdk 33, minSdk 22
iOS deployment target13.0 (unchanged)

Procedure

  1. Confirm the plugin is on 4.x from the snapshot and the tree is clean (git status).
  2. From the plugin root run:

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

    It edits package.json, android/build.gradle, the wrapper, gradle.properties, and the manifest. Review git diff.

  3. Finish manually anything not applied (references/android.md):
    • @capacitor/cli, core, android, ios dev deps to latest-5; peer @capacitor/core to ^5.0.0.
    • SDK defaults 33, AGP 8.0.0, Gradle 8.0.2, namespace in android {} and no package= in the manifest, Java 17, Jetifier removed, Kotlin 1.8.20 with kotlin-stdlib.
  4. iOS code: if the plugin conforms to CAPBridgedPlugin manually (no CAP_PLUGIN macro), move requirements to instance level, rename pluginId to identifier, type pluginMethods as [CAPPluginMethod], and drop getMethod(_:). Macro-based plugins need no change.
  5. Android code: call.getObject(key) and call.getArray(key) can now return null. Add null checks and call.reject(...) with a clear message when required.
  6. Update the example app (if present) to Capacitor 5 via capacitor-app-upgrade-v4-to-v5.
  7. Bump the plugin major version and note "Requires Capacitor 5" in the changelog/README.

Verification

grep -n "\"@capacitor/" package.json                         # 5.x everywhere
grep -n "package=" android/src/main/AndroidManifest.xml      # expect none
grep -n "namespace\|VERSION_17\|gradle:8.0.0" android/build.gradle
grep -rn "kotlin-stdlib-jdk" android/build.gradle            # expect none
grep -rn "getObject(\|getArray(" android/src/main/           # each result null-checked
grep -rn "pluginId\b" ios/                                   # only CAPPlugin usages remain
npm run build
npm run verify        # plugin template script: verify:ios + verify:android + verify:web, if present
cd android && ./gradlew clean build test

Run the example app on both platforms and exercise every method.

Error Handling

ErrorFix
Namespace not specifiedAdd namespace "<package>" to android {} in the plugin build.gradle.
Android Gradle plugin requires Java 17 to runSwitch the Gradle JDK to 17.
NullPointerException from getObject/getArrayAdd null checks (step 5).
Swift: type does not conform to protocol CAPBridgedPluginUse instance-level identifier, jsName, pluginMethods, or switch to the macro.
Duplicate class ... kotlin-stdlib-jdk8Replace kotlin-stdlib-jdk7/jdk8 with kotlin-stdlib.

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.