-
Notifications
You must be signed in to change notification settings - Fork 415
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
fix for deploying individual packages. #48
fix for deploying individual packages. #48
Conversation
370fb79
to
2145591
Compare
2145591
to
64e2391
Compare
Looks like there's some logic there. Is this something that could be tested? :) |
Would have added tests but there was non for the existing behavior and the logic was copied from serverless individual deployment feature. But if that is a requirement then will add some tests. |
@gertjvr are you able to deploy individual functions (and individually packaged)? I'm using your PR48, and it packages correctly, but when I execute |
any update on when this will be merge? |
Any chance this can get merged? |
Looking at it now. Will merge asap |
|
Same for me, I'm doing single function deploy and getting an error on Lambda deploy because the web package is not doing his work. |
So the plugin is just uploading the code not compiling for deploy function. If i pull out the es6 stuff it then rejects like above, talking about functions that are there but saying they aren't. I'm getting this: Syntax error in module ‘handler’: SyntaxError if i do this then do sls deploy -v it then works fine after the full deploy |
A new version that includes #130 will be published today. With that it should be possible to use |
Serverless added the ability to deploy functions individually when using
serverless-webpack
it doesn't change the paths of the individual artifacts similar to how it change the this.serverless.package.artifact.This solutions is very brittle as it copies how individual packages was implemented.