Because:
* New routes and some account cleanup is needed for allowing a new
account with no password. This requires multiple re-usable functions
to be extracted from the existing create account handler.
This commit:
* Converts the account.js file to TypeScript and refactors the handlers
into a class to make room for the new account creation route.
Ref #8735
Because:
* We are using NestJS for application architecture on new projects.
This commit:
* Moves the event-broker to a NestJS architecture.
Closes#6238
- We have two clients for the auth-server API, one in `content-server/app/scripts/lib/auth` and `fxa-js-client`. The content-server one was meant to replace fxa-js-client but I didn't finish the work to get it running on nodejs.
- Extracts the content-server implementation into `fxa-auth-client`
- Wraps the implementation with shims to work with nodejs in `server.ts`
- Updates references to fxa-js-client to use fxa-auth-client
- Removes fxa-js-client
Because:
* The gql-api needs the ability to issue new recovery codes and
update the users two-factor auth settings.
This commit:
* Add's two-factor auth and recovery code mutations.
Closes#5395
Because:
* We want to alter/update the profile avatar/displayname and modify
email addresses in use.
This commit:
* Add's mutations to upload an avatar, change the display name, and
manipulate email addresses in use.
Closes#5397, #5396
To reduce duplication and encourage consistency in our
typescript builds this extracts most of the options
into two base configs, one for node and one for browsers.
Also, in order to better utilize workspaces the require
paths to fxa-shared and fxa-react were updated throughout.