38 replies

Best Practices for Aliasing imports from `effect` and its Extensions

Are there any idiomatic / recommended aliases for Effect's imported modules? E.g. something like

import { Effect as E, ReadonlyArray as A } from 'effect';

import { Effect as E, ReadonlyArray as A } from 'effect';

And what about extension libraries like

@effect/schema

@effect/schema

? The Readme seems to suggest

import { Schema as S } from '@effect/schema`;

import { Schema as S } from '@effect/schema`;

And how would you reconcile that with some other candidates for the

alias, e.g. when doing

import { Stream, String, Struct } from 'effect'

import { Stream, String, Struct } from 'effect'

.

I guess this is all somewhat inspired by https://www.youtube.com/watch?v=V2jOP5resAE (for

fp-ts

fp-ts

@unsplash/ts-namespace-import-plugin

@unsplash/ts-namespace-import-plugin

in VS Code.