A library for generating native app code from JavaScript config through Expo config plugins
{
"context": "Evaluates whether the solution uses @expo/config-plugins to wire a reusable iOS config plugin. Checks Info.plist and entitlements updates for URL schemes, transport security exceptions, associated domains, and keychain access groups.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Plugin shape",
"description": "Exports the helper as a @expo/config-plugins ConfigPlugin (or via createRunOncePlugin/createInfoPlistPlugin) so it participates in the mod pipeline instead of acting as a plain function.",
"max_score": 20
},
{
"name": "Info mod hook",
"description": "Uses withInfoPlist to mutate CFBundleURLTypes and NSAppTransportSecurity inside the provided modResults rather than reading/writing the plist file manually.",
"max_score": 25
},
{
"name": "Scheme helper",
"description": "Adds and deduplicates the provided URL scheme with IOSConfig.Scheme.appendScheme or setSchemesInPlist instead of crafting CFBundleURLTypes entries by hand.",
"max_score": 20
},
{
"name": "Entitlements hook",
"description": "Routes entitlement updates through withEntitlementsPlist so modifications occur on the parsed entitlements plist within the mod system.",
"max_score": 20
},
{
"name": "Entitlement helpers",
"description": "Populates associated domains and keychain-access-groups using IOSConfig.Entitlements helpers (setAssociatedDomains and/or setCustomEntitlement) to merge new entries with existing values.",
"max_score": 15
}
]
}tessl i tessl/npm-expo--config-plugins@11.0.0docs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10