samverschueren/generator-aws-lambda

Scaffold out an AWS Lambda module.

generator-aws-lambda

Scaffold out an AWS Lambda microservice with bragg.

Installation

$ npm install -g generator-aws-lambda

Usage

With Yeoman.

$ yo aws-lambda

License

MIT © Sam Verschueren

generator-aws-lambda's Issues

Write tests

Add possibility to add keywords

I couldn't add a list of strings in the package.json file with the template possibilities.

Outdated dependencies in generator

After running the generator and building the lambda, there are several issues which prevent npm build to create a deployment package.

Following packages needs to be updated due to ava:

• typescript
• @types/node

The test package has a typescript error as well.

add babel option

Scaffold out a project with babel of this option was chosen.

Add option for invoking other lambda functions

If the question is answered positive, the aws-lambda-invoke package should be added.

Add option for tests

If the question is answered positive, everything should be added for easy test writing.

Refactor zip task

The zip task is not working properly anymore. Since npm@3, all the packages are deduplicated. This makes ignoring the devDependencies not really intelligent. Better would be to create a temp directory, copy all the js files + license + package.json and run npm install --production. Zip everything inside that temp directory.

Provide list of extra libraries

It would be nice if it was possible to provide a list of extra libraries that should be installed.

Remove aws-sdk

aws-sdk is globally available and shouldn't zipped. The module is > 3 MB so this will reduce the size of the uploaded code.

Issue when installing one of the extra packages

For instance, when selecting dynongo in the last question, the package.json file looks like this.

  "dependencies": {
    "bragg": "^0.2.0",
    "bragg-router": "^0.2.0",
    "bragg-env": "^0.2.0",
    "bragg-route-invoke": "^0.1.0",
,
    "dynongo": "^0.6.0"
  },

Remove gulpfile in JavaScript project and use npm scripts

Just like the TypeScript project.

upgrade to es6

Drop support for nod 0.10

Don't require github username

While I see that you're using the username as a convenience function to set the name and email address in the package.json, I don't think it should be mandatory; like if someone doesn't enter it offer the option to enter the name and email manually. In my case my github account is completely unrelated to the company I'm doing work for, so I have to hop into the package.json and change it manually negating the convenience factor anyways.

I know it's a minor quibble, but it almost stopped me from using your generator as I immediately had to pause and jump into the source code to see why this module I just downloaded wants to know details about me and what is it going to do with them.

Add support for gulp zip upload to lambda

Via one of several options:

• https://www.npmjs.com/package/gulp-awslambda
• https://www.npmjs.com/package/gulp-aws-lambda
• https://github.com/ThoughtWorksStudios/node-aws-lambda (what I'm using)

Add possibility for directories in files property

The files property should not be used with globbing patterns.

{
  "files": [
    "index.js",
    "util"
  ]
}

should include the index.js file and all the files in the util directory.

Is it ok to ignore license files?

To keep the zip file as small as possible, all the LICENSE files or ignored and are not copied to the zip file. Is this ok to do or not? Probably this isn't and the licenses should be copied to the zip as well.

Add TypeScript app

Scaffold out a project and tests with TypeScript.