This repository has been archived by the owner on Sep 12, 2019. It is now read-only.
Add support for function builders #94
Merged
Conversation
This file contains 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
This introduces a concept of function builders, that runs some form of build process against a source directory to generate the functions directory used by zip-it-and-ship-it. The immediate goal with this is to make sure netlify-lambda based setups keeps working transparently with netlify-dev
|
fixes #61 |
swyxio
force-pushed
the
function-builds
branch
2 times, most recently
from
9194705
to
824ab04
Compare
swyxio
approved these changes
Apr 8, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This introduces a concept of function builders, that runs some form of build process
against a source directory to generate the functions directory used by zip-it-and-ship-it.
The immediate goal with this is to make sure netlify-lambda based setups keeps working
transparently with netlify-dev
This is one approach to solve the netlify-lambda question, that feels in line with our
general detectors and could potentially be extended to more toolchains.