Circular dependency when importing types from other features

[SevenOutman]

It's a common scenario when we import type definitions from other features, especially definitions for resources (fetched from APIs). If we expose everything from only the index.ts to other features, it's easy to encounter circular dependency.

For example, if I'm writing a components in teams feature where type User from users feature is used:

// teams/components/MyComponent.ts
import type { User } from '@/features/users';

That will cause components from users to also be loaded because I re-exported them from users/index.ts.

// users/index.ts
export * from './types';
export * from './components';

Meanwhile I have a component in users feature that imports type Team from teams feature:

// users/component/MyComponent.ts
import type { Team } from '@/features/teams';

Now my teams/components/MyComponent.ts and users/component/MyComponent.ts forms a circular dependency.

My solution is to import types from other features directly from their ./types.ts, which means that ./index.ts is not reguarded as the only port of a feature.

Same problem exists with importing APIs from other features. Any idea?