Discuss removing `serve` command

Given that serverless-offline and serverless-simulate both exist, are there many users of this plugin that use the included serve functionality?

Removing it would help a lot with code bloat, allowing the plugin to focus solely on building bundles via Webpack.

Any feedback from users would highly be appreciated, would be great to know what plugin/combinations of plugins you use for development.

[arabold]

We’re successfully using serverless-offline in combination with serverless-webpack since months. I tried theserve command once but it didn’t really work well and didn’t provide the full simulation as serverless-offline does. There are A LOT of things to consider when trying to simulate API Gateway correctly.

So I’m absolutely for removing the serve command from serverless-webpack and redirect users to serverless-offline instead. This will allow focusing on the core features which are packaging, not simulating IMO.

[arabold]

There’s a difference between lambda and lambda-proxy integration in Serverless. I don’t remember which one works which way, but over the last two years a pattern has emerged for us:

const body = _.isString(event.body) ? JSON.parse(event.body) : event.body;

This seems to be the most reliable and robust way around different behaviors of the simulation. 🤔