npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

grunt-kopper-serverless

v0.0.6

Published

A grunt utility for easily testing and deploying AWS lambda + AWS api gateway apis/apps

Downloads

5

Readme

grunt-kopper-serverless

A grunt utility for easily testing and deploying AWS lambda + AWS api gateway apis/apps.

Build Status Coverage Status Dependency Status devDependency Status

##there is a library too! Use https://github.com/benconnito/kopper-serverless for developing the lambda functions. It has some Error classes, success/fail wrappers, and an AWS config method.

##Getting Started

npm install grunt-kopper-serverless

##usage Unlike most grunt plugins where you grunt.loadNpmTask this library is just some helper methods for auto setting up your config and adding some run, test, and deploy methods.

See the example Gruntfile.js for an example of what to write.

##test helpers

grunt-kopper-serverless uses nodeunit + grunt-contrib-nodeunit for tests. You will need to add a test for each lambda function that you create. place it in /test/api/LAMBDA_NAME/test.js

var Kopper = require('grunt-kopper-serverless');

exports.testMyFirstLambda = {
	testOK: function (test) {
		Kopper.Test.ok(__dirname + '/../../../examples/lambda', 'my-first-lambda', test, {
			isLocal: true,
			id: 'test'
		});
	},
	testFail: function(test){
		Kopper.Test.fail(__dirname + '/../../../examples/lambda', 'my-first-lambda', test, {
			isLocal: true,
			id: 'test'
		});
	},
	testWithContext: function (test) {
		Kopper.Test.test(__dirname + '/../../../examples/lambda', 'my-first-lambda', {
			isLocal: true,
			id: 'test'
		}, {
			succeed: function (response) {
				test.ok(response.message, 'there is a message');
				test.done();
			},
			fail: function (error) {
				test.ok(false, error.toString());
				test.done();
			}
		});
	}
};

##api definition

See api.js for an example api definition file.

##running a local api with apache and cgi-node

If you've set up an api definition. You can run a local version of it via apache and cgi-node.

cgi-node is located at cgi or at https://github.com/UeiRicho/cgi-node

Copy this file into your lambdas folder directory along with app.js.

Replace REAPLACE-cgi-node.min.cgi file with cgi-node from /cgi folder in this repo. Then replace the NODE_EXECUTABLE_PATH and TEMP_PATH values.

Change 'api' in app.js to to whatever file you named your api definition file. The router uses require() to include it.

Then set up your apache directory directive like this:

Options +ExecCGI
AddHandler cgi-script .cgi
		
AddHandler cgi-node .js
Action cgi-node /cgi-node.min.cgi

RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ app.js [QSA,L]