StoreAction
Actions the Store itself reduces, rather than routing to a module.
A module action names the module that handles it and is reduced by that module's reducer. A store action operates on the whole state tree, so the store applies it directly.
Store actions travel the same ordered dispatch pipeline as every other action, so they are serialised against module dispatches rather than racing them. They do not pass through the middleware chain: Middleware is defined in terms of one module's resulting state, and a store action has no single module. A consequence worth relying on is that a store action triggers no middleware-driven work, which is why a projection fires no navigation lifecycle hooks.