Capacitor plugin not found when calling from shared web code

Capacitor plugin not found when calling from shared web code

The goal is to run a Capacitor‑based app in web browsers and debug native builds without committing production credentials. The main uncertainty lies in how direct imports of native plugins in shared TypeScript code affect web execution. When a plugin that exists only on iOS or Android is imported and invoked on the web, the runtime throws a CapacitorError: Plugin not found exception, breaking the bundle. This behavior is documented in the Capacitor error handling section of the core API reference.

Unresolved decisions:

• Should shared web code abstract Capacitor plugins behind a platform‑specific interface with web mocks, or import them directly?
• What is the safest way to gate plugin usage so that web builds remain credential‑free while native builds retain full functionality?
• Is there an official Capacitor configuration that suppresses plugin errors on unsupported platforms?

Key questions to resolve:

1. Does importing a Capacitor plugin directly in shared code always result in a runtime error on web builds, or can it be mitigated with conditional checks?
2. What best‑practice patterns exist for mocking Capacitor plugins in credential‑free test environments?
3. Does Capacitor provide a documented mechanism to disable or stub plugins on non‑native platforms without code changes?