dabit3/gatsby-auth-starter-aws-amplify

Starter Project with Authentication with Gatsby & AWS Amplify

Gatsby Auth starter with AWS Amplify

This auth starter implements a basic authentication flow for signing up signing in users as well as protected client side routing using AWS Amplify. Auth features:

• User sign up
• User sign in
• Multi-factor Authentication
• User sign-out

Deploy to the Amplify console

Click the button to deploy a fullstack app in your AWS account:

You can now continuously deploy changes to your frontend or backend and Amplify Console will automatically deploy those changes.

Run locally

1. Create the project

gatsby new gatsby-amplify-auth https://github.com/dabit3/gatsby-auth-starter-aws-amplify

2. Change into the new directory

cd gatsby-amplify-auth

3. Install dependencies

yarn
# or
npm install

4. Install & configure the AWS Amplify CLI.

npm install -g @aws-amplify/cli

amplify configure

To see a video of how to configure the CLI, click here

5. Create a new AWS Amplify Project

amplify init

Here, walk through the following steps:

• Enter a name for the project YOURPROJECTNAME
• Enter a name for the environment master
• Choose your default editor: Visual Studio Code (or your editor of choice)
• Choose the type of app that you're building javascript
• What javascript framework are you using react
• Source Directory Path: src
• Distribution Directory Path: public
• Build Command: npm run-script build
• Start Command: npm run-script develop

6. Push the updated project configuration to AWS. It will deploy a CloudFormation template that has an Amazon Cognito resource that enables user authentication.

amplify push

7. Then you can run it by:

gatsby develop

gatsby-auth-starter-aws-amplify's Issues

Permission Error

When the site is deployed to Amplify via Github, I get a permission error when viewing the Amplify URL.

NOT ABLE TO SIGN UP

I have got the starter setup and after running gatsby develop I cannot sign up

Why is this happening and how come it is so difficult (impossible) to sign up?
phone numbers tried
555 555 5555
555-555-6555
(555) -555-6555

error signing up...
{code: "InvalidParameterException", name: "InvalidParameterException", message: "Invalid phone number format."}
code: "InvalidParameterException"
name: "InvalidParameterException"
message: "Invalid phone number format."
proto: Object

NPM package error: Error: Cannot create as TypeComposer the following value: Date.

When first trying to run "gatsby develop" I received this error:

It is also documented here: aws-amplify/learn#41

Installing packages with Yarn resolved this issue.

gatsby site will not start due to major error

H Nada,
Firstly thanks for the tutorials.
Have gone along on a few of theReact ones and they have been very informative.
Now moving to graphql and hit a wall.
Have tried 3 different times from scratch to install and run this project for amplify but keep getting various errors on gatsby locally after installing project. Will not run.
Initially there was graphql conflict saying 2 versions of grpahql in nodes so cannot start
deleted both present and reinstalled latest.
That error went away
then this that I have been unable to resolve.
Seems to be something with graphql conflicts reading some posts but cannot be sure

Using "gatsby develop" I get the following

success open and validate gatsby-configs - 0.027s
success load plugins - 0.939s
success onPreInit - 0.044s
success initialize cache - 0.025s
success copy gatsby files - 0.045s
success onPreBootstrap - 0.026s
success createSchemaCustomization - 0.008s
success Checking for changed pages - 0.002s
success source and transform nodes - 0.129s

ERROR

Missing onError handler for invocation 'building-schema', error was 'Error: Cannot create as TypeComposer the following value: Date.'. Stacktrace was 'Error: Cannot create as TypeComposer the following value: Date.
at SchemaComposer.createTempTC (/Users/marksteven/Documents/sites/mytutorial-app/wildwood/node_modules/graphql-compose/lib/SchemaComposer.js:365:11)
at SchemaComposer.addAsComposer (/Users/mark/Documents/sites/mytutorial-app/wildwood/node_modules/graphql-compose/lib/SchemaComposer.js:563:27)
at createSchemaComposer (/Users/mark/Documents/sites/mytutorial-app/node_modules/gatsby/src/schema/schema-composer.js:16:18)
at build (/Users/mark/Documents/sites/mytutorial-app/node_modules/gatsby/src/schema/index.js:104:26)
at buildSchema (/Users/mark/Documents/sites/mytutorial-app/node_modules/gatsby/src/services/build-schema.ts:19:3)'

Hope this helps
Mark

Browser refresh causes auth errors

Just cloned this and tested it out. Seems to work fine but when I click refresh after logging in I get the following error:

[ERROR] 26:36.281 AuthClass - Cannot get the current user because the user pool is missing. Please make sure the Auth module is configured with a valid Cognito User Pool ID
e._log @ ConsoleLogger.js:80
e.error @ ConsoleLogger.js:146
(anonymous) @ Auth.js:1085
(anonymous) @ Auth.js:44
(anonymous) @ Auth.js:25
s @ Auth.js:17
Promise.then (async)
u @ Auth.js:18
a @ Auth.js:16
Promise.then (async)
u @ Auth.js:18
(anonymous) @ Auth.js:19
r @ Auth.js:15
e.currentAuthenticatedUser @ Auth.js:1043
a @ gatsby-browser.js:13
(anonymous) @ api-runner-browser.js:29
t.apiRunner @ api-runner-browser.js:20
E @ navigation.js:45
n.componentDidMount @ navigation.js:137
Ha @ react-dom.production.min.js:216
za @ react-dom.production.min.js:220
(anonymous) @ react-dom.production.min.js:250
t.unstable_runWithPriority @ scheduler.production.min.js:18
Rs @ react-dom.production.min.js:250
Is @ react-dom.production.min.js:249
Ps @ react-dom.production.min.js:248
Cs @ react-dom.production.min.js:245
Qa @ react-dom.production.min.js:243
Ls @ react-dom.production.min.js:253
js @ react-dom.production.min.js:253
Bs.render @ react-dom.production.min.js:261
(anonymous) @ react-dom.production.min.js:264
Ds @ react-dom.production.min.js:251
Ws @ react-dom.production.min.js:264
hydrate @ react-dom.production.min.js:266
(anonymous) @ production-app.js:113
setTimeout (async)
(anonymous) @ ready.js:32
(anonymous) @ production-app.js:112
Promise.then (async)
(anonymous) @ production-app.js:85
Promise.then (async)
(anonymous) @ production-app.js:31
s @ bootstrap:88
n @ bootstrap:45
t @ bootstrap:32
(anonymous) @ app-369a707a093d910ed867.js:1

Can't Build Project

When following the README instructions "Run locally", during the install step npm can't find a package:

"npm ERR! notarget No matching version found for gatsby-plugin-offline@next"

When doing git clone [email protected]:dabit3/gatsby-auth-starter-aws-amplify.git
and then cd into directory, npm install
"npm ERR! notarget No matching version found for gatsby-plugin-react-helmet@next"

macOS 10.14.4, npm version 6.4.1, node v10.12.0, gatsby v 2.5.11

Amplify status without data

After crashed when publish project to aws I had init new amplify configuration
After that I don't seee any data before added to the project by amplify status

Api
Auth

I have these files at project dir

amplify publish still do not usable for publish project

Fail to start...

I tried to use this one but I failed.

The last step gatsby develop it produce below errors

 ERROR

UNHANDLED REJECTION Cannot create as TypeComposer the following value: Date.



  Error: Cannot create as TypeComposer the following value: Date.

  - SchemaComposer.js:365 SchemaComposer.createTempTC
    [gatsby-amplify-auth]/[graphql-compose]/lib/SchemaComposer.js:365:11

  - SchemaComposer.js:563 SchemaComposer.addAsComposer
    [gatsby-amplify-auth]/[graphql-compose]/lib/SchemaComposer.js:563:27

  - schema-composer.js:35 createSchemaComposer
    [gatsby-amplify-auth]/[gatsby]/dist/schema/schema-composer.js:35:18

  - index.js:65 Object.module.exports.build
    [gatsby-amplify-auth]/[gatsby]/dist/schema/index.js:65:26

Can you give me some hint? Thank you!

AWS Amplify configure step requests should not request full Admin policy

AdministratorAccess is far too powerful a policy and we shouldn't be asking users to grant it to Amplify CLI during configure step.

GATSBY STARTER IS NOT STARTING UP

I basically did the following

1. amplify config

• ran through the install steps

2. amplify init
   set up env name and selected profile
3. amplify add api

• went through the steps to create guided schema with graphQL selected the fine grained access control

4. amplify push
5. gatsby develop

I run into the error

Error: Cannot create as TypeComposer the following value: Date.

• SchemaComposer.js:365 SchemaComposer.createTempTC

Please help! It is so frustruating when starter files do not WORK

gatsby dependencies fail to install when using "next" in package.json

next tag is longer supported by gatsby
gatsbyjs/gatsby#12463 (comment)

amplify publish needs "hosting add" and crashed when publish 2

When Im trying publish project amplify ask me

Please add hosting to your project before publishing your project
Command: amplify hosting add

Trying to add hosting without chances

amplify hosting add
Hosting is already fully enabled.

Error: Hosting is already fully enabled.

Documentation - Change Default Project Name?

I just tested this starter out and it works great, however the amplify init did not ask for a project name, so the CLI tool provisioned everything as my-aws-project. Trying to change the project named seemed to end up in a various states of error.

Proposal would be to update the documentation to show where to change that project name before running amplify init or linking to documentation from Amplify that shows a step by step how to change project name and reprovision. I was looking for something here but was not able to find something specific: https://aws-amplify.github.io/docs/cli/init#amplify-configure-project

SSR part of gatsby build fails due to AWS Amplify client libraries not being "Node safe"

When I run npm run build, I get the following error:
failed Building static HTML for pages - 8.576s

ERROR #95312

"navigator" is not available during server side rendering.

See our docs page for more info on this error: https://gatsby.dev/debug-html

85 | var ACCEPTED_CODES = [202];
86 | var MOBILE_SERVICE_NAME = 'mobiletargeting';

87 | var BEACON_SUPPORTED = navigator && typeof navigator.sendBeacon === 'function';
| ^
88 | // events buffer
89 | var BUFFER_SIZE = 1000;
90 | var FLUSH_SIZE = 100;

WebpackError: ReferenceError: navigator is not defined

• AWSPinpointProvider.js:87 Module../node_modules/@aws-amplify/analytics/lib-esm/Providers/AWSPinpointProvider.js
  node_modules/@aws-amplify/analytics/lib-esm/Providers/AWSPinpointProvider.js:87:1

• Analytics.js:1 Module../node_modules/@aws-amplify/analytics/lib-esm/Analytics.js
  node_modules/@aws-amplify/analytics/lib-esm/Analytics.js:1:1

• index.js:1 Module../node_modules/@aws-amplify/analytics/lib-esm/index.js
  node_modules/@aws-amplify/analytics/lib-esm/index.js:1:1

• index.js:1 Module../node_modules/aws-amplify/lib-esm/index.js
  node_modules/aws-amplify/lib-esm/index.js:1:1

• header.js:1 Module../src/components/header.js
  src/components/header.js:1:1

• 404.js:1 Module../src/pages/404.js
  src/pages/404.js:1:1

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] build: gatsby build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\romer\AppData\Roaming\npm-cache_logs\2019-12-10T13_36_16_975Z-debug.log

Can Aws Amplify client libraries be "Node safe" to prevent this issue?

Change cognito userpool?

Unfortunately, userpools cannot be edited once setup and we need to change the required parameters from username to email for example. Its not clear to me where the userpool can be changed? Thanks - saved me a ton of time!

Incompatible graphql versions between Gatsby and Amplify

I cloned this repo and followed the steps. I get the following error when I run gatsby develop

I investigated the package-lock file and noticed that Amplify deps for graphql are 0.13.0 and the Gatsby version is 0.13.2 I'm not sure why. I'm assuming because the dependancy in your package.json is using next in a couple places and the versions got out of sync at some point.

error Cannot use GraphQLObjectType "SitePageConnection" from another module or realm.

Ensure that there is only one instance of "graphql" in the node_modules
directory. If different versions of "graphql" are the dependencies of other
relied on modules, use "resolutions" to ensure only one version is installed.

https://yarnpkg.com/en/docs/selective-version-resolutions

Duplicate "graphql" modules cannot be used at the same time since different
versions may have different capabilities and behavior. The data from one
version used in the function from another could produce confusing and
spurious results.


  Error: Cannot use GraphQLObjectType "SitePageConnection" from another module or realm.
  Ensure that there is only one instance of "graphql" in the node_modules
  directory. If different versions of "graphql" are the dependencies of other
  relied on modules, use "resolutions" to ensure only one version is installed.
  https://yarnpkg.com/en/docs/selective-version-resolutions
  Duplicate "graphql" modules cannot be used at the same time since different
  versions may have different capabilities and behavior. The data from one
  version used in the function from another could produce confusing and
  spurious results.

Update gatsby-node.js and / or gatsby-ssr.js for server-side rendering

I tried to implement the example given in the new SSR features into the gatsby-node.js file but kept having issues with Authentication. It would be better to have a working example here to reference how some data can be rendered from a DynamoDB query during build-time (a query that isn't expected to change much since the data would only be updated for each new build).

Refreshing a route while logged in redirects to index.html

I'm running into an issue with redirects when I deploy this app. The issue is that when I am logged in and reload the page, I get redirected to index.html which then redirects me to the home page. The expected behavior is that reloading the page should maintain the current route.

Steps to reproduce:

1. Log in
2. go to /app/home
3. Reload the page
4. App redirects user to / route which forces the user to have to navigate back to the /app/home to get where they were.

I made a video which documents this behavior:
https://www.youtube.com/watch?v=3rhpsWgAX3s

I played around with this and the behavior can be "fixed" by changing the 404 redirect to a 404 rewrite, but it has the negative consequence that none of the meta tags load and it shows up to facebook link debugger as a 404 error (in contrast to the default behavior where it all loads correctly). So that's to say that the 404 rewrite change probably isn't a long term solution.

Any ideas how you'd go about fixing this? Thanks so much for contributing this demo repo Nader, it's really great!

amplify publish needs "hosting add" and crashed when publish

when i executed:
amplify publish
had an error:
Please add hosting to your project before publishing your project

then i ran:
amplify hosting add
and after
amplify publish

then ... another error ocurrs:

`
gatsby build

success open and validate gatsby-config — 0.008 s
success load plugins — 0.138 s
success onPreInit — 0.418 s
success delete html and css files from previous builds — 0.058 s
success initialize cache — 0.008 s
success copy gatsby files — 0.060 s
success onPreBootstrap — 0.003 s
success source and transform nodes — 0.016 s
success building schema — 0.169 s
success createPages — 0.005 s
success createPagesStatefully — 0.026 s
success onPreExtractQueries — 0.000 s
success update schema — 0.056 s
success extract queries from components — 0.032 s
success run graphql queries — 0.028 s — 6/6 223.35 queries/second
success write out page data — 0.003 s
success write out redirect data — 0.001 s
⢀ onPostBootstrapdone generating icons for manifest
success onPostBootstrap — 0.305 s

info bootstrap finished - 4.992 s

error Generating JavaScript bundles failed

Error: ./node_modules/graphql/index.mjs 64:0-70:117
Can't reexport the named export 'BREAK' from non EcmaScript module (only default export is available)
at HarmonyExportImportedSpecifierDependency._getErrors (/Users/vladimirestrada/Documents/Code/brunoferrini/gatsby/gatsby-auth/node_modules/webpack/lib/dependencies/Harmo nyExportImportedSpecifierDependency.js:344:6)
at HarmonyExportImportedSpecifierDependency.getErrors (/Users/vladimirestrada/Documents/Code/brunoferrini/gatsby/gatsby-auth/node_modules/webpack/lib/dependencies/Harmon yExportImportedSpecifierDependency.js:322:16)
at Compilation.reportDependencyErrorsAndWarnings (/Users/vladimirestrada/Documents/Code/brunoferrini/gatsby/gatsby-auth/node_modules/webpack/lib/Compilation.js:1014:22)
at Compilation.finish (/Users/vladimirestrada/Documents/Code/brunoferrini/gatsby/gatsby-auth/node_modules/webpack/lib/Compilation.js:832:9)
at hooks.make.callAsync.err (/Users/vladimirestrada/Documents/Code/brunoferrini/gatsby/gatsby-auth/node_modules/webpack/lib/Compiler.js:492:17)
at _err0 (eval at create (/Users/vladimirestrada/Documents/Code/brunoferrini/gatsby/gatsby-auth/node_modules/tapable/lib/HookCodeFactory.js:24:12), :11:1)
at _addModuleChain (/Users/vladimirestrada/Documents/Code/brunoferrini/gatsby/gatsby-auth/node_modules/webpack/lib/Compilation.js:771:12)
at processModuleDependencies.err (/Users/vladimirestrada/Documents/Code/brunoferrini/gatsby/gatsby-auth/node_modules/webpack/lib/Compilation.js:710:9)
at _combinedTickCallback (internal/process/next_tick.js:131:7)
at process._tickCallback (internal/process/next_tick.js:180:9)
@ ./node_modules/@aws-amplify/api/lib/API.js
@ ./node_modules/@aws-amplify/api/lib/index.js
@ ./node_modules/aws-amplify/lib/index.js
@ ./src/pages/index.js
@ ./.cache/async-requires.js
@ ./.cache/production-app.js
`

Error signing up in demo site

When attempting to sign up in the demo site I get the following error:

errorMessage: {
 "code": "ResourceNotFoundException",
 "name": "ResourceNotFoundException",
 "message": "User pool client mqf1hekas6mvbbsst9ffne1nt does not exist."
}

Add Social IdP Example

Thanks for the great starter! It's been a great reference.

One thing I think would be a great addition is a Facebook/Google auth login example. Most examples out there use the Authenticator high order component from aws-amplify-react, which this starter site stays away from.

Lambda functions need to be updated to nodejs12.x runtime

It looks like the Lambda functions need to be updated from nodejs8.10 to nodejs12.x. At the moment $ amplify push fails with:

The runtime parameter of nodejs8.10 is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (nodejs12.x) while creating or updating functions. (Service: AWSLambdaInternal; Status Code: 400; Error Code: InvalidParameterValueException; ... )

Security vulnerability: sensitive user fields in local storage

Following user authentication, the user information returned from Auth.currentAuthenticatedUser() is saved to local storage:
https://github.com/dabit3/gatsby-auth-starter-aws-amplify/blob/master/src/components/Login.js#L25
https://github.com/dabit3/gatsby-auth-starter-aws-amplify/blob/master/src/utils/auth.js#L3

This appears to results in sensitive user fields such as the password being saved in local storage in plain text. Seems to be a serious security issue for anyone using this Gatsby starter.

Any suggestions on fixing that while still having a proper token of logged in user available for signing GraphQL calls etc.?

Amplify Console build error

The frontend build step on Amplify Console would fail with the following error.

# Starting phase: preBuild
# Executing command: yarn install
2019-04-14T23:17:04.159Z [INFO]: yarn install v1.13.0
2019-04-14T23:17:04.271Z [WARNING]: warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
2019-04-14T23:17:04.276Z [INFO]: [1/4] Resolving packages...
2019-04-14T23:17:04.326Z [WARNING]: warning Resolution field "[email protected]" is incompatible with requested version "graphql@^0.13.2"
2019-04-14T23:17:04.961Z [INFO]: [2/4] Fetching packages...
2019-04-14T23:17:19.517Z [INFO]: info [email protected]: The platform "linux" is incompatible with this module.
2019-04-14T23:17:19.518Z [INFO]: info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
2019-04-14T23:17:19.537Z [INFO]: [3/4] Linking dependencies...
2019-04-14T23:17:19.548Z [WARNING]: warning "gatsby > [email protected]" has incorrect peer dependency "graphql@^0.13.2".
2019-04-14T23:17:26.618Z [INFO]: [4/4] Building fresh packages...
2019-04-14T23:17:28.008Z [INFO]: success Saved lockfile.
2019-04-14T23:17:28.014Z [INFO]: Done in 23.86s.
2019-04-14T23:17:28.031Z [INFO]: # Completed phase: preBuild
# Starting phase: build
2019-04-14T23:17:28.032Z [INFO]: # Executing command: yarn run build
2019-04-14T23:17:28.201Z [INFO]: yarn run v1.13.0
2019-04-14T23:17:28.252Z [INFO]: $ gatsby build
2019-04-14T23:17:29.952Z [INFO]: success open and validate gatsby-config — 0.006 s
2019-04-14T23:17:30.092Z [INFO]: success load plugins — 0.140 s
2019-04-14T23:17:30.240Z [INFO]: success onPreInit — 0.148 s
2019-04-14T23:17:30.246Z [INFO]: success delete html and css files from previous builds — 0.006 s
2019-04-14T23:17:30.253Z [INFO]: success initialize cache — 0.007 s
2019-04-14T23:17:30.264Z [INFO]: success copy gatsby files — 0.011 s
2019-04-14T23:17:30.265Z [INFO]: success onPreBootstrap — 0.001 s
2019-04-14T23:17:30.280Z [INFO]: success source and transform nodes — 0.016 s
2019-04-14T23:17:30.408Z [INFO]: success building schema — 0.128 s
2019-04-14T23:17:30.413Z [INFO]: success createPages — 0.004 s
2019-04-14T23:17:30.435Z [INFO]: success createPagesStatefully — 0.021 s
2019-04-14T23:17:30.435Z [INFO]: success onPreExtractQueries — 0.000 s
2019-04-14T23:17:30.503Z [INFO]: success update schema — 0.067 s
2019-04-14T23:17:30.538Z [INFO]: success extract queries from components — 0.035 s
2019-04-14T23:17:30.567Z [INFO]: success run graphql queries — 0.029 s — 6/6 215.69 queries/second
2019-04-14T23:17:30.570Z [INFO]: success write out page data — 0.003 s
2019-04-14T23:17:30.571Z [INFO]: success write out redirect data — 0.000 s
2019-04-14T23:17:30.729Z [INFO]: done generating icons for manifest
2019-04-14T23:17:30.730Z [INFO]: success onPostBootstrap — 0.159 s
2019-04-14T23:17:30.730Z [INFO]: 
info bootstrap finished - 2.462 s
2019-04-14T23:17:30.730Z [INFO]: 
2019-04-14T23:17:32.711Z [WARNING]: Browserslist: caniuse-lite is outdated. Please run next command `yarn upgrade caniuse-lite browserslist`
2019-04-14T23:18:00.734Z [INFO]: success Building production JavaScript and CSS bundles — 30.002 s
2019-04-14T23:18:04.476Z [INFO]: 
2019-04-14T23:18:04.477Z [WARNING]: error Building static HTML for pages failed
See our docs page on debugging HTML builds for help https://goo.gl/yL9lND
2019-04-14T23:18:04.503Z [INFO]: 
  64 | 
  65 |     if (data == null || !ClientId || !AppWebDomain || !RedirectUriSignIn || !RedirectUriSignOut) {
> 66 |       throw new Error(this.getCognitoConstants().PARAMETERERROR);
     | ^
  67 |     }
  68 | 
  69 |     this.clientId = ClientId;
�[0m
�[0m  �[0m�[97m�[41mWebpackError�[0m�[37m�[41m:�[0m�[37m�[41m �[0m�[97m�[41mThe parameters: App client Id, App web domain, the redirect URL �[0m  �[0m�[97m�[41mwhen you are signed in and the redirect URL when you are signed out are requir�[0m  �[0m�[97m�[41med.�[0m
�[0m  �[0m
�[0m  �[0m�[90m-�[0m �[0m�[93mCognitoAuth.js�[0m�[90m:�[0m�[93m66�[0m�[37m �[0m�[37mnew CognitoAuth�[0m
�[0m  �[0m  �[0m�[90m[lib]/[amazon-cognito-auth-js]/es/CognitoAuth.js:66:1�[0m
�[0m  �[0m
�[0m  �[0m�[90m-�[0m �[0m�[93mAuth.js�[0m�[90m:�[0m�[93m135�[0m�[37m �[0m�[37mAuthClass../node_modules/@aws-amplify/auth/lib/Auth.js.AuthClass�[0m  �[0m  �[0m�[37m.configure�[0m
�[0m  �[0m  �[0m�[90m[lib]/[@aws-amplify]/auth/lib/Auth.js:135:1�[0m
�[0m  �[0m
�[0m  �[0m�[90m-�[0m �[0m�[93mAmplify.js�[0m�[90m:�[0m�[93m25�[0m�[37m �[0m
�[0m  �[0m  �[0m�[90m[lib]/[@aws-amplify]/core/lib/Amplify.js:25:1�[0m
�[0m  �[0m
�[0m  �[0m
�[0m  �[0m�[90m-�[0m �[0m�[93mAmplify.js�[0m�[90m:�[0m�[93m24�[0m�[37m �[0m�[37mFunction../node_modules/@aws-amplify/core/lib/Amplify.js.Ampli�[0m  �[0m  �[0m�[37mfy.configure�[0m
�[0m  �[0m  �[0m�[90m[lib]/[@aws-amplify]/core/lib/Amplify.js:24:1�[0m
�[0m  �[0m
�[0m  �[0m�[90m-�[0m �[0m�[93mindex.js�[0m�[90m:�[0m�[93m8�[0m�[37m �[0m�[37mModule../src/pages/index.js�[0m
�[0m  �[0m  �[0m�[90mlib/src/pages/index.js:8:9�[0m
�[0m  �[0m
�[0m  �[0m�[90m-�[0m �[0m�[93mbootstrap�[0m�[90m:�[0m�[93m19�[0m�[37m �[0m�[37m__webpack_require__�[0m
�[0m  �[0m  �[0m�[90mlib/webpack/bootstrap:19:1�[0m
�[0m  �[0m
�[0m  �[0m�[90m-�[0m �[0m�[93msync-requires.js�[0m�[90m:�[0m�[93m9�[0m�[37m �[0m�[37mObject../.cache/sync-requires.js�[0m
�[0m  �[0m  �[0m�[90mlib/.cache/sync-requires.js:9:51�[0m
�[0m  �[0m
�[0m  �[0m�[90m-�[0m �[0m�[93mbootstrap�[0m�[90m:�[0m�[93m19�[0m�[37m �[0m�[37m__webpack_require__�[0m
�[0m  �[0m  �[0m�[90mlib/webpack/bootstrap:19:1�[0m
�[0m  �[0m
�[0m  �[0m�[90m-�[0m �[0m�[93mstatic-entry.js�[0m�[90m:�[0m�[93m9�[0m�[37m �[0m�[37mModule../.cache/static-entry.js�[0m
�[0m  �[0m  �[0m�[90mlib/.cache/static-entry.js:9:22�[0m
�[0m  �[0m
�[0m  �[0m�[90m-�[0m �[0m�[93mbootstrap�[0m�[90m:�[0m�[93m19�[0m�[37m �[0m�[37m__webpack_require__�[0m
�[0m  �[0m  �[0m�[90mlib/webpack/bootstrap:19:1�[0m
�[0m  �[0m
�[0m  �[0m�[90m-�[0m �[0m�[93mbootstrap�[0m�[90m:�[0m�[93m83�[0m�[37m �[0m
�[0m  �[0m  �[0m�[90mlib/webpack/bootstrap:83:1�[0m
�[0m  �[0m
�[0m  �[0m
�[0m  �[0m�[90m-�[0m �[0m�[93muniversalModuleDefinition�[0m�[90m:�[0m�[93m3�[0m�[37m �[0m�[37mwebpackUniversalModuleDefinition�[0m
�[0m  �[0m  �[0m�[90mlib/webpack/universalModuleDefinition:3:1�[0m
�[0m  �[0m
�[0m  �[0m�[90m-�[0m �[0m�[93muniversalModuleDefinition�[0m�[90m:�[0m�[93m10�[0m�[37m �[0m�[37mObject.<anonymous>�[0m
�[0m  �[0m  �[0m�[90mlib/webpack/universalModuleDefinition:10:2�[0m
�[0m  �[0m
�[0m  �[0m
�[0m
2019-04-14T23:18:04.576Z [WARNING]: error Command failed with exit code 1.
2019-04-14T23:18:04.578Z [INFO]: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
2019-04-14T23:18:04.581Z [ERROR]: !!! Build failed
2019-04-14T23:18:04.708Z [ERROR]: !!! Non-Zero Exit Code detected
2019-04-14T23:18:04.708Z [INFO]: # Starting environment caching...
2019-04-14T23:18:04.708Z [INFO]: Uploading environment cache artifact...
2019-04-14T23:18:04.754Z [INFO]: # Environment caching completed
Terminating logging...

Why are we not using `withAuthenticator` with gatsby?

The example for React / React Native is very simple using a HOC, but this repo has a more complex setup for Auth, why is that?

See: https://aws-amplify.github.io/docs/js/react#add-auth

Thanks!