Importing this entry point configures WarpDrive to use a signals graph built on alien-signals for reactivity: on import it calls setupSignals with buildSignalConfig.
Add the import to the top of your application, before any other install import. If you have tests which do not invoke your app, add it to your test setup as well:
import '@warp-drive/alien-signals/install';The graph it configures composes other signals implementations into its own. A framework's install entry point imported after this one, such as @warp-drive/ember/install, adds that framework's signals to the graph instead of replacing it, so one store re-renders components in every framework on the page. Importing this entry point after another framework's install throws, since that framework's hooks are already configured by then.
Memos, such as the ones behind derived fields, always come from this graph, so they only recompute when a signal WarpDrive manages changes. A memo that reads state only a framework tracks, such as an Ember @tracked property, keeps returning its cached value when that state changes.
A library should do this only in its tests, not in its published code. To observe changes from outside WarpDrive, use the Watcher from @warp-drive/alien-signals/primitives.