core/import-boundaries

Components may import actions, selectors, types, and the initialized Store instance, but never saga files or redux-saga effects. Services dispatch through the Store instance, while only sagas may import other sagas and typed-redux-saga effects.

A component can import action creators from slice files, selectors from selector modules, and TypeScript types. It must not import saga source, reducer internals, store setup modules, or collection utilities directly.

No. typed-redux-saga effects like call, put, and takeEvery only have meaning inside saga generators. Importing them in components bloats the bundle and can drag saga middleware into client code; dispatch an action through the Store instead.

Importing saga source into a component pulls side-effect code into the client bundle and invites direct generator invocation, which bypasses the Store.runSaga lifecycle. The fix is to dispatch the triggering action and let the saga middleware handle it.

Services should dispatch through the app's initialized Store instance captured outside callbacks, or receive a Store or dispatch function as an explicit parameter. Hidden module-level dispatch helpers create an unreviewable second boundary even when imports type-check.