You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(android): per-plugin build options reaching the plugin gradle build
A plugin's `android.plugins.<name>` entry already reaches `buildAar`; this
makes it reach the gradle build itself, and adds `abiFilters` as the first
option that does:
```js
android: {
plugins: {
"@foo/plugin-x": { abiFilters: ["arm64-v8a"] },
},
}
```
Nothing here is specific to `abiFilters`. What a plugin has native code for
does not depend on what is plugged in, so the list wins over the ABIs
`--filter-plugins-devices-arch` derives from the connected devices and applies
whether or not that flag is set; an empty list passes nothing, opting a single
plugin out of the narrowing. Every other key of the entry reaches the build as
it is written.
The plugin build data now records the options gradle was asked for, under a
single `__buildOptions` entry rather than the `abiFilters`-specific one, since
the plugin sources do not change when an option does: any per-plugin option
added later takes part in the rebuild decision by being listed there. Options
that only change the artifact's name, such as `aarSuffix`, produce a different
file rather than a stale one and stay out of it.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
0 commit comments