Pin package dependencies, remove CRWA template yarn.lock, set up Yarn offline cache

[thedavidprice]

Per Core Team discussion, I made the following changes in an attempt to improve dependency stability across packages:

• pin all dependencies versions
• remove create-redwood-app/template/yarn.lock
• set up Yarn offline cache; add dependency tgz files to repo (moving to separate PR set up yarn offline cache #2669)
• adds '@babel/plugin-proposal-nullish-coalescing-operator' to babel.config and core/config/babel-preset
  • look into removing in Webpack 5 PR
• fixes FetchConfigProvider (which were apparently hidden previously)
• Deprecate authToken from AuthContext

[thedavidprice]

UPDATE: solved with nhost package update. And, yes, it was an error hidden by yarn.lock I believe.

Wow, not at all understanding how I'm encountering this TS build error:

packages/auth/src/authClients/nhost.ts:80:9 - error TS2345: Argument of type '{ email: any; password: any; options: { userData: { display_name: any; }; }; }' is not assignable to parameter of type 'registerCredentials'.
  Object literal may only specify known properties, and 'options' does not exist in type 'registerCredentials'.

80         options: { userData: { display_name: email } },

Has it been there all along and we've just missed it due to dependency version resolutions? That's the only thing I've changed in this PR.

[cypress]

---

Test summary

17 • 0 • 0 • 0 • 1

---

Run details

Project	RedwoodJS Framework
Status	Passed
Commit	c9dd80d ℹ️
Started	May 28, 2021 5:30 PM
Ended	May 28, 2021 5:40 PM
Duration	09:51 💡
OS	Linux Ubuntu - 20.04
Browser	Chrome 90

View run in Cypress Dashboard ➡️

---

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard

[thedavidprice]

@dac09 I believe I've tracked down the Babel error, which is:

../redwood/web/dist/components/FetchConfigProvider.js 29:40
Module parse failed: Unexpected token (29:40)
File was processed with these loaders:
 * ../node_modules/babel-loader/lib/index.js
You may need an additional loader to handle the result of these loaders.
| 
| const FetchConfigProvider = ({
>   useAuth = global.__REDWOOD__USE_AUTH ?? (() => ({
|     loading: false,
|     isAuthenticated: false

It's coming from the transpiled file redwood/web/dist/components/FetchConfigProvider.js. It's throwing the error on the ?? operator, which seems strange to me. If I modify the file directly like this, indeed I resolve the issue:

useAuth = global.__REDWOOD__USE_AUTH ? global.__REDWOOD__USE_AUTH : (() => ({

The source code is here:

redwood/packages/web/src/components/FetchConfigProvider.tsx

Lines 15 to 22 in 9d8fa28

	export const FetchConfigProvider: React.FunctionComponent<{
	useAuth?: () => AuthContextInterface
	}> = ({
	useAuth = global.__REDWOOD__USE_AUTH ??
	(() => ({ loading: false, isAuthenticated: false })),
	...rest
	}) => {
	const { isAuthenticated, authToken, type } = useAuth()

So I attempted to use different syntax/conditional here; however, I run into TS errors for AuthContextInterface. What I think is going on is that the conditional logic for the case !global.__REDWOOD__USE_AUTH results in invalid TS for useAuth() —> authToken, type specifically.

Assuming I'm correct, I need your help resolving.

Update: I was not correct...