Gatsby Starter Blog v2 Netlify deploy does not work #6844
Assignees
Labels
help wanted
Issue with a clear description that the community can help with.
status: confirmed
Issue with steps to reproduce the bug that’s been verified by at least one reviewer.
type: maintenance
An issue or pull request describing a change that isn't a bug, feature or documentation change
Comments
naheller
changed the title
|
I should also add that the build runs successfully on my machine. |
Possibly a caching issue? Try triggering a redeploy in Netlify but disable cache.
|
|
I, too, have been having issues deploying Gatsby v2 to Netlify. I've started with the default starter but edited it. Here is my deploy logs Netlify Deploy Log
3:10:36 PM: Build ready to start
3:10:38 PM: Fetching cached dependencies
3:10:38 PM: Starting to download cache of 254.8KB
3:10:38 PM: Finished downloading cache in 127.614649ms
3:10:38 PM: Starting to extract cache
3:10:38 PM: Failed to fetch cache, continuing with build
3:10:38 PM: Starting to prepare the repo for build
3:10:38 PM: No cached dependencies found. Cloning fresh repo
3:10:38 PM: git clone git@github.com:mrsbeitel/parkshipper
3:10:39 PM: Preparing Git Reference refs/heads/master
3:10:40 PM: Starting build script
3:10:40 PM: Installing dependencies
3:10:41 PM: Downloading and installing node v8.11.3...
3:10:41 PM: Downloading https://nodejs.org/dist/v8.11.3/node-v8.11.3-linux-x64.tar.xz...
3:10:41 PM: #
3:10:41 PM: # 3.3%
3:10:41 PM: #
3:10:41 PM: ######################## 34.8%
3:10:42 PM:
###############
3:10:42 PM: ###################################### 73.8%
3:10:42 PM:
######################################################################## 100.0%
3:10:42 PM: Computing checksum with sha256sum
3:10:42 PM: Checksums matched!
3:10:44 PM: Now using node v8.11.3 (npm v5.6.0)
3:10:44 PM: Attempting ruby version 2.3.6, read from environment
3:10:45 PM: Using ruby version 2.3.6
3:10:46 PM: Using PHP version 5.6
3:10:46 PM: Started restoring cached node modules
3:10:46 PM: Finished restoring cached node modules
3:10:46 PM: Started restoring cached yarn cache
3:10:46 PM: Finished restoring cached yarn cache
3:10:46 PM: Installing yarn at version 1.3.2
3:10:46 PM: Installing Yarn!
3:10:46 PM: > Downloading tarball...
3:10:46 PM: [1/2]: https://yarnpkg.com/downloads/1.3.2/yarn-v1.3.2.tar.gz --> /tmp/yarn.tar.gz.zBQyhr6woR
3:10:46 PM: % Total % Received % Xferd Average Speed Time Time Time Current
3:10:46 PM: Dload Upload Total Spent Left Speed
3:10:46 PM:
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
3:10:46 PM:
100 91 100 91 0 0 805 0 --:--:-- --:--:-- --:--:-- 812
3:10:46 PM:
0 0 0 608 0 0 2016 0 --:--:-- --:--:-- --:--:-- 2016
3:10:46 PM:
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
3:10:47 PM: 1
3:10:47 PM: 00 865k 100 865k 0 0 886k 0 --:--:-- --:--:-- --:--:-- 1367k
3:10:47 PM: [2/2]: https://yarnpkg.com/downloads/1.3.2/yarn-v1.3.2.tar.gz.asc --> /tmp/yarn.tar.gz.zBQyhr6woR.asc
3:10:47 PM:
100 95 100 95 0 0 1933 0 --:--:-- --:--:-- --:--:-- 1933
3:10:47 PM:
0 0 0 612 0 0 4415 0 --:--:-- --:--:-- --:--:-- 4415
3:10:47 PM:
100 1027 100 1027 0 0 5946 0 --:--:-- --:--:-- --:--:-- 5946
3:10:47 PM: > Verifying integrity...
3:10:47 PM: gpg: Signature made Thu 02 Nov 2017 04:44:10 PM UTC using RSA key ID FD2497F5
3:10:47 PM: gpg: Good signature from "Yarn Packaging <yarn@dan.cx>"
3:10:47 PM: gpg: WARNING: This key is not certified with a trusted signature!
3:10:47 PM: gpg: There is no indication that the signature belongs to the owner.
3:10:47 PM: Primary key fingerprint: 72EC F46A 56B4 AD39 C907 BBB7 1646 B01B 86E5 0310
3:10:47 PM: Subkey fingerprint: 6A01 0C51 6600 6599 AA17 F081 46C2 130D FD24 97F5
3:10:47 PM: > GPG signature looks good
3:10:48 PM: > Extracting to ~/.yarn...
3:10:48 PM: > Adding to $PATH...
3:10:48 PM: > We've added the following to your /opt/buildhome/.profile
3:10:48 PM: > If this isn't the profile of your current shell then please add the following to your correct profile:
3:10:48 PM: export PATH="$HOME/.yarn/bin:$HOME/.config/yarn/global/node_modules/.bin:$PATH"
3:10:48 PM:
3:10:48 PM: > Successfully installed Yarn 1.3.2! Please open another terminal where the `yarn` command will now be available.
3:10:48 PM: Installing NPM modules using Yarn version 1.3.2
3:10:49 PM: yarn install v1.3.2
3:10:49 PM: [1/4] Resolving packages...
3:10:51 PM: [2/4] Fetching packages...
3:11:08 PM: info fsevents@1.2.4: The platform "linux" is incompatible with this module.
3:11:08 PM: info "fsevents@1.2.4" is an optional dependency and failed compatibility check. Excluding it from installation.
3:11:09 PM: [3/4] Linking dependencies...
3:11:15 PM: [4/4] Building fresh packages...
3:11:32 PM: success Saved lockfile.
3:11:32 PM: Done in 43.44s.
3:11:32 PM: NPM modules installed using Yarn
3:11:33 PM: Started restoring cached go cache
3:11:33 PM: Finished restoring cached go cache
3:11:33 PM: unset GOOS;
3:11:33 PM: unset GOARCH;
3:11:33 PM: export GOROOT='/opt/buildhome/.gimme/versions/go1.10.linux.amd64';
3:11:33 PM: export PATH="/opt/buildhome/.gimme/versions/go1.10.linux.amd64/bin:${PATH}";
3:11:33 PM: go version >&2;
3:11:33 PM: export GIMME_ENV='/opt/buildhome/.gimme/env/go1.10.linux.amd64.env';
3:11:33 PM: go version go1.10 linux/amd64
3:11:33 PM: Installing missing commands
3:11:33 PM: Verify run directory
3:11:33 PM: Executing user command: gatsby build
3:11:35 PM: success open and validate gatsby-config — 0.009 s
3:11:35 PM: success load plugins — 0.233 s
3:11:36 PM: success onPreInit — 0.224 s
3:11:36 PM: success delete html and css files from previous builds — 0.008 s
3:11:36 PM: success initialize cache — 0.009 s
3:11:36 PM: success copy gatsby files — 0.022 s
3:11:36 PM: success onPreBootstrap — 0.001 s
3:11:36 PM: success source and transform nodes — 0.028 s
3:11:36 PM: success building schema — 0.103 s
3:11:36 PM: success createPages — 0.006 s
3:11:36 PM: success createPagesStatefully — 0.028 s
3:11:36 PM: success onPreExtractQueries — 0.001 s
3:11:36 PM: success update schema — 0.053 s
3:11:36 PM: success extract queries from components — 0.042 s
3:11:36 PM: success run graphql queries — 0.027 s — 7/7 274.19 queries/second
3:11:36 PM: success write out page data — 0.003 s
3:11:36 PM: success write out redirect data — 0.001 s
3:11:36 PM: success onPostBootstrap — 0.001 s
3:11:37 PM: info bootstrap finished - 3.322 s
3:12:00 PM: success Building production JavaScript and CSS bundles — 24.323 s
3:12:01 PM: (node:1622) DeprecationWarning: Tapable.plugin is deprecated. Use new API on `.hooks` instead
3:12:02 PM: error Building static HTML for pages failed
3:12:03 PM: See our docs page on debugging HTML builds for help https://goo.gl/yL9lND
3:12:03 PM: 7 | // Check if module is in cache
3:12:03 PM: 8 | if(installedModules[moduleId]) {
3:12:03 PM: > 9 | return installedModules[moduleId].exports;
3:12:03 PM: | ^
3:12:03 PM: 10 | }
3:12:03 PM: 11 | // Create a new module (and put it into the cache)
3:12:03 PM: 12 | var module = installedModules[moduleId] = {
3:12:03 PM:
3:12:03 PM: WebpackError: TypeError: Promise.map is not a function
3:12:03 PM:
3:12:03 PM: - bootstrap:9 Promise
3:12:03 PM: lib/webpack/bootstrap:9:1
3:12:03 PM:
3:12:03 PM: - static-entry.js:6 initializePromise
3:12:04 PM: lib/.cache/static-entry.js:6:14
3:12:04 PM:
3:12:04 PM:
3:12:04 PM: - bootstrap:5 module.exports
3:12:04 PM: lib/webpack/bootstrap:5:1
3:12:04 PM:
3:12:04 PM: - bootstrap:35 webpack.run
3:12:04 PM: lib/webpack/bootstrap:35:1
3:12:04 PM:
3:12:04 PM:
3:12:04 PM:
3:12:04 PM: - bootstrap:13 AsyncSeriesHook.eval [as callAsync]
3:12:04 PM: eval at create (lib/webpack/bootstrap:13:1
3:12:04 PM:
3:12:04 PM: - bootstrap:24 AsyncSeriesHook.lazyCompileHook [as _callAsync]
3:12:05 PM: lib/webpack/bootstrap:24:1
3:12:05 PM:
3:12:05 PM:
3:12:05 PM:
3:12:05 PM:
3:12:05 PM:
3:12:05 PM: - bootstrap:13 _err0
3:12:05 PM: eval at create (lib/webpack/bootstrap:13:1
3:12:05 PM:
3:12:05 PM: - gatsby-browser-entry.js:2 WebpackAssetsManifest.handleAfterEmit
3:12:05 PM: lib/.cache/gatsby-browser-entry.js:2:1
3:12:05 PM:
3:12:05 PM: - bootstrap:13 AsyncSeriesHook.eval [as callAsync]
3:12:05 PM: eval at create (lib/webpack/bootstrap:13:1
3:12:06 PM:
3:12:06 PM:
3:12:06 PM: Caching artifacts
3:12:06 PM: Started saving node modules
3:12:06 PM: Finished saving node modules
3:12:06 PM: Started saving yarn cache
3:12:06 PM: Finished saving yarn cache
3:12:07 PM: Started saving pip cache
3:12:07 PM: Finished saving pip cache
3:12:07 PM: Started saving emacs cask dependencies
3:12:07 PM: Finished saving emacs cask dependencies
3:12:07 PM: Started saving maven dependencies
3:12:07 PM: Finished saving maven dependencies
3:12:07 PM: Started saving boot dependencies
3:12:07 PM: Finished saving boot dependencies
3:12:08 PM: Started saving go dependencies
3:12:08 PM: Finished saving go dependencies
3:12:08 PM: Cached node version v8.11.3
3:12:08 PM: Error running command: Build script returned non-zero exit code: 1
3:12:08 PM: Failing build: Failed to build site
3:12:08 PM: failed during stage 'building site': Build script returned non-zero exit code: 1
3:12:08 PM: Finished processing build request in 1m30.607343653s |
|
+1 running into the same issues deploying Gatsby Starter Blog v2 to Netlify. Build also runs successfully on my local machine. |
|
@joshbuchea Have you tried the latest beta? Upgrading to the latest beta fixed my problems. |
|
Was able to resolve just now by removing |
|
@naheller are you able to solve this by upgrading to the latest beta? |
Chuloo
added
the
status: needs more info
|
@joshbuchea @DevanB @Chuloo Can ya'll please post the output of |
|
Update: running |
|
Here is the error that I get: And here is the output from running |
|
@agarrharr can you try |
|
Successfully deployed to netlify, included the |
Chuloo
added
type: bug
Chuloo
added
type: maintenance
|
@Chuloo This is the error I get on Netlify with yarn: It looks like |
|
Ok, I got it to work by using yarn.
|
|
It looks like this is caused by the package-lock.json file being out of date, and issues when switching between yarn and npm. The short term fix is to update the package-lock for these starters. Longer term maybe the gatsby cli should ask which package manager you want to use? @KyleAMathews is updating the package-lock for these starters. Edit: related issue #6834 |
|
Implementing #1545 would mean that the package-lock file would be kept up to date automatically. |
pieh
added
the
status: confirmed
This was referenced Sep 7, 2018
|
This is fixed for now, so I'll close this issue |
|
I had the same problem, I just move out I think netlify checks this file first instead |
|
#6834 appears to be broken again (using |
paxcodes
pushed a commit
to paxcodes/portfolio
that referenced
this issue
Sep 4, 2019
Having issues with Netlify build gatsbyjs/gatsby#6844 (comment)
paxcodes
pushed a commit
to paxcodes/portfolio
that referenced
this issue
Sep 4, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
I am unable to deploy Gatsby Starter Blog v2 on Netlify. I have made no changes to the current code. Please see errors below.
Steps to reproduce
Clone down
https://github.com/gatsbyjs/gatsby-starter-blog#v2Initialize git repo with this code
Attempt to deploy via Netlify
Expected result
Site deploys via Netlify
Actual result
Many build errors, primarily around resolving modules. The phrase all errors have in common is
Field 'browser' doesn't contain a valid alias configuration. The topmost error is as follows:I'm happy to share additional errors if that would help.
Environment
File contents (if changed)
gatsby-config.js: N/Apackage.json: N/Agatsby-node.js: N/Agatsby-browser.js: N/Agatsby-ssr.js: N/AThe text was updated successfully, but these errors were encountered: