-
-
Notifications
You must be signed in to change notification settings - Fork 797
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update serverless version #1388
Update serverless version #1388
Conversation
Reduced duplicated code
fixed hanging when python raises exception or return nothing
…uplication Revert "Reduced duplicated code"
…-runner Revert "fixed hanging when python raises exception or return nothing"
…5-fix-python-runner Revert "Revert "fixed hanging when python raises exception or return nothing""
… return nothing"""
…2-revert-1365-fix-python-runner Revert "Revert "Revert "fixed hanging when python raises exception or return nothing"""
Co-authored-by: Luciano Jesus Lima <luciano@doutoraovivo.com.br>
* Move authorizer and identity data to requestContext in order to follow lambda proxy specs * Apply context validation for authorizer * Better route initialization logging
hi @AndrewCEmil thank you for the PR!
this should not be the case, as that said, we could still bump the serverless dev dependency to v3. |
@AndrewCEmil unfortunately some tests broke with the update. I'll look into this when I find some time. in the meanwhile I reverted back. |
Description
I updated the serverless version by running
npm i --save-dev serverless@latest
.Motivation and Context
Due to 2 different bugs
npm/cli#3210
serverless/serverless#10876
If you have a version of serverless installed by any package, you cannot run a different version. Since serverless-offline includes all of serverless, it will actually force users that don't have serverless installed elsewhere in their project (ie are using a global installation in their dev environment) to use the version provided by serverless-offline.
Because of all this, and because serverless-offline is a major plugin, it seems right that it should be kept up to date with the main serverless package version.
How Has This Been Tested?
I'm not sure the appropriate way to test this. I just ran the updated package locally and confirmed it worked for all my use cases. Sorry for not being more extensive - I'm happy to do more testing, but I'm not sure how.
Screenshots (if appropriate):