S3Service.Type resolves to internal S3Service$ which isn't exported, causing TS4058 declaration emit errors

[eikeon]

I'm trying to use the type S3Service.Type (@effect-aws/client-s3) and am running into the following issue:

S3Service.Type resolves to internal S3Service$ which isn't exported, causing TS4058 declaration emit errors.

Could you export S3Service$ (or an equivalent public type) so S3Service.Type can be used in emitted declarations?

Thank you!

[floydspace]

hi @eikeon could you please show a quick repro?

Adding S3Service.Type supposed to fix this issue actually

[eikeon]

I've worked around it a couple times now so perhaps more an issue on my end. Both use case involved needing more than one Tag / Layer to have more than one S3 client configured differently (source / destination talking to two different environments). This latest one is multiple region specific S3 clients at the same time.

I think I was trying to do something like:

export class MyS3Client extends Context.Tag("MyS3Client")<S3Service.Type, void>() {}

which for me results in

error TS4020: 'extends' clause of exported class 'MyS3Client' has or is using private name 'S3Service$'.

export class MyS3Client extends Context.Tag("MyS3Client")<S3Service.Type, void>() {}

This is the way I ended up allowing for more than one:

export type MyS3Client<T extends S3Type> = S3Service.Type & {
    [paprikaSubClientPhantom]?: T; // Phantom: ties T to the type without runtime presence (optional to avoid needing to set it)
};

Perhaps there's a better way to implement this use case. I hope this helps clarify what I was running into.

[floydspace]

That is solved in 2.0.0-beta.2