draft: CRA migration, DX slim-down

[mattxwang]

This draft PR (in its current state):

• installs create-react-app via react-scripts
  • sneaky fixes include changing the source URL for module resolution, and the homepage field in package.json
• changes the API_URL to read from the DEV env var; defaults to https://members.uclaacm.com/app if we're not in dev, which currently causes a CORS issue if not deployed to it
• replaces node-sass with sass
• removes everything related to:
  • Jenkins
  • nginx
  • babel
  • husky
  • lint-staged
  • jest and enzyme
  • the fetch polyfill
  • webpack
• fixes newfound linter issues (unused imports, failed nan checks, etc.)
• switches the body font from Lato to Open Sans

Locally, it builds and runs; we only run into problems once we hit the backend, as this introduces CORS issues.

To merge this, I think we need to:

• somehow resolve this CORS issue and/or figure out how to deploy this
  • if we keep the rest of our deploy setup, then we need to resolve CORS, the final dockerized bundle, API subdomains, etc.
  • idea: maybe make a staging backend on heroku!
• re-add the relevant linting tools (though I'm fine with just eslint, as that's not a regression)
• add a CI action to ensure that yarn build passes
• documents these changes somehow

[mattxwang]

@reginawang99

[reginawang3495]

Just to confirm, was the intention of the PR to move completely away from Docker?

And what could I help with here? I tested on my computer and yarn install and yarn start opens up the app properly.

[mattxwang]

Just to confirm, was the intention of the PR to move completely away from Docker?

And what could I help with here? I tested on my computer and yarn install and yarn start opens up the app properly.

Partially, yes - let me write this down, didn't get the opportunity to do it before. I'll tag you in the issue!

[mattxwang]

Just going through my own stale PRs, bump @matthewcn56; what do you want to do about this?