The reasoning for this approach is the an assumption that a lot of projects already have ngrx in place and adding another lib or creating your own logic is additional code that might not be needed ( if it is than yea , build a different message service )

The way I see the actions is like any basic message queue service, something the ngrx team actually talked about recently, keeping the store completely decoupled from the application. So that means that it lies in the global scope of your application so there is no reason for now to anticipate the issue your are bringing up.

I appreciate your comment and hope that you do find this useful 😇