Legacy Dependency Metadata Selector Syntax
These formats keep working without changes, but when a rule policy uses them the plugin emits a one-time runtime console warning encouraging migration to object-based selectors. When you are ready to migrate, the v6 to v7 migration guide covers the full transition, including the entity selector form.
Dependency metadata properties
module
Since v7, the module information is now reachable through the module sub-selector. The legacy form keeps working, but it should be migrated to use the to.module.source property instead.
| Deprecated | Replacement |
|---|---|
{ dependency: { module: "react" } } | { to: { module: { source: "react" } } } |
Migration guide
For step-by-step migration instructions and examples, see the v6 to v7 migration guide.
See Also
- Selectors — modern object-based and entity selector reference.
- Policies — where selectors are used in
from/to/dependency. - v6 to v7 Migration Guide — full migration instructions.