Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Remove the serve command
See original GitHub issueThis is a Feature Task
Description
In #135 we decided that the serve command will be removed because it does
not add additional value to the Serverless framework as the serverless-offline
integrates with the plugin and does the job even better.
This task should contain all (technical) discussions about the actual removal, so that it can be removed without affecting the other commands/features that will stay in the plugin.
The target milestone for the removal is version 3.0.0 as it is (by definition) a breaking change that needs actions to be taken by users that currently use it.
All PRs for the feature have to be targeted to the (new) v3.0.0-remove-serve branch to keep master clean
for any 2.x.x bugfix or feature versions. We will use this branch to stabilize the feature. The branch will be
rebased to master each time something is added there.
Similar or dependent issue(s):
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This might be a good place for tracking two pending sls-offline PRs on blocking issues for some use-cases for discarding the serve command -
https://github.com/dherault/serverless-offline/pull/283 https://github.com/dherault/serverless-offline/pull/285
@hassankhan Are you interested (and have time) to take care of this?
Additionally to removing the command, we also have to check for then obsolete dependencies that can be removed from the project.