gatsbyjs / gatsby

The best React-based framework with performance, scalability and security built in.
https://www.gatsbyjs.com
MIT License
55.27k stars 10.31k forks source link

AWS Amplify build failing without error message #25025

Closed jaencarrodine closed 4 years ago

jaencarrodine commented 4 years ago

Description

I am attempting to deploy to AWS amplify but the build is failing but not producing an error message.

this is the last bit of the build log:

`- couldn't fulfill desired order of chunk group(s) component---src-pages-app-js, component---src-pages-quiz-js

Steps to reproduce

the full project is located here: https://github.com/jaencarrodine/gatsby-port the problem occurs when attempting to deploy on amplify but not when running gatsby develop

Expected result

The project should deploy successfully or provide an error message(I think)

Actual result

build failed without error message

Environment

System: OS: Windows 10 10.0.18362 CPU: (4) x64 Intel(R) Core(TM) i5-7300U CPU @ 2.60GHz Binaries: Node: 12.6.0 - C:\Program Files\nodejs\node.EXE npm: 6.9.0 - C:\Program Files\nodejs\npm.CMD Languages: Python: 3.7.7 Browsers: Edge: 44.18362.449.0 npmPackages: gatsby: ^2.23.3 => 2.23.3 gatsby-image: ^2.4.5 => 2.4.5 gatsby-plugin-manifest: ^2.4.9 => 2.4.9 gatsby-plugin-offline: ^3.2.7 => 3.2.7 gatsby-plugin-react-helmet: ^3.3.2 => 3.3.2 gatsby-plugin-sass: ^2.3.3 => 2.3.3 gatsby-plugin-sharp: ^2.6.9 => 2.6.9 gatsby-source-filesystem: ^2.3.8 => 2.3.8 gatsby-transformer-sharp: ^2.5.3 => 2.5.3 npmGlobalPackages: gatsby-cli: 2.12.45

jaencarrodine commented 4 years ago

I tried to deploy on netlify just to test it out and now I'm getting the following error: 11:31:27 AM: failed Building static HTML for pages - 5.038s 11:31:27 AM: 11:31:27 AM: 11:31:27 AM: error Building static HTML failed 11:31:27 AM: 11:31:27 AM: 11:31:27 AM: 11:31:27 AM: WebpackError: Invariant failed 11:31:27 AM: 11:31:27 AM: - build-html.js:110 doBuildPages 11:31:27 AM: [repo]/[gatsby]/dist/commands/build-html.js:110:24 11:31:27 AM: 11:31:27 AM: 11:31:27 AM: 11:31:27 AM: not finished Generating image thumbnails - 35.136s 11:31:27 AM: npm 11:31:27 AM: ERR! 11:31:27 AM: code ELIFECYCLE 11:31:27 AM: npm 11:31:27 AM: ERR! errno 11:31:27 AM: 1 11:31:27 AM: npm 11:31:27 AM: ERR! gatsby-starter-default@0.1.0 build:gatsby build 11:31:27 AM: npm ERR! Exit status 1 11:31:27 AM: npm ERR! 11:31:27 AM: npm ERR! Failed at the gatsby-starter-default@0.1.0 build script. 11:31:27 AM: npm ERR! This is probably not a problem with npm. There is likely additional logging output above. 11:31:27 AM: npm 11:31:27 AM: ERR! A complete log of this run can be found in: 11:31:27 AM: npm ERR! /opt/buildhome/.npm/_logs/2020-06-16T15_31_27_747Z-debug.log 11:31:27 AM: ​ 11:31:27 AM: ┌─────────────────────────────┐ 11:31:27 AM: │ "build.command" failed │ 11:31:27 AM: └─────────────────────────────┘ 11:31:27 AM: ​ 11:31:27 AM: Error message 11:31:27 AM: Command failed with exit code 1: npm run build 11:31:27 AM: ​ 11:31:27 AM: Error location 11:31:27 AM: In Build command from settings: 11:31:27 AM: npm run build 11:31:27 AM: ​ 11:31:27 AM: Resolved config 11:31:27 AM: build: 11:31:27 AM: command: npm run build 11:31:27 AM: publish: /opt/build/repo/build 11:31:27 AM: Caching artifacts 11:31:27 AM: Started saving node modules 11:31:27 AM: Finished saving node modules 11:31:27 AM: Started saving build plugins 11:31:27 AM: Finished saving build plugins 11:31:27 AM: Started saving pip cache 11:31:28 AM: Finished saving pip cache 11:31:28 AM: Started saving emacs cask dependencies 11:31:28 AM: Finished saving emacs cask dependencies 11:31:28 AM: Started saving maven dependencies 11:31:28 AM: Finished saving maven dependencies 11:31:28 AM: Started saving boot dependencies 11:31:28 AM: Finished saving boot dependencies 11:31:28 AM: Started saving go dependencies 11:31:28 AM: Finished saving go dependencies 11:31:32 AM: Error running command: Build script returned non-zero exit code: 1 11:31:32 AM: Failing build: Failed to build site 11:31:32 AM: Finished processing build request in 3m50.072549967s

any help is appreciated! thanks

jaencarrodine commented 4 years ago

I figured it out. had to change my build settings to the following. it was automatically using "build" as the base directory instead of "public" for some reason. `version: 0.1 frontend: phases: preBuild: commands: