effect-v4-imports

Standardize Effect v4 imports by enforcing specific module aliases like Array to A and Option to O, ensuring namespace-first helper module policies, and migrating deprecated package paths for cleaner codebases.

Migrate deprecated Effect v3 API imports by discouraging the use of deprecated v3 APIs and specific unstable modules, replacing them with stable Effect v4 module paths to ensure adherence to stable module policies.

Enforce A/O/P/R/S aliases for Effect modules during refactoring by applying standard import aliases such as mapping effect/Array to A, ensuring consistent namespace-first helper module imports across the codebase.

Yes, Effect v4 prefers dedicated namespace imports over root imports. This module policy guides developers to use specific namespace-first helper module imports to maintain import hygiene and codebase cleanliness.

Use namespace-first helper module imports in Effect v4 to satisfy requirements for cleaner codebases, enforce import hygiene, and ensure adherence to stable module policies during your TypeScript migration.