ryanwiemer / gatsby-starter-gcn Goto Github PK

View Code? Open in Web Editor NEW

512.0 12.0 121.0 2.54 MB

A starter template to build amazing static websites with Gatsby, Contentful and Netlify

Home Page: https://gcn.netlify.app/

License: MIT License

JavaScript 100.00%

gatsby gatsbyjs contentful netlify static static-site blogging react gatsby-starter theme

gatsby-starter-gcn's People

Contributors

Stargazers

Watchers

Forkers

clodal zcei brandonkal fxw ongerit ajeetbpr sparker888 khaledgarbaya vyshnav believelody arcadiaswx sethbaur mandlamag johnmeredith sethlilly montshejohn jordiyahii illucent hyeomans dominiczaq valid dattila23 inflammatorydev janakhpon lukejosten steelwolf180 simonbiggs netmolecz smcgov1 snbasics georotzen aazahrou maryboi eddiewilson jonsch1 stuut cesarhub chris-modica-aws alechemy msq6323013 trendingtechnology richardmckenzie param-harrison yangtech2020 d2denis raccoon-git taixhi jbidani vitaliykononov 9eeky kacoze datahelpdoc stondin matthewcreid callelacouture mayankshubham calvimor celacouture r1q hadissulejmani duncanlhs masteraddy ahmadtahirpk anujsachan1990 koniarek shishak ibenthinkin p-oszkar otarsko wardt0 papistan youlekeji asader dskelton-cos edouardlvdl kerrboniel emmaroland32 buugaaga bdunncompany just1and0 realharshbhatt clovisrodriguez qinghuazhao divyamrastogi brendan-hurley jared-luke ianthonycoder nastybomber avrilpearl co360 tunphraong sneurgaonkar sachiotomita curioustauseef aiclouds parzivalwins dztigeruno smoothmaverick doc22940 shashithej

gatsby-starter-gcn's Issues

webpack absolute path error

Hello!

I build locally (gatsby build) but it is error:

WebpackOptionsValidationError: Invalid configuration object. Webpack has been initialised using a co
nfiguration object that does not match the API schema.

configuration.context: The provided value "e:\!Project\GatsBy\gatsby-starter-gcn" contains exc
lamation mark (!) which is not allowed because it's reserved for loader syntax.
-> The base directory (absolute path!) for resolving the entry option. If output.pathinfo is
set, the included pathinfo is shortened to this directory.
configuration.output.path: The provided value "e:\\!Project\\GatsBy\\gatsby-starter-gcn\\
public" contains exclamation mark (!) which is not allowed because it's reserved for loader syntax.
-> The output directory as absolute path (required).

What is the fail?
Thanks

Improve Spam Protection on Contact Form

This may be a limitation of @netlify but I still see a decent amount of spam even when using the honeypot field. I'm open to any ideas or recommendations to get the number of spam emails down particularly since Netlify only includes 100 email submissions per month on the free tier.

Relevant Links

.env file

I cloned this repo and successfully ran the setup and deployed to Netlify without any issues. However, when I clone the repo I created to a different computer I cannot find a .env file to add my Contentful space_id and access_token. I can hard code it into the gatsby-config.js but that is not ideal. Am I missing something?

failed during stage 'building site'

failed to build with Netlify Deployment From Git (Recommended) method;
what it can be?

failed during stage 'building site': Build script returned non-zero exit code: 1
...

TypeError: Cannot read property 'allContentfulPost' of undefined
- gatsby-node.js:19 graphql.then.result
/opt/build/repo/gatsby-node.js:19:21

Contact form failure

Hi there,
Second time I've hit this problem with the Netlify forms so hopefully it's a quick fix.

I previously had an HTML contact for that was fialing and the original dev kindly added a honeypot. Low and behold the form submissions began to work. I notice you also have a honeypot witihn the contact component but I canot seem to get it working.

My repo is here.
My site on Netlify is here.

Thank you!

Node 12 compatibility

It looks like due to dependency issues the current repo is not compatible with Node 12, however updating the dependencies to the latest seem to fix the compatibility issue.

Error while deploying to netlify

Hey, I followed all the steps on the documentation but I get this error while deploying.
Thanks!

10:49:48 PM: Build ready to start
10:49:50 PM: build-image version: 53a2d5fe9ca22a80747972bf7a83d93509ec503c
10:49:50 PM: buildbot version: 4011bc275ed1e45f93e758dff0bce4fda2a3c46f
10:49:50 PM: Fetching cached dependencies
10:49:50 PM: Starting to download cache of 254.7KB
10:49:50 PM: Finished downloading cache in 135.658971ms
10:49:50 PM: Starting to extract cache
10:49:50 PM: Failed to fetch cache, continuing with build
10:49:50 PM: Starting to prepare the repo for build
10:49:51 PM: No cached dependencies found. Cloning fresh repo
10:49:51 PM: git clone https://github.com/EmilianoCarrillo/emilianocarrillo
10:49:51 PM: Preparing Git Reference refs/heads/master
10:49:52 PM: Starting build script
10:49:52 PM: Installing dependencies
10:49:53 PM: Downloading and installing node v8.15.0...
10:49:53 PM: Downloading https://nodejs.org/dist/v8.15.0/node-v8.15.0-linux-x64.tar.xz...
10:49:53 PM:   1.1%
10:49:53 PM: 
############
10:49:53 PM:                                              17.4%
10:49:53 PM: 
######################
10:49:53 PM: ###########                                         46.3%
10:49:53 PM: #
10:49:53 PM: ##########################################################               83.2%
10:49:53 PM: 
######################################################################## 100.0%
10:49:53 PM: Computing checksum with sha256sum
10:49:53 PM: Checksums matched!
10:49:56 PM: Now using node v8.15.0 (npm v6.4.1)
10:49:56 PM: Attempting ruby version 2.3.6, read from environment
10:49:57 PM: Using ruby version 2.3.6
10:49:57 PM: Using PHP version 5.6
10:49:57 PM: Started restoring cached node modules
10:49:57 PM: Finished restoring cached node modules
10:49:57 PM: Installing NPM modules using NPM version 6.4.1
10:50:45 PM: > [email protected] install /opt/build/repo/node_modules/sharp
10:50:45 PM: > (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)
10:50:45 PM: info
10:50:45 PM:  sharp Detected globally-installed libvips v8.6.2
10:50:46 PM: info sharp Building from source via node-gyp
10:50:47 PM: make: Entering directory `/opt/build/repo/node_modules/sharp/build'
10:50:47 PM:   TOUCH Release/obj.target/libvips-cpp.stamp
10:50:47 PM:   CXX(target) Release/obj.target/sharp/src/common.o
10:50:49 PM:   CXX(target) Release/obj.target/sharp/src/metadata.o
10:50:51 PM:   CXX(target) Release/obj.target/sharp/src/stats.o
10:50:52 PM:   CXX(target) Release/obj.target/sharp/src/operations.o
10:50:55 PM:   CXX(target) Release/obj.target/sharp/src/pipeline.o
10:50:58 PM:   CXX(target) Release/obj.target/sharp/src/sharp.o
10:51:00 PM:   CXX(target) Release/obj.target/sharp/src/utilities.o
10:51:01 PM:   SOLINK_MODULE(target) Release/obj.target/sharp.node
10:51:01 PM:   COPY Release/sharp.node
10:51:01 PM: make: Leaving directory `/opt/build/repo/node_modules/sharp/build'
10:51:03 PM: > [email protected] postinstall /opt/build/repo/node_modules/cwebp-bin
10:51:03 PM: > node lib/install.js
10:51:03 PM:   ✔ cwebp pre-build test passed successfully
10:51:03 PM: > [email protected] postinstall /opt/build/repo/node_modules/mozjpeg
10:51:03 PM: > node lib/install.js
10:51:04 PM:   ⚠ The `/opt/build/repo/node_modules/mozjpeg/vendor/cjpeg` binary doesn't seem to work correctly
10:51:04 PM:   ⚠ mozjpeg pre-build test failed
10:51:04 PM:   ℹ compiling from source
10:51:42 PM:   ✔ mozjpeg built successfully
10:51:42 PM: > [email protected] postinstall /opt/build/repo/node_modules/pngquant-bin
10:51:42 PM: > node lib/install.js
10:51:43 PM:   ✔ pngquant pre-build test passed successfully
10:51:43 PM: > [email protected] postinstall /opt/build/repo/node_modules/styled-components
10:51:43 PM: > node ./scripts/postinstall.js || exit 0
10:51:43 PM: Use styled-components at work? Consider supporting our development efforts at https://opencollective.com/styled-components
10:51:49 PM: npm WARN
10:51:49 PM:  optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents):
10:51:49 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
10:51:49 PM: added 2348 packages from 1266 contributors and audited 30953 packages in 111.438s
10:51:49 PM: found 6 vulnerabilities (5 moderate, 1 high)
10:51:49 PM:   run `npm audit fix` to fix them, or `npm audit` for details
10:51:49 PM: NPM modules installed
10:51:50 PM: Started restoring cached go cache
10:51:50 PM: Finished restoring cached go cache
10:51:50 PM: unset GOOS;
10:51:50 PM: unset GOARCH;
10:51:50 PM: export GOROOT='/opt/buildhome/.gimme/versions/go1.10.linux.amd64';
10:51:50 PM: export PATH="/opt/buildhome/.gimme/versions/go1.10.linux.amd64/bin:${PATH}";
10:51:50 PM: go version >&2;
10:51:50 PM: export GIMME_ENV='/opt/buildhome/.gimme/env/go1.10.linux.amd64.env';
10:51:50 PM: go version go1.10 linux/amd64
10:51:50 PM: Installing missing commands
10:51:50 PM: Verify run directory
10:51:50 PM: Executing user command: gatsby build
10:51:52 PM: success open and validate gatsby-configs — 0.010 s
10:51:53 PM: success load plugins — 0.322 s
10:51:53 PM: success onPreInit — 0.858 s
10:51:53 PM: success delete html and css files from previous builds — 0.091 s
10:51:53 PM: success initialize cache — 0.008 s
10:51:54 PM: success copy gatsby files — 0.155 s
10:51:54 PM: success onPreBootstrap — 0.009 s
10:51:54 PM: Starting to fetch data from Contentful
10:51:54 PM: Fetching default locale
10:51:54 PM: Accessing your Contentful space failed. Perhaps you're offline or the spaceId/accessToken is incorrect.
10:51:54 PM: Try running setting GATSBY_CONTENTFUL_OFFLINE=true to see if we can serve from cache.
10:51:54 PM: Caching artifacts
10:51:54 PM: Started saving node modules
10:51:54 PM: Finished saving node modules
10:51:54 PM: Started saving pip cache
10:51:54 PM: Finished saving pip cache
10:51:54 PM: Started saving emacs cask dependencies
10:51:54 PM: Finished saving emacs cask dependencies
10:51:54 PM: Started saving maven dependencies
10:51:54 PM: Finished saving maven dependencies
10:51:54 PM: Started saving boot dependencies
10:51:54 PM: Finished saving boot dependencies
10:51:54 PM: Started saving go dependencies
10:51:54 PM: Finished saving go dependencies
10:51:54 PM: Cached node version v8.15.0
10:51:54 PM: Error running command: Build script returned non-zero exit code: 1
10:51:55 PM: Failing build: Failed to build site
10:51:55 PM: failed during stage 'building site': Build script returned non-zero exit code: 1
10:51:55 PM: Finished processing build request in 2m4.987595041s

Change post image width

Hi there,
Not a bug but a general "I suck" question... I have tweaked the width of each post successfully but cannot see where to change the width of the images included? As a result the post body width is now wider but all images do not match.

Thanks!
John

Removing Tag Create Build Error

Not sure if this is a bug or I need to RTFM but when removing tags from a previously publsihed post, I get the following build error on Netlify:

TypeError: Cannot read property 'length' of null

I tracked down my changes to me removing a tag from a post due to the post header looking too cramped (it's only one row and does not wrap?).

I can recreate the error just by removing a tag from a post and re-publishing.

In this example, I removed the tag Norway from this post. I then get this build error:

builderror.txt

If I add the tag back in it is fine again.

Build Fails When Changing Existing Content In Contentful

Just adding this here to track it. I appear to see an issue building the site after changing an existing entry in Contentful. For example creating a new Post is fine but changing an existing Post's title will fail to build.

In the meantime I will probably just downgrade to 1.9.209.

gatsbyjs/gatsby#4401

Hot reload keeps refreshing

Hi,

I just started with using you start for a gatsby/contentful blog.
I was able to set-up everythink fine but when I started to make minor change to the post and tag page I had some strange behavior.
The page keeps on refreshing continously as if the HRM keeps on finding a change to update for.
I'm using AWS C9 to code.
I don't know if this error is related to gatsby or the AWS C9.

Any help or tips would be appreciated.

Blurry Images on Desktop

This might well be a mistake on my part configuring Contentful but I get blurry images on desktop browsers. For example:

https://www.archetextur.es/interoperability-is-poorly-defined-and-subsequently-misused/

It seems clear on mobile though?

npm test failure on check-pretty script

When running npm test with a new install of the repo, I'm getting:

npm ERR! [email protected] check-pretty: prettier -l {,src/**/}*.{js,jsx,json,css,scss}
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the [email protected] check-pretty script.

I'm looking into whether this might be an environmental issue (running node on Windows 10).

Contentful API keys

Tried to insert environmental variables into netlify as per Contentful keys (access / space id) however during deployment is drops this error:

Accessing your Contentful space failed. Perhaps you're offline or the spaceId/accessToken is incorrect
Error running command: Build script returned non-zero exit code: 1

Wonder what can be wrong?

Homepage fails to render correctly in Firefox for Mac

I really like this starter framework, it looks like a great combination of technologies. Unfortunately it doesn't seem to render properly in Firefox. Also the contentful attribution doesn't seem to load on the knw.io website.
Here is a screenshot of how it looks in Firefox Quantum. Not really why it is failing in this browser:

Multilingual functionality

Hey Ryan,

Thanks for creating the repo and adding all the instructions for setting things up!
I was wondering if you can think of a way of getting this to work with different contentful locales. I spent a couple of days trying to filter page and post queries for node_locale and switch languages but it's quite tricky. Any ideas or plans of implementing this in the future?

Thanks again!

Update to Gatsby V2

Waiting until Gatsby v2 is officially launched but in the meantime starting work on migrating the code.

List of issues/bugs with Gatsby v2

Google Analytics

Other than putting in my Google analytics ID on Netlify's deployment variable, is there anything else I need to do? I've done that and it doesn't seem that GA is taking. Thanks

TypeError: Cannot read property 'allContentfulPost' of undefined

Hi,

I am getting this error when I'm trying to build Gatsby or even put it into develop mode.

I have tried to use an existing space that already contains content. Could that be an issue? Does it always have to start with a blank space on Contentful?

Thanks

Canonical Link Check

Hi there
I’ve clearly missed something in the config of my site but when running an SEO check for
https://sitechecker.pro/seo-report/https://www.archetextur.es/ i get the canonical link to your demo page at https://gcn.netlify.com/. Where can I reconfigure this to my domain?

Sorry for the dumb question!
J

Redundant meta tags

I noticed this while grepping through the diffs for the version 2 upgrade.
It is not a huge concern because React Helmet handles everything nicely. But since the SEO component handles the meta tags in the Layout component, those lines should probably be removed. I'll leave this here as a reminder for when I find the time to do this down the road.

Error with Image being a null

First of all thanks a lot for the starter! You did a fantastic job on it.

I've started to modify it and play with contentful+netlify integration and everything worked fine but lately when I run gatsby develop there is no error in terminal and everything seems correct but I get nothing rendered because of some error concerning image being null.

I didn't change any logic apart from adding react headroom. Moreover if I change something and push changes to github which triggers netlify build everything is working fine on the server and site is live without any errors. So basically I can't develop locally.

I would much appreciate your help with it! Thanks!

Here is stack trace:

The above error occurred in the <Card> component:
    in Card (at templates/index.js:29)
    in ul (created by Context.Consumer)
    in StyledComponent (created by CardList__List)
    in CardList (at templates/index.js:28)
    in section (created by Context.Consumer)
    in StyledComponent (created by Container__Wrapper)
    in Container (at templates/index.js:26)
    in div (at Layout.js:23)
    in ThemeProvider (at Layout.js:21)
    in div (at Layout.js:13)
    in Template (at templates/index.js:19)
    in Index (created by PageRenderer)
    in PageRenderer (at json-store.js:93)
    in JSONStore (created by EnsureResources)
    in ScrollContext (at root.js:63)
    in RouteUpdates (at root.js:62)
    in EnsureResources (at root.js:60)
    in RouteHandler (created by Root)
    in div (created by FocusHandlerImpl)
    in FocusHandlerImpl (created by Context.Consumer)
    in FocusHandler (created by RouterImpl)
    in RouterImpl (created by LocationProvider)
    in LocationProvider (created by Context.Consumer)
    in Location (created by Context.Consumer)
    in Router (created by Root)
    in Root (at root.js:119)
    in _default (created by HotExported_default)
    in AppContainer (created by HotExported_default)
    in HotExported_default (at app.js:56)

Is there anyway to fix the black favicon?

I tried changing the site icon and the plugin-manifest but I still get the default dark favicon

Unable to build on Netlify - Module not found

When trying to deploy to Netlify I get the following error.

The app runs locally and builds locally. I have also made sure my Netlify settings are correct based on your instructions.

Error:
Module not found: Error: Can't resolve '../components/Container' in '/opt/buil d/repo/src/pages' 8:46:45 AM: resolve '../components/Container' in '/opt/build/repo/src/pages'

Full output:

8:45:27 AM: Build ready to start
8:45:30 AM: build-image version: 84aca9ba39e0ee86ba194760fbfc51a808f62543
8:45:30 AM: buildbot version: ae7eabf6c88cc6c45c19fb821f4b0a1c2a55238d
8:45:30 AM: Fetching cached dependencies
8:45:31 AM: Starting to download cache of 254.8KB
8:45:31 AM: Finished downloading cache in 70.942969ms
8:45:31 AM: Starting to extract cache
8:45:31 AM: Failed to fetch cache, continuing with build
8:45:31 AM: Starting to prepare the repo for build
8:45:31 AM: No cached dependencies found. Cloning fresh repo
8:45:31 AM: git clone https://github.com/marchdoe/spaceman
8:45:32 AM: Preparing Git Reference refs/heads/master
8:45:32 AM: Starting build script
8:45:32 AM: Installing dependencies
8:45:33 AM: Downloading and installing node v8.15.1...
8:45:33 AM: Downloading https://nodejs.org/dist/v8.15.1/node-v8.15.1-linux-x64.tar.xz...
8:45:34 AM:   0.9
8:45:34 AM: %
8:45:34 AM: 
#####################
8:45:34 AM:               29.6%
8:45:34 AM: ######
8:45:34 AM: ##########################                                          45.0%
8:45:34 AM: 
################################################
8:45:34 AM:                66.8%
8:45:34 AM: 
################################################
8:45:34 AM: ######################## 100.0%
8:45:34 AM: Computing checksum with sha256sum
8:45:34 AM: Checksums matched!
8:45:37 AM: Now using node v8.15.1 (npm v6.4.1)
8:45:37 AM: Attempting ruby version 2.3.6, read from environment
8:45:38 AM: Using ruby version 2.3.6
8:45:39 AM: Using PHP version 5.6
8:45:39 AM: Started restoring cached node modules
8:45:39 AM: Finished restoring cached node modules
8:45:39 AM: Started restoring cached yarn cache
8:45:39 AM: Finished restoring cached yarn cache
8:45:39 AM: Installing yarn at version 1.3.2
8:45:39 AM: Installing Yarn!
8:45:39 AM: > Downloading tarball...
8:45:39 AM: [1/2]: https
8:45:39 AM: ://yarnpkg.com/downloads/1.3.2/yarn-v1.3.2.tar.gz --> /tmp/yarn.tar.gz.CIxTMjM6ri
8:45:39 AM:   % Total    % Received % Xferd
8:45:39 AM:   Average Speed   Time    Time     Time  Current
8:45:39 AM:                                  Dload  Upload   Total   Spent    Left  Speed
8:45:39 AM: 
  0     0
8:45:39 AM:  0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
8:45:39 AM: 
100    91  100    91    0
8:45:39 AM:      0    842      0 --:--:-- --:--:-- --:--:--   850
8:45:39 AM: 
  0     0    0   608
8:45:39 AM:  0     0   1609      0 --:--:-- --:--:-- --:--:--  1609
8:45:40 AM: 
100  865k  100  865k    0     0  1153k      0 --:--
8:45:40 AM: :-- --:--:-- --:--:-- 1153k
8:45:40 AM: [2/2]: https://yarnpkg.com/downloads/1
8:45:40 AM: .3.2/yarn-v1.3.2.tar.gz.asc --> /tmp/yarn.tar.gz.CIxTMjM6ri.asc
8:45:40 AM: 
100    95  100    95    0     0    278
8:45:40 AM:     0 --:--:-- --:--:-- --:--:--   278
100    95  100    95    0     0    278      0 --:--:-- --:--:-- --:--:--     0
8:45:40 AM: 
  0     0    0   612    0     0    980
8:45:40 AM:   0 --:--:-- --:--:-- --:--:--   980
8:45:40 AM: 
100  1027  100  1027    0     0
8:45:40 AM:    1551      0 --:--:-- --:--:-- --:--:--  1551
8:45:40 AM: > Verifying integrity...
8:45:40 AM: gpg: Signature made Thu 02 Nov 2017 04:44:10 PM UTC using RSA key ID FD2497F5
8:45:40 AM: gpg: Good signature from "Yarn Packaging <[email protected]>"
8:45:40 AM: gpg: Note: This key has expired!
8:45:40 AM: Primary key fingerprint: 72EC F46A 56B4 AD39 C907  BBB7 1646 B01B 86E5 0310
8:45:40 AM:      Subkey fingerprint: 6A01 0C51 6600 6599 AA17  F081 46C2 130D FD24 97F5
8:45:40 AM: > GPG signature looks good
8:45:40 AM: > Extracting to ~/.yarn...
8:45:41 AM: > Adding to $PATH...
8:45:41 AM: > We've added the following to your /opt/buildhome/.profile
8:45:41 AM: > If this isn't the profile of your current shell then please add the following to your correct profile:
8:45:41 AM: export PATH="$HOME/.yarn/bin:$HOME/.config/yarn/global/node_modules/.bin:$PATH"
8:45:41 AM: 
8:45:41 AM: > Successfully installed Yarn 1.3.2! Please open another terminal where the `yarn` command will now be available.
8:45:42 AM: Installing NPM modules using Yarn version 1.3.2
8:45:43 AM: yarn install v1.3.2
8:45:43 AM: [1/4] Resolving packages...
8:45:44 AM: [2/4] Fetching packages...
8:46:04 AM: info [email protected]: The platform "linux" is incompatible with this module.
8:46:04 AM: info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
8:46:04 AM: [3/4] Linking dependencies...
8:46:04 AM: warning "gatsby > [email protected]" has incorrect peer dependency "graphql@^0.12.0 || ^0.13.0".
8:46:04 AM: warning "gatsby > [email protected]" has incorrect peer dependency "graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0".
8:46:04 AM: warning "gatsby > [email protected]" has incorrect peer dependency "graphql@^0.13.0".
8:46:04 AM: warning "gatsby > mini-css-extract-plugin > schema-utils > [email protected]" has unmet peer dependency "ajv@>=5.0.0".
8:46:04 AM: warning "gatsby-plugin-netlify > [email protected]" has unmet peer dependency "webpack@>=4.4.0".
8:46:04 AM: warning "stylelint > [email protected]" has unmet peer dependency "postcss@>=5.0.0".
8:46:04 AM: warning "stylelint > [email protected]" has unmet peer dependency "postcss@>=5.0.0".
8:46:04 AM: warning "stylelint > [email protected]" has unmet peer dependency "postcss@>=5.0.0".
8:46:04 AM: warning "stylelint > [email protected]" has unmet peer dependency "postcss@>=5.0.0".
8:46:04 AM: warning "stylelint > [email protected]" has unmet peer dependency "postcss@>=5.0.0".
8:46:12 AM: [4/4] Building fresh packages...
8:46:17 AM: Done in 34.11s.
8:46:17 AM: NPM modules installed using Yarn
8:46:17 AM: Started restoring cached go cache
8:46:17 AM: Finished restoring cached go cache
8:46:18 AM: unset GOOS;
8:46:18 AM: unset GOARCH;
8:46:18 AM: export GOROOT='/opt/buildhome/.gimme/versions/go1.10.linux.amd64';
8:46:18 AM: export PATH="/opt/buildhome/.gimme/versions/go1.10.linux.amd64/bin:${PATH}";
8:46:18 AM: go version >&2;
8:46:18 AM: export GIMME_ENV='/opt/buildhome/.gimme/env/go1.10.linux.amd64.env';
8:46:18 AM: go version go1.10 linux/amd64
8:46:18 AM: Installing missing commands
8:46:18 AM: Verify run directory
8:46:18 AM: Executing user command: gatsby build
8:46:21 AM: success open and validate gatsby-configs — 0.012 s
8:46:21 AM: success load plugins — 0.443 s
8:46:22 AM: success onPreInit — 0.892 s
8:46:22 AM: success delete html and css files from previous builds — 0.007 s
8:46:22 AM: success initialize cache — 0.010 s
8:46:22 AM: success copy gatsby files — 0.032 s
8:46:23 AM: success onPreBootstrap — 0.135 s
8:46:23 AM: Starting to fetch data from Contentful
8:46:23 AM: Fetching default locale
8:46:23 AM: default locale is : en-US
8:46:23 AM: contentTypes fetched 5
8:46:23 AM: Updated entries  26
8:46:23 AM: Deleted entries  0
8:46:23 AM: Updated assets  20
8:46:23 AM: Deleted assets  0
8:46:23 AM: Fetch Contentful data: 319.706ms
8:46:23 AM: success source and transform nodes — 0.561 s
8:46:24 AM: success building schema — 0.576 s
8:46:24 AM: success createPages — 0.203 s
8:46:24 AM: success createPagesStatefully — 0.051 s
8:46:24 AM: success onPreExtractQueries — 0.007 s
8:46:24 AM: success update schema — 0.346 s
8:46:24 AM: success extract queries from components — 0.160 s
8:46:25 AM: success run graphql queries — 0.650 s — 30/30 46.28 queries/second
8:46:25 AM: success write out page data — 0.004 s
8:46:25 AM: success write out redirect data — 0.001 s
8:46:25 AM: done generating icons for manifest
8:46:25 AM: success onPostBootstrap — 0.099 s
8:46:25 AM: info bootstrap finished - 7.687 s
8:46:45 AM: error Generating JavaScript bundles failed
8:46:45 AM: 
8:46:45 AM:   Error: ./src/pages/404.js
8:46:45 AM:   Module not found: Error: Can't resolve '../components/Container' in '/opt/buil  d/repo/src/pages'
8:46:45 AM:   resolve '../components/Container' in '/opt/build/repo/src/pages'
8:46:45 AM:     using description file: /opt/build/repo/package.json (relative path: ./src/p  ages)
8:46:45 AM:       Field 'browser' doesn't contain a valid alias configuration
8:46:45 AM:       using description file: /opt/build/repo/package.json (relative path: ./src  /components/Container)
8:46:45 AM:         no extension
8:46:45 AM:           Field 'browser' doesn't contain a valid alias configuration
8:46:45 AM:           /opt/build/repo/src/components/Container doesn't exist
8:46:45 AM:         .mjs
8:46:45 AM:           Field 'browser' doesn't contain a valid alias configuration
8:46:45 AM:           /opt/build/repo/src/components/Container.mjs doesn't exist
8:46:45 AM:         .js
8:46:45 AM:           Field 'browser' doesn't contain a valid alias configuration
8:46:45 AM:           /opt/build/repo/src/components/Container.js doesn't exist
8:46:45 AM:         .jsx
8:46:45 AM:           Field 'browser' doesn't contain a valid alias configuration
8:46:45 AM:           /opt/build/repo/src/components/Container.jsx doesn't exist
8:46:45 AM:         .wasm
8:46:45 AM:           Field 'browser' doesn't contain a valid alias configuration
8:46:46 AM: failed during stage 'building site': Build script returned non-zero exit code: 1
8:46:45 AM:           /opt/build/repo/src/components/Container.wasm doesn't exist
8:46:45 AM:         .json
8:46:45 AM:           Field 'browser' doesn't contain a valid alias configuration
8:46:45 AM:           /opt/build/repo/src/components/Container.json doesn't exist
8:46:46 AM: Shutting down logging, 253 messages pending

Images Downloaded Twice on Mobile

I noticed this while remote debugging on Android Chrome. I am not sure why this is happening but it seems redundant and causes unnecessary HTTP requests.

On the index page of the site the card thumnails fetch and download images that have a width of 1200 pixels on my phone. However, after clicking into a post, the hero image is again downloaded, this time with a width of 900 pixels.

A prefferrable solution would be to only download the 900 pixel version for the card list or reuse the 1200 pixel image for the post pages.

On desktop, it makes sense to fetch the image twice. In my case, an 800 pixel wide image is fetched for the post listing cards and an 1800 pixel wide image is downloaded on the post pages.

However on mobile it seems silly to fetch the image twice especially when the post hero image is smaller than that of the card index.

webpack error

I get this error when building locally,

error Building static HTML for pages failed

See our docs page on debugging HTML builds for help https://goo.gl/yL9lND

59 |
60 | <Link to={/${slug}/}>

61 | <Img fluid={heroImage.fluid} backgroundColor={'#eeeeee'} />
| ^
62 | <Title>{title}</Title>
63 | {publishDate}
64 | <Excerpt

WebpackError: TypeError: Cannot read property 'fluid' of null

Contentful to GitLab

Thank you for writing this and let us use it.

I have followed the instruction and been able to get my site up and running, including the automatic Netlify deployment when I publish something on Contentful.

I am wondering if there is a way to also push content from Contentful to GitLab? I like the idea that I have a copy of my content stored in GitLab. Thank you.

Edit

After playing with it a little bit more, I found that doing gatsby build actually pull Contentful content and then I can push it to GitLab. Is it possible to do this automatically using Netlify deployment?

Explore Comment Options

I am interested in exploring comment options. Perhaps not adding it entirely depending on your thoughts, because then it becomes more than "Gatsby Contentful and Netlify." One option that would likely be useful to people would be building a comment component that matches the theme styles and adding a note to the readme on how to include it on the pages.

After sifting through the various commenting options, I've narrowed it down to two good options:

Commento

This one seems to be a good route for users interested in self-hosting their comment system. There is an open-source docker container available, but there is not really any documentation on the setup process for a self-hosted route. They do have a hosted option available with some documentation available, but their terms are too open for my tastes: https://commento.io/terms

You also give other Commento.io users permission to share your Content on other Commento.io websites and add their own Content to it (aka to reblog your Content) ... Commento has the right to reclaim your username or website’s URL due to prolonged inactivity

Not horrible, but the lack of this requirement and depth of documentation is probably reason enough to go with the small cost of Just Comments.

It is possible that the website URL thing could be an unintended side-effect of lifting it from the WP.com TOS but I wouldn't want a comment system claiming legal ownership of one of my domains!

Just Comments

This one looks really nice and easy to implement. It is well-documented and has some nice features such as JWT to integrate with any authentication system. https://just-comments.com/

The front-end is open sourced, and the backend API is available as a hosted option which comes out to around $0.30/20K comment page views. The styling is barebones but a sane starting point, which is nice because it makes it easy to integrate with a website's theme.

~~Kyle Matthews~~ Oleksii Rudenko wrote a nice piece on how to add it to a Gatsby blog: https://60devs.com/add-comments-to-your-gatsbyjs-blog-within-two-minutes.html

Anyway, I'd be interested to know you throughts and if something like this makes sense for this project.

npm test failure on eslint

The eslint rule is "Disallow shorthand properties that override related longhand properties.".

The test failure is by:
1514df5#diff-c8a07c8225c0af21bdd6c40b67170518R26

More about the eslint rule: https://stylelint.io/user-guide/rules/declaration-block-no-shorthand-property-overrides/

$ npm run test

> [email protected] test /mnt/c/temp/gatsby-starter-gcn
> npm run lint:css && npm run lint:js && npm run check-pretty


> [email protected] lint:css /mnt/c/temp/gatsby-starter-gcn
> stylelint 'src/**/*.js'


src/styles/global.js
 25:5  ✖  Unexpected shorthand "font"   declaration-block-no-shorthand-property-overrides
          after "font-size"

npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! [email protected] lint:css: `stylelint 'src/**/*.js'`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the [email protected] lint:css 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!     /home/user/.npm/_logs/2019-06-15T17_41_23_017Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! [email protected] test: `npm run lint:css && npm run lint:js && npm run check-pretty`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the [email protected] test 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!     /home/user/.npm/_logs/2019-06-15T17_41_23_058Z-debug.log

Use blur up and progressive JPEGs

Not sure exactly how to implement this. The Contentful documentation mentions it is possible to force jpegs to be progressive but doesn't show how. I believe it is ?fl=progressive though.

Also, using blur up for the hero images would probably make the transition less jarring. When I initially deployed the site to Netlify, the contentful images had a waiting time of 1.5 seconds.

Line Wrapping on TagList Component

Minor CSS issue with how tags are wrapping on the TagList component.

PageTitle.js

I am having a hard time figuring out the conditional(ternary) operator 'props.small'. It appears the condition is 'falsy'.

Thanks for the starter.

Failed to deploy on Netlify - Build script returned non-zero exit code: 1

Hi,

The starter works perfectly on local env, but when I try to deploy it on Netlify it gives me this error

3:30:25 PM: Error running command: Build script returned non-zero exit code: 1

Any ideas how to fix that? (I used the latest release)
Thank you

Is there a way to deploy to Github Pages?

Hello, thank you very much for this starter kit. As a beginner, I want to deploy the blog to Github Pages instead of Netlify. Is this a possibility? How would one edit this repo to deploy to Github Pages?

After deleting provided posts, build fails

Drafting, archiving, and deleting provided posts all lead to the below error log (trimmed for readability).

10:19:38 PM: Fetch Contentful data: 438.722ms
10:19:38 PM: success source and transform nodes — 0.563 s
10:19:39 PM: success building schema — 0.516 s
10:19:39 PM: success createPages — 0.065 s
10:19:39 PM: success createPagesStatefully — 0.050 s
10:19:39 PM: success onPreExtractQueries — 0.005 s
10:19:39 PM: success update schema — 0.034 s
10:19:39 PM: error GraphQL Error Encountered 1 error(s):
10:19:39 PM: - Unknown field 'metaDescription' on type 'ContentfulPost'.
10:19:39 PM:       file: /opt/build/repo/src/templates/post.js
10:19:39 PM: Skipping functions preparation step: no functions directory set
10:19:39 PM: Caching artifacts

Found that src/templates/post.js does contain metaDescription with default being the internal content. I've tried 'clear cache and deploy', 'deleting all related tags' to no avail. The only change I've made to Contentful was making 2 locales possible; below are my locale settings.

Locale	Fallback	Include in response	Editing	Required Fields
English - default	None	Enabled	Enabled	Content is required
Korean	English	Disabled	Enabled	Can be published empty

What might be causing the problem? Thank you very much for your help!

Embedded Content - Twitter

Embedded content that appears to render correctly in Contentful (e.g. tweets) do not appear on the built page.

See this post at the bottom, in the Why This Matters section.

For reference, this is how it appears in Contentful:

Images not showing when publishing new blog

When I publish a new blogpost via contentful, netlify builds the new version successfully, but none of the images appear and a JavaScript error is thrown.

Locally (gatsby develop or gatsby build), all images are loading perfectly fine.

When I delete the blogpost, all images show again as before.

I tried different images and blogposts, but until I delete the entry, nothing works.

Contentful Rate Limit - Image imports are failing

Hi, thanks I love the starter, have used it in the past without problems. Today I ran setup with a fresh project and I got a ton of asset upload failures and it seemed to finish but when running gatsby there are a lot of graphql errors about missing images and the site doesn't run properly. Maybe it should be able to handle if images fail more gracefully? I tried running setup again and it doesn't seem to pick off where it left off asking for space id and other info again.

During setup:

The following 4 errors and 12 warnings occurred:

20:16:46 - Rate limit error occurred. Waiting for 1529 ms before retrying...
20:16:49 - Rate limit error occurred. Waiting for 1567 ms before retrying...
20:16:62 - Rate limit error occurred. Waiting for 1511 ms before retrying...
20:16:70 - Rate limit error occurred. Waiting for 1623 ms before retrying...
20:16:80 - Rate limit error occurred. Waiting for 1625 ms before retrying...
20:16:82 - Rate limit error occurred. Waiting for 1670 ms before retrying...
20:17:83 - AssetProcessingTimeout: Asset is taking longer then expected to process.
20:17:21 - AssetProcessingTimeout: Asset is taking longer then expected to process.
20:17:80 - AssetProcessingTimeout: Asset is taking longer then expected to process.
20:17:13 - AssetProcessingTimeout: Asset is taking longer then expected to process.
20:17:54 - Rate limit error occurred. Waiting for 1697 ms before retrying...
20:17:55 - Rate limit error occurred. Waiting for 1675 ms before retrying...
20:17:72 - Rate limit error occurred. Waiting for 1635 ms before retrying...
20:17:73 - Rate limit error occurred. Waiting for 1587 ms before retrying...
20:17:76 - Rate limit error occurred. Waiting for 1691 ms before retrying...
20:17:80 - Rate limit error occurred. Waiting for 1696 ms before retrying...

When running gatsby after setup

error
The GraphQL query from /Users/zanedev/Projects/gatsby-starter-gcn/src/templates/index.js failed.

Errors:
  Cannot read property 'image' of undefined

  GraphQL request (14:11)
  13:           title
  14:           fluid(maxWidth: 1800) {
                ^
  15:             ...GatsbyContentfulFluid_withWebp_noBase64
  ,Cannot read property 'image' of undefined

  GraphQL request (14:11)
  13:           title
  14:           fluid(maxWidth: 1800) {
                ^
  15:             ...GatsbyContentfulFluid_withWebp_noBase64

URL path:
  /
Context:
  {
    "limit": 7,
    "skip": 0,
    "numPages": 3,
    "currentPage": 1
  }
Plugin:
  none
Query:
  query usersZaneProjectsGatsbyStarterGcnSrcTemplatesIndexJs3965247395(
    $skip: Int!
    $limit: Int!
  ) {
    allContentfulPost(sort: {fields: [publishDate], order: DESC}, limit: $limit, skip: $skip) {
      edges {
        node {
          title
          id
          slug
          publishDate(formatString: "MMMM DD, YYYY")
          heroImage {
            title
            fluid(maxWidth: 1800) {
              ...GatsbyContentfulFluid_withWebp_noBase64
            }
          }
          body {
            childMarkdownRemark {
              timeToRead
              html
              excerpt(pruneLength: 80)
            }
          }
        }
      }
    }
  }

  fragment GatsbyContentfulFluid_withWebp_noBase64 on ContentfulFluid {
    aspectRatio
    src
    srcSet
    srcWebp
    srcSetWebp
    sizes
  }

Set static home page and blog urls

Hi,
I am trying to set one page as static home page and the blogs inside a blog page with the following url structure

example.com/blog/page/1 
example.com/blog/page/2
example.com/blog/page/3

I changed the url here:
https://github.com/ryanwiemer/gatsby-starter-gcn/blob/master/gatsby-node.js#L45

but it broke the pagination

Suggestion - change attribution domain

Per the Contentful documentation, they updated the asset domain:
images.contentful.com → images.ctfassets.net
https://www.contentful.com/blog/2017/12/08/change-of-the-contentful-asset-domain/
They just made this change a week or so ago. Changing the url for the attribution link to the ctfassets domain will save a DNS lookup and redirect though the performance improvement will likely be negligable it would make things a bit cleaner.

Posts are added twice

Hey there and thank you very much for your nice starter. So far everything works with with contentful and the whole setup, the only thing I came across is that every post I create in contentufl is added twice.

I checked the querys with the GraphiQL and figured out that each posts exists twice but a different ID

I tired googeling and digging around in contentful and so far I could not find any fix. Does someone has an idea why that happens?

Thank you very much.

Draft content on Contentful showing

I see that draft content on Contentful (posts) is showing up for local gatsby develop. Is this intended?

Async error and GraphQL error

I tried the local install and connected it to my Contentful space. I've confirmed that everything's connected because the content has been created in Contentful (posts, pages, and tags).

When I try to run "gatsby develop" I get the following errors:

error Plugin gatsby-transformer-remark returned an error

Error: /Users/hrashid/Sites/gatsby-starter-gcn/node_modules/gatsby-remark-images-contentful/index.js:25
module.exports = async ({
^
SyntaxError: Unexpected token (

error GraphQL Error Unknown field html on type MarkdownRemark

file: /Users/hrashid/Sites/gatsby-starter-gcn/src/templates/index.js

any idea how to fix this?

allContentfulPage error

I've just downloaded the starter theme and when I attempt to run gatsby develop I get the following errors:

error Cannot read property 'allContentfulPage' of undefined
  TypeError: Cannot read property 'allContentfulPage' of undefined

and

error UNHANDLED REJECTION
TypeError: Cannot read property 'allContentfulPage' of undefined

I only found allContentfulPage in Gatsby-node.js. on lines 118 and 127 but I didn't spot an issue. Any idea what I am doing wrong?

Thanks in advance, Isaac

gatsby-netlify-plugin causes an error

This happens when trying to deploy to netlify. I've followed every instructions.

error Plugin gatsby-plugin-netlify returned an error
4:35:17 PM: 
4:35:17 PM:   Error: Cannot find module '/opt/build/repo/public/stats.json'
4:35:17 PM:   
4:35:17 PM:   - v8-compile-cache.js:159 require
4:35:17 PM:     [repo]/[v8-compile-cache]/v8-compile-cache.js:159:20
4:35:17 PM:   
4:35:17 PM:   - plugin-data.js:65 makePluginData
4:35:17 PM:     [repo]/[gatsby-plugin-netlify]/plugin-data.js:65:15
4:35:17 PM:   
4:35:17 PM:   - gatsby-node.js:71 _callee$
4:35:17 PM:     [repo]/[gatsby-plugin-netlify]/gatsby-node.js:71:51
4:35:17 PM:   
4:35:17 PM:   - gatsby-node.js:101 Object.onPostBuild
4:35:17 PM:     [repo]/[gatsby-plugin-netlify]/gatsby-node.js:101:18
4:35:17 PM:   
4:35:17 PM:   - api-runner-node.js:104 runAPI
4:35:17 PM:     [repo]/[gatsby]/dist/utils/api-runner-node.js:104:37
4:35:17 PM:   
4:35:17 PM:   - api-runner-node.js:173 mapSeries
4:35:17 PM:     [repo]/[gatsby]/dist/utils/api-runner-node.js:173:25
4:35:17 PM:

###Environment:

I've modified it to comply with v2 so i don't think it should matter.

System:
OS: macOS High Sierra 10.13.3
CPU: x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.0.0 - /usr/local/bin/node
Yarn: 1.6.0 - ~/.yarn/bin/yarn
npm: 6.1.0 - /usr/local/bin/npm
Browsers:
Chrome: 67.0.3396.87
Firefox: 57.0.3
Safari: 11.0.3
npmPackages:
gatsby: next => 2.0.0-beta.1
gatsby-image: ^2.0.0-beta.1 => 2.0.0-beta.1
gatsby-link: ^1.6.44 => 1.6.44
gatsby-plugin-canonical-urls: ^1.0.18 => 1.0.18
gatsby-plugin-feed: ^1.3.22 => 1.3.25
gatsby-plugin-google-analytics: ^1.0.31 => 1.0.31
gatsby-plugin-manifest: ^1.0.22 => 1.0.27
gatsby-plugin-netlify: ^1.0.19 => 1.0.21
gatsby-plugin-nprogress: ^1.0.14 => 1.0.14
gatsby-plugin-offline: ^1.0.16 => 1.0.18
gatsby-plugin-react-helmet: ^2.0.11 => 2.0.11
gatsby-plugin-sitemap: ^1.2.23 => 1.2.25
gatsby-plugin-styled-components: ^2.0.11 => 2.0.11
gatsby-plugin-svgr: ^1.0.1 => 1.0.1
gatsby-plugin-typography: ^1.7.19 => 1.7.19
gatsby-remark-prismjs: ^2.0.2 => 2.0.4
gatsby-source-contentful: next => 2.0.1-beta.1
gatsby-source-filesystem: ^1.5.36 => 1.5.39
gatsby-transformer-remark: ^1.7.41 => 1.7.44
gatsby-transformer-sharp: ^2.1.1-beta.1 => 2.1.1-beta.1
npmGlobalPackages:
gatsby-cli: 1.1.58

Netlify Build Command

Hey,
Thanks for setting this up on github. I'm not able to get to the published site(getting a 404 not found). do you have any recommendations for the netlify build command and publish directory?

I 've tried running the build command with npm run build

6:40:13 PM: build-image version: 42bca793ccd33055023c56c4ca8510463a56d317
6:40:13 PM: buildbot version: 3924ed076b0a333c42ff8c2dff3d88014c29564c
6:40:13 PM: Fetching cached dependencies
6:40:13 PM: Starting to download cache of 2.4MB
6:40:13 PM: Finished downloading cache in 254.570989ms
6:40:13 PM: Starting to extract cache
6:40:13 PM: Finished extracting cache in 47.231033ms
6:40:13 PM: Finished fetching cache in 348.818892ms
6:40:13 PM: Starting to prepare the repo for build
6:40:14 PM: Preparing Git Reference refs/heads/master
6:40:14 PM: Starting build script
6:40:14 PM: Installing dependencies
6:40:15 PM: Downloading and installing node v8.12.0...
6:40:16 PM: Downloading https://nodejs.org/dist/v8.12.0/node-v8.12.0-linux-x64.tar.xz...
6:40:16 PM:  0.0
6:40:16 PM: %
6:40:16 PM: #
6:40:16 PM: #########                                                                15.2%
6:40:16 PM: 
######################
6:40:16 PM: ##########################################          89.7%
######################################################################## 100.0%
6:40:16 PM: Computing checksum with sha256sum
6:40:16 PM: Checksums matched!
6:40:18 PM: Now using node v8.12.0 (npm v6.4.1)
6:40:19 PM: Attempting ruby version 2.3.6, read from environment
6:40:20 PM: Using ruby version 2.3.6
6:40:20 PM: Using PHP version 5.6
6:40:20 PM: Started restoring cached node modules
6:40:20 PM: Finished restoring cached node modules
6:40:20 PM: Installing NPM modules using NPM version 6.4.1
6:41:09 PM: > [email protected] install /opt/build/repo/node_modules/sharp
6:41:09 PM: > (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)
6:41:10 PM: info
6:41:10 PM:  sharp Detected globally-installed libvips v8.6.2
6:41:10 PM: info sharp Building from source via node-gyp
6:41:11 PM: make: Entering directory `/opt/build/repo/node_modules/sharp/build'
6:41:11 PM:   TOUCH Release/obj.target/libvips-cpp.stamp
6:41:11 PM:   CXX(target) Release/obj.target/sharp/src/common.o
6:41:14 PM:   CXX(target) Release/obj.target/sharp/src/metadata.o
6:41:15 PM:   CXX(target) Release/obj.target/sharp/src/stats.o
6:41:17 PM:   CXX(target) Release/obj.target/sharp/src/operations.o
6:41:19 PM:   CXX(target) Release/obj.target/sharp/src/pipeline.o
6:41:22 PM:   CXX(target) Release/obj.target/sharp/src/sharp.o
6:41:24 PM:   CXX(target) Release/obj.target/sharp/src/utilities.o
6:41:25 PM:   SOLINK_MODULE(target) Release/obj.target/sharp.node
6:41:25 PM:   COPY Release/sharp.node
6:41:25 PM: make: Leaving directory `/opt/build/repo/node_modules/sharp/build'
6:41:27 PM: > [email protected] postinstall /opt/build/repo/node_modules/cwebp-bin
6:41:27 PM: > node lib/install.js
6:41:27 PM:   ✔ cwebp pre-build test passed successfully
6:41:27 PM: > [email protected] postinstall /opt/build/repo/node_modules/mozjpeg
6:41:27 PM: > node lib/install.js
6:41:28 PM:   ⚠ The `/opt/build/repo/node_modules/mozjpeg/vendor/cjpeg` binary doesn't seem to work correctly
6:41:28 PM:   ⚠ mozjpeg pre-build test failed
6:41:28 PM:   ℹ compiling from source
6:42:08 PM:   ✔ mozjpeg built successfully
6:42:08 PM: > [email protected] postinstall /opt/build/repo/node_modules/pngquant-bin
6:42:08 PM: > node lib/install.js
6:42:09 PM:   ✔ pngquant pre-build test passed successfully
6:42:09 PM: > [email protected] postinstall /opt/build/repo/node_modules/styled-components
6:42:09 PM: > node ./scripts/postinstall.js || exit 0
6:42:09 PM: Use styled-components at work? Consider supporting our development efforts at https://opencollective.com/styled-components
6:42:19 PM: npm WARN
6:42:19 PM:  optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents):
6:42:19 PM: npm WARN
6:42:19 PM: notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
6:42:19 PM: added 2340 packages from 1249 contributors and audited 30939 packages in 118.293s
6:42:19 PM: found 5 moderate severity vulnerabilities
6:42:19 PM:   run `npm audit fix` to fix them, or `npm audit` for details
6:42:20 PM: NPM modules installed
6:42:20 PM: Started restoring cached go cache
6:42:20 PM: Finished restoring cached go cache
6:42:20 PM: unset GOOS;
6:42:20 PM: unset GOARCH;
6:42:20 PM: export GOROOT='/opt/buildhome/.gimme/versions/go1.10.linux.amd64';
6:42:20 PM: export PATH="/opt/buildhome/.gimme/versions/go1.10.linux.amd64/bin:${PATH}";
6:42:20 PM: go version >&2;
6:42:20 PM: export GIMME_ENV='/opt/buildhome/.gimme/env/go1.10.linux.amd64.env';
6:42:20 PM: go version go1.10 linux/amd64
6:42:20 PM: Installing missing commands
6:42:20 PM: Verify run directory
6:42:20 PM: Executing user command: npm run build
6:42:20 PM: > [email protected] build /opt/build/repo
6:42:20 PM: > gatsby build
6:42:22 PM: success open and validate gatsby-configs — 0.014 s
6:42:23 PM: success load plugins — 0.283 s
6:42:23 PM: success onPreInit — 0.758 s
6:42:23 PM: success delete html and css files from previous builds — 0.106 s
6:42:23 PM: success initialize cache — 0.009 s
6:42:24 PM: success copy gatsby files — 0.156 s
6:42:24 PM: success onPreBootstrap — 0.010 s
6:42:24 PM: Starting to fetch data from Contentful
6:42:24 PM: Fetching default locale
6:42:24 PM: default locale is : en-US
6:42:24 PM: contentTypes fetched 3
6:42:24 PM: Updated entries  22
6:42:24 PM: Deleted entries  0
6:42:24 PM: Updated assets  16
6:42:24 PM: Deleted assets  0
6:42:24 PM: Fetch Contentful data: 613.707ms
6:42:24 PM: success source and transform nodes — 0.778 s
6:42:25 PM: success building schema — 0.317 s
6:42:25 PM: success createPages — 0.093 s
6:42:25 PM: success createPagesStatefully — 0.024 s
6:42:25 PM: success onPreExtractQueries — 0.005 s
6:42:25 PM: success update schema — 0.172 s
6:42:25 PM: success extract queries from components — 0.117 s
6:42:26 PM: success run graphql queries — 0.540 s — 30/30 55.75 queries/second
6:42:26 PM: success write out page data — 0.004 s
6:42:26 PM: success write out redirect data — 0.001 s
6:42:26 PM: done generating icons for manifest
6:42:26 PM: success onPostBootstrap — 0.109 s
6:42:26 PM: info bootstrap finished - 5.743 s
6:42:41 PM: success Building production JavaScript and CSS bundles — 14.971 s
6:42:42 PM: success Building static HTML for pages — 1.630 s — 30/30 63.61 pages/second
6:42:43 PM: Generated public/sw.js, which will precache 13 files, totaling 362304 bytes.
6:42:43 PM: info Done building in 22.508 sec
6:42:43 PM: Caching artifacts
6:42:43 PM: Started saving node modules
6:42:43 PM: Finished saving node modules
6:42:43 PM: Started saving pip cache
6:42:43 PM: Finished saving pip cache
6:42:43 PM: Started saving emacs cask dependencies
6:42:43 PM: Finished saving emacs cask dependencies
6:42:43 PM: Started saving maven dependencies
6:42:43 PM: Finished saving maven dependencies
6:42:43 PM: Started saving boot dependencies
6:42:43 PM: Finished saving boot dependencies
6:42:43 PM: Started saving go dependencies
6:42:43 PM: Finished saving go dependencies
6:42:43 PM: Cached node version v8.12.0
6:42:43 PM: Build script success
6:42:43 PM: Starting to deploy site from '/'
6:42:47 PM: Starting post processing
6:42:52 PM: Post processing done
6:42:52 PM: Site is live
6:43:03 PM: Finished processing build request in 2m50.431146692s```

Startup Readme Clarity?

Ryan -- Thanks for creating this, it looks like a really cool project. I followed the setup instructions and it's still rendering your space via the export.json. I tried commenting it out but it's not loading my space. Can you provide some clarity on how I can start loading in my own content and adjusting the starter? I didn't see any issues with similar problems, I'm not sure what I'm missing. 😅

It's building and I've received zero errors. I'm new to Gatsby and GraphQL, so I'm currently playing catchup.

Deleted Contentful post still present in local build

First of all, fantastic job at putting this together Ryan. I'm new to pretty much everything involved here (React, Gatsby, Contenful, Netlify) but this project has helped me understand each of them.

I'm experiencing an issue where I've deleted one of the pre-existing posts ("Sailing Around The Bay") and it still shows in my local build. The live site is updated fine through Netlify.

I've run gatsby develop and gatsby build multiple times to try and 'flush' the change, but it remains.

To confirm, a graphQL query for posts on my local build brings back the following:

{ "data": { "allContentfulPost": { "edges": [ { "node": { "title": "Beach Day", "id": "c46W6F2LB9KK48AoKWGKQWy" } }, { "node": { "title": "A Walk In The Park", "id": "gaDq907enKa8UeKuAWOQG" } }, { "node": { "title": "Sailing Around The Bay", "id": "c2H1mrgshZeQki8UQ2yGq0s" } }, { "node": { "title": "Puppies!", "id": "c3wnBmHFsMg8KAOq2kagiks" } }, { "node": { "title": "Test Post", "id": "c3exNfAvwYg4IKK426sQS4S" } } ] } } }

If I run gatsby build then a public/sailing-around-the-bay folder is created with an index.html inside. As expected, if I open the local build then the home page displays the deleted blog post.

If I run gatsby develop then the folder remains but the index.html disappears. If I open the development site on the localhost URL then the home page still displays the deleted blog post.

Any ideas?

npm test failing on v2 branch

Using gatsby 2 and the gatsby 2 branch and getting the following when running npm test, not sure what the actual error is. Seems like deprecation warnings only.

$ npm test

> [email protected] test /Users/user/Projects/project
> npm run lint:css && npm run lint:js && npm run check-pretty


> [email protected] lint:css /Users/user/Projects/project
> stylelint 'src/**/*.js'


> [email protected] lint:js /Users/user/Projects/project
> eslint --ext .js,.jsx .

(node:7837) [ESLINT_LEGACY_OBJECT_REST_SPREAD] DeprecationWarning: The 'parserOptions.ecmaFeatures.experimentalObjectRestSpread' option is deprecated. Use 'parserOptions.ecmaVersion' instead. (found in "standard-react")
(node:7837) [ESLINT_LEGACY_OBJECT_REST_SPREAD] DeprecationWarning: The 'parserOptions.ecmaFeatures.experimentalObjectRestSpread' option is deprecated. Use 'parserOptions.ecmaVersion' instead. (found in "node_modules/eslint-config-standard-jsx/index.js")
(node:7837) [ESLINT_LEGACY_OBJECT_REST_SPREAD] DeprecationWarning: The 'parserOptions.ecmaFeatures.experimentalObjectRestSpread' option is deprecated. Use 'parserOptions.ecmaVersion' instead. (found in "standard")

> [email protected] check-pretty /Users/user/Projects/project
> prettier -l {,src/**/}*.{js,jsx,json,css,scss}

src/components/Card.js
src/components/TagList.js
src/pages/index.js
src/templates/tag.js
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] check-pretty: `prettier -l {,src/**/}*.{js,jsx,json,css,scss}`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] check-pretty 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!     /Users/user/.npm/_logs/2018-08-24T03_06_04_998Z-debug.log
npm ERR! Test failed.  See above for more details.

Pagination on index and tags pages

Would love to see an example on how to do this.