Move web and api jest configs to proper directories

[AryanJ-NYC]

Contributes to #181

[thedavidprice]

Hi @AryanJ-NYC thanks for getting this process started. I only had time for a quick look but will spend more time early next week.

There is some complexity here because the package/core/ is providing config to the create-redwood-app, and what we think we need to do is make that config extensible in the create-redwood-app root, api, and web directories. (Maybe… that’s the current discussion about what the best path forward is.) So in this case, it’s not adding the config to separate web/ and api/ folders within core/config/, it’s actually about moving them to create-redwood-app/web/…, etc over in https://github.com/redwoodjs/create-redwood-app Developers are going to have all kinds of wacky things to add to jest + babel config and will need to extend as needed. Does that make sense?

Looping in @peterp ‘cause this is good momentum to get us back on the conversation.

[AryanJ-NYC]

Hey @thedavidprice. Thanks for the feedback.

What if users are defaulted with no jest.config.js in both the web and api directories BUT can make a jest.config.js that Redwood uses to extend the base jest.config.js in @redwoodjs/web and @redwood/api?

That way, there's zero config unless otherwise needed.

I'm basing this on next.js use of next.config.js: https://nextjs.org/docs/api-reference/next.config.js/introduction. I'm quite sure they simple take in the custom config and extend their own based on the customization.

[thedavidprice]

Yes, that’s the right direction! If you haven’t already, see current conversation with Peter here #181

For now I think we can just leave files as-is in core/config. And then we’ll need to tie together two things:

• the actual command that’s run when user enters yarn rw test, which is 'yarn jest --passWithNoTests --config ../node_modules/@redwoodjs/core/config/jest.config.[api | web].js' found here: packages/cli/src/commands/test.js
• a means to extend our core config within the app using something similar to Babel “extends” or the Nextjs example above.

We’ll need documentation either way. I’m in favor of an empty starter/template file already in the app with simple commented help text at the top. But more files in CRA is more overhead to upgrade over time. TBD