Describe the bug
On running npm run start compilation fails with below errors
ERROR in ./src/pages/DashBoard.js
Module not found: Error: Can't resolve '../aws-exports'
ERROR in ./src/pages/index.js
Module not found: Error: Can't resolve '../aws-exports'
To Reproduce
Steps to reproduce the behavior:
git clone git@github.com:antstackio/lanyard.git
cd lanyard
npm install
npm run start
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
subratas-MBP ~/workspace/lanyard master npm run start
> lanyard@0.1.0 start /Users/subratamazumder/workspace/lanyard
> npm run develop
> lanyard@0.1.0 develop /Users/subratamazumder/workspace/lanyard
> gatsby develop
success open and validate gatsby-configs - 0.053 s
success load plugins - 1.378 s
success onPreInit - 0.011 s
success initialize cache - 0.010 s
success copy gatsby files - 0.077 s
success onPreBootstrap - 0.010 s
success source and transform nodes - 0.379 s
warn There are conflicting field types in your data.
If you have explicitly defined a type for those fields, you can safely ignore this warning message.
Otherwise, Gatsby will omit those fields from the GraphQL schema.
If you know all field types in advance, the best strategy is to explicitly define them with the `createTypes` action,
and skip inference with the `@dontInfer` directive.
TestJson.speakers:
- type: [object]
value: [ { designation: 'Solutions Architect at Amazon (USA)', externalLink:
'https://www.linkedin.com/in/gregbulmash/', firstName: 'Greg', lastName: 'Bulmash', profilePicture: 'greg_bulmash.jpg'
} ]
source: File "src/data/test.json"
- type: string
success building schema - 0.238 s
success createPages - 0.002 s
success createPagesStatefully - 0.065 s
success onPreExtractQueries - 0.004 s
success update schema - 0.040 s
success extract queries from components - 6.546 s
success write out requires - 0.008 s
success write out redirect data - 0.003 s
success Build manifest and related icons - 0.333 s
success onPostBootstrap - 0.344 s
⠀
info bootstrap finished - 13.581 s
⠀
success run static queries - 1.409 s — 7/7 4.99 queries/second
success run page queries - 0.473 s — 13/13 28.54 queries/second
success Generating image thumbnails — 113/113 - 19.062 s
Browserslist: caniuse-lite is outdated. Please run next command `yarn upgrade`
Browserslist: caniuse-lite is outdated. Please run next command `yarn upgrade`
ERROR Failed to compile with 2 errors 4:38:38 PM
⠀
This relative module was not found:
⠀
* ../aws-exports in ./src/pages/DashBoard.js, ./src/pages/index.js
✖ 「wdm」:
ERROR in ./src/pages/DashBoard.js
Module not found: Error: Can't resolve '../aws-exports' in '/Users/subratamazumder/workspace/lanyard/src/pages'
@ ./src/pages/DashBoard.js 29:0-39 30:18-27
@ ./.cache/sync-requires.js
@ ./.cache/app.js
@ multi ./node_modules/event-source-polyfill/src/eventsource.js
(webpack)-hot-middleware/client.js?path=/__webpack_hmr&reload=true&overlay=false ./.cache/app
ERROR in ./src/pages/index.js
Module not found: Error: Can't resolve '../aws-exports' in '/Users/subratamazumder/workspace/lanyard/src/pages'
@ ./src/pages/index.js 20:0-39 21:18-27
@ ./.cache/sync-requires.js
@ ./.cache/app.js
ℹ 「wdm」: Failed to compile.
Desktop (please complete the following information):
OS: [e.g. iOS] MacOS Catalina
Browser [e.g. chrome, safari]
Version [e.g. 22]
Smartphone (please complete the following information):
Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]
Additional context
It seems aws-exports.js is not checked in.
If this is intentional then readme needs update to suggest what are the dependent configuration needed to run it in local.
Describe the bug On running
npm run start
compilation fails with below errorsTo Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
Screenshots
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context It seems aws-exports.js is not checked in.
If this is intentional then readme needs update to suggest what are the dependent configuration needed to run it in local.