-
Notifications
You must be signed in to change notification settings - Fork 230
Support for Lambda Layers #128
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
Conversation
Can you help pushing this change? |
Does this fix help resolve issue mentioned here? - serverless/serverless#5556 Can this get merged in? |
@schickling ^^ |
@dortega3000 I know it's been a long time. Is there any chance you can update your PR, so it's in sync with master? |
@medikoo can you provide support here? @mmeyers-xomly it seems there are still conflicts... |
@mmeyers-xomly There's still conflicts, can you fix them? |
Hey @medikoo and @micheleangioni, I think these are resolved in my PR. I can't update this PR here since I don't have access, but it looks like mine has them all resolved: #267 |
Amazing, thanks @mmeyers-xomly . This should be good I think, @medikoo |
Closing in favor of #267 |
Set the right artifact paths for Lambda layers after TypeScript Compile