nextnc / nestjs-ses Goto Github PK

Is there any possibility to use templates using Twing or another engine?

Hello,
It generates an error ‘SignatureDoesNotMatch’ Probably due to the 4th version of AWS authentification.

In my email body, I've content which has brackets. ex: Welcome user(role).
If I remove brackets () it works fine else it gives me error "SignatureDoesNotMatch".
Also I tried same with square brackets [] it worked.

Is there a way to add attachments in email..as I do not see any options in EmailOptions for doing same.

Kindly assist!!

I installed your package, but the import statement gives error "Cannot find module '@nextm/nestjs-ses'.ts(2307)". Whereas I verified the node_modules directory, it is present.

Also one query, while importing you are using name as NestjsSesModule, but while configuring it you are using SesModule why so?

Its also missing the index.js file while downloading it from npm.

Please see aheckmann/node-ses#68 for necessity.

On installing I get the following error:

npm ERR! Found: @nestjs/[email protected]
npm ERR! node_modules/@nestjs/common
npm ERR!   @nestjs/common@"^9.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @nestjs/common@"^7.0.7" from @nextnm/[email protected]
npm ERR! node_modules/@nextnm/nestjs-ses
npm ERR!   @nextnm/nestjs-ses@"*" from the root project

Looks like the nestjs/common version needs to be bumped.

Hello,

I have noticed that the module currently does not have a forRootAsync method to obtain AWS credentials using ConfigModule. Currently, only the forRoot method can be used in the import statement.

It would be helpful to add a forRootAsync method, similar to what is available in TypeORM, to allow for the configuration of AWS credentials via a ConfigService.

For example:

        NestJsSesModule.forRootAsync({
            imports: [ConfigModule],
            inject: [ConfigService],
            useFactory: (configService: ConfigService) => ({
                accessKeyId: configService.get("AWS_ACCESS_KEY_ID"),
                secretAccessKey: configService.get("AWS_SECRET_ACCESS_KEY"),
                region: configService.get("AWS_REGION")
            })
        }),

Thank you for considering this enhancement.

Is this repo maintained any longer? It seems like issues and pull requests are not being responded to.