Merged
Conversation
added 4 commits
June 24, 2016 18:36
When using webpack, we may have one npm package and multiple lambda functions sharing code. Lambda functions don't necessarily have a package.json in them.
Collaborator
|
+1; @sean-shirazi great work, even added tests! 👍 |
Author
|
@DeviaVir Fantastic. Thanks. |
Merged
Collaborator
|
this change has been deployed to |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I use Webpack both to get the latest language features and get around the 'npm link' and dependencies with local paths problem; non of which seems to be supported by node-lambda.
The new
--prebuiltDirectoryflag is useful for working with Webpack. It skipsnpm install --productionandpost_install.shand simply packages the specified directory.