When running with version 1.33 and over the serverless process exits killing the local server.

This means the express instance is stopped and nothing is bound to the port.

Must be a change in the plugin architecture?

https://github.com/serverless/serverless/releases/tag/v1.33.0

The following error occures on serverless v 1.19.0

Serverless Error ---------------------------------------

  Serverless command "local-dev-server" not found

  Run "serverless help" for a list of all available commands.

  Stack Trace --------------------------------------------

Windows 10, Node 6.11

Error: Invalid regular expression: /^\http\echo(?:([^\/]+?))/?$/: Unmatched ')'
HttpEndpoint.js (15, ..)

I assume this has something to do with the way Windows treats slashes. If I update this line:

this.path = path.join('/http', this.resourcePath)

to be fixed:

this.path = path.posix.join('/http', this.resourcePath)

The error is gone and all works.

Hi.

Great stuff with the plugin. I think it is very important that we have a local dev setup as well :)

Although, I could not get it to work for my python project. I get the following error.

Serverless: HTTP: get hello/world Serverless: ➡ Failure: Cannot find module '/Users/prakashraman/<path>/Code/api/handler'

Does this only work with a NodeJS codebase?

Hello,

This module almost does exactly what I need. However when running on AWS the event object that gets passed to the lambda has a property called path which is missing in this module.

Here's an example event object sent from API Gateway to my Lambda...

{ "resource": "/profile",
  "path": "/profile",
  "httpMethod": "GET",
  "headers": 

Here is the event object sent in the module...

{ httpMethod: 'GET',
  body: '{}',
  queryStringParameters: {},
  pathParameters: {}
}

I've made this available by editing Server.js on line 82...

lambdaEvent.path = endpoint.resourcePath;

Do you think this is a plausible change to the module? I'm happy to make a pull request.

Thanks for making this module, its super useful!

Regards,
/t

Hello again,

Have you thought about supporting cookies? The lambda I'm developing interacts with the cookie header.

I'll also create a PR for this if you're interested?

Thanks,
/t

Hello again,

Have you thought about providing HTTPS support?

I got a crude version working by adding this code into Server.js...

const https = require('https');
const fs = require('fs');
const options = {
    cert: fs.readFileSync('/Users/tmo2367/Certs/localhost-cert.pem'),
    key: fs.readFileSync('/Users/tmo2367/Certs/localhost-key.pem'),
    passphrase: 'XXXXX'
};
https.createServer(options, this.app).listen(8443);

You'd want HTTPS to be enabled via a flag, and also the 3 option values too.

This is useful as I'm doing AWS Cognito integration, passing the user back to your serverless app requires a HTTPS URL to be added into Cognito.

Shall I make a PR if you're interested and not already started this?

Thanks,
/t