shared/eager-without-singleton
- Category: performance
- Default severity: warning
Issue
An eager non-singleton can add copies to initial chunks without guaranteeing reuse.
How to fix it
Set singleton: true on that shared package when it holds framework state, or drop eager: true so the runtime can load a single copy.
Suppress or retarget with rules["shared/eager-without-singleton"] set to "off" or a severity, see Suppressions and allowlists.