Instructions are conflicting and out of date

[maiya-22]

The readme and various instructions are conflicting.

• When you google "netflify lambda create react app" this repo and instructional videos pointing to it are the first results.

• The .setupProxy.js file is missing from the repo.

• In the history, you can find a note about why it was deleted; and comment about updated instructions.

• link to commit and notes when was deleted: https://github.com/netlify/create-react-app-lambda/commit/eb77fe87e6431d2e3497cb13f29f4a2690795763

• link to notes about updated method and readme: https://github.com/netlify/create-react-app-lambda/pull/30

• However, there are no complete instructions about how to run it without it, and a repo does not work automatically when removed ; nor when you change the url, per the readme.

• Link above says that readme used to be out of date, but video in readme is the same out of date video.

• Can someone please clarify/ update the instructions.

• current docs also point to this repo and video https://functions.netlify.com/example/create-react-app-lambda/

[jeffreytgilbert]

@maiya-22 in a perfect world, service providers with library integration kits for running micro services, serverless FaaS, and PaaS would have their testing, their docs, and their libraries all in sync with the versions, but I haven't noticed that yet for the providers and libraries I've been getting into lately. Nexus and Prisma and Netlify and Yarn 2 seem to evolve faster than the libraries around them, which i guess is fine, but it is a somewhat dystopian reality from the slick looking shrink wrapped web building promises we're buying into.

All that to say, I'd love it if these features weren't actually considered features unless they had supported and updated barebones boilerplates or create templates that were tested against releases and products/services from the providers so we knew when things were ready vs when they were vaporware. This project hasn't been touched in 2-3 years!

[maiya-22]

@jeffreytgilbert Well said. And I agree.

[jeffreytgilbert]

Check out redwood.js. I was digging into it while researching how to wire up all these libraries and it turns out it has it already done and ready to deploy to multiple FaaS vendors.