Removing a package can affect components that reuse its styles, render its fields
or offer them as optional capabilities. Inspect that graph before uninstalling it:
This command does not remove files, data or Composer packages. It returns a failure
status when registered external components depend on that package. Its scope is
the installed definition graph; it does not scan application databases.
Supply your saved schemas to check the impact on persisted configuration too:
Include inactive schemas in that inventory: their saved values may still need the
package later. Each call accepts up to 256 typed definitions with unique slugs;
inspect all batches across all relevant records before removal. Reports contain
schema identities and format versions, not labels, settings or saved values.
readyWithinSuppliedScope describes only the graph and schemas passed to that
call. Your application remains responsible for complete record inventories,
explicit migrations, backups and retaining published releases used by existing
pages. Saved snapshots can be retained without the package using
FamilyValueSnapshotCodec; normal saves must not silently discard them.
Continue reading
Extension guides · Definition and registration reference Last modified on October 16, 2026