Message type is not exposed

[matehuszarik]

Message type is not exposed

[nicholasgriffintn]

Well no, the use case of needing the Message type is not that great (we haven't been exporting it for about half a year).

I'm not sure that it's that big of an ask for the user to import it directly themselves honestly, it's not something we're ever going to modify.

This isn't a bug either btw, so I'm gonna change the labelling.

[nicholasgriffintn]

I'm not sure this is actually required, as you need to install sqs-client anyway, it's realistically not that different or better from doing this:

import { Message } from '@aws-sdk/client-sqs';

I'll have a think on it, we did used to do it, but that was when we were adjusting the type ourselves.

[matehuszarik]

I'm a bit confused because the @aws-sdk/client-sqs pkg is added to peerDependencies and dependencies too.
https://github.com/bbc/sqs-consumer/blob/main/package.json#L65

Because of this, I'm not required to install the pkg separately.

[nicholasgriffintn]

As of version 7 of npm, peer dependencies are also auto installed, but either way, you still need to install it yeah.

[matehuszarik]

As of version 7 of npm, peer dependencies are also auto installed

Exactly, so I don't have to add @aws-sdk/client-sqs to dependencies separately and can not import the Message type. This is the problem I'd like to solve.

IMO sqs-consumer should either enforce the installation of @aws-sdk/client-sqs or re-export the Message type.

[nicholasgriffintn]

This has sort of been done in #385 I'm not happy with it though due to the docs issues.

Thinking about the time I have available, I'm going to decide not to do this, if anyone would still like to do this, feel free to open a new pr with the documentation fixed.

[github-actions]

This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.