[ Package conformance ]
Analytics · >=55.0.0
expo-insights
package-local wrapper registers only the ExpoInsights native module; upstream public JS is an empty default export.95%
API coverage
No visual conformance cases have been published for this package yet. The registry summary below describes what the compat layer implements.
Working (1)
default export is the upstream empty object; ExpoInsights native module name resolves after importing expo-insights so inlined expo-modules-core bundles do not fall through to the permissive proxy
Missing (1)
native lifecycle telemetry delivery to i.expo.dev is intentionally absent in sootsim