update docs for CRAL with netlify dev #30
Merged
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.
for a while this readme was completely out of date with how we envision people would use CRA with netlify-lambda, in a Netlify Dev world. That is primarily because you no longer need
netlify-lambda
to locally serve Netlify Functions, nor do you need to configure CRA'ssetupProxy
in order to usenetlify-lambda
in order to locally serve Netlify Functions. This is a good deal better.So the reduced scope makes this reference repo almost irrelevant.
Almost.
There is still a usecase for
netlify-lambda
even with Netlify Dev, when you genuinely need to bundle/transform your Netlify Functions (e.g. for import/export syntax, or using TypeScript). That is now the purpose of this repo, to demonstrate how to usenetlify-lambda
as a Netlify Dev "function builder", in acreate-react-app
context (although this is now basically agnostic of whether you usecreate-react-app
orvue-cli
or@angular/cli
etc.).Yes this is non trivial churn. But we always want this repo to show the best practice, what we recommend people to do.