jlengstorf / netlify-plugin-gatsby-cache Goto Github PK

JavaScript 100.00%

netlify-plugin-gatsby-cache's Introduction

Netlify Build Plugin: Persist the Gatsby Cache Between Builds

Persist the Gatsby cache between Netlify builds for huge build speed improvements! ⚡️

Note: The functionality in this plugin is now available in the Essential Gatsby build plugin. Check out Essential Gatsby for additional framework-specific functionality on Netlify, including Gatsby Functions. If you choose to install it, you should remove this plugin first.

Usage

Currently, there are two ways to install this plugin on your application:

Installing from Netlify UI

One-click install to add this to your Gatsby site

Installing from your project's code

You can also install it manually using netlify.toml. If you want to know more about file-based configuration on Netlify, click here.

Add the following lines to your project's netlify.toml file:

[build]
  publish = "public"

[[plugins]]
  package = "netlify-plugin-gatsby-cache"

Note: The [[plugins]] line is required for each plugin, even if you have other plugins in your netlify.toml file already.

How does it work?

This plugin determines the location of your .cache folder by looking at the publish folder configured for Netlify deployment. This means that if your Gatsby site successfully deploys, it will be cached as well with no config required! 🎉

How much of a difference does this plugin make in build times?

Each Gatsby site is different, so build times vary widely between them, but one common slowdown in Gatsby builds is processing and transforming images. Gatsby is smart enough to check if these transformations have already been done and skip them, but in order to get that benefit in a build pipeline (e.g. Netlify) the public and .cache directories need to be preserved between builds. That’s what this plugin does!

	No Cache	Cache	Savings
* 231 GraphQL queries * 1,871 images * 224 pages	293207ms (build log)	72835ms (build log)	75%
* 5 GraphQL queries * No image processing * 32 pages	22072ms (build log)	15543ms (build log)	30%

tl;dr: Repeat builds with lots of images will be much faster. With few or no images, the difference will be there, but it won’t be as pronounced.

Want to learn how to create your own Netlify Build Plugins?

Check out Sarah Drasner’s excellent tutorial!

netlify-plugin-gatsby-cache's People

Contributors

Stargazers

Watchers

Forkers

juhosa future-foundry davidwells knpwrs antonandresen davidosomething edm00se samouss anthonykasabian karlrombauts duktiga-havet mallonenogueira lucis mmiller42 hartantothio math4youbyusgroupillinois rstavchansky iq-scm

netlify-plugin-gatsby-cache's Issues

Some users report performance issues

Some users report that this Build plugin makes builds slower instead of faster.

I personally have not encountered this issue: this plugin makes my builds faster. Reasons why builds might be slower could include though:

writing/reading and upload/downloading the cached public and .cache directories takes more time than it saves
a bug in utils.cache

To be able to fix this problem, I would need to reproduce it first though either:

by reproducing it myself
by having someone else point to a Deploy that exhibits this behavior.

@dsoaress you interacted on the following issue: netlify/build#1125, do you have a Deploy that exhibits this behavior by any chance?

@marisamorby, is there any chance you found some Deploys that do?

How does this interact with gatsby-plugin-netlify-cache?

I currently use this plugin on my site -
https://www.gatsbyjs.org/packages/gatsby-plugin-netlify-cache/

It appears to do the same thing on paper - does this plugin differ somehow?

Builds fail with WebpackError relating to a Gatsby image plugin

When I enable this plugin in Netlify config UI, builds consistently fails at:
const imageSEO = frontmatter.image.childImageSharp.fluid.src
WebpackError: TypeError: Cannot read property 'childImageSharp' of null
(see full output below)

The build succeeds the 1st time and fails each subsequent time. This indicates to me that something about the cache is not quite right.

Without this plugin netlify builds and publishes, no problem.

Perhaps relevant: locally, when I would get this error, I would have to run gatsby clean (or delete .cache folder). Then dev+builds work.

Thanks for any insight!

6:22:36 PM: Build ready to start
6:22:38 PM: build-image version: 3571f0130496395a23bffe9820bc78b4f73a6234
6:22:38 PM: build-image tag: v3.7.0
6:22:38 PM: buildbot version: c8ebd612d11de8df807ee80082ae1ebcb899414f
6:22:38 PM: Fetching cached dependencies
6:22:38 PM: Starting to download cache of 269.7MB
6:22:39 PM: Finished downloading cache in 1.649367079s
6:22:39 PM: Starting to extract cache
6:22:50 PM: Finished extracting cache in 10.654367029s
6:22:50 PM: Finished fetching cache in 12.421319728s
6:22:50 PM: Starting to prepare the repo for build
6:22:51 PM: Preparing Git Reference pull/52/head
6:22:51 PM: Parsing package.json dependencies
6:22:52 PM: Different publish path detected, going to use the one specified in the Netlify configuration file: 'public' versus 'public/' in the Netlify UI
6:22:52 PM: Different functions path detected, going to use the one specified in the Netlify configuration file: 'netlify/functions' versus '' in the Netlify UI
6:22:53 PM: Starting build script
6:22:53 PM: Installing dependencies
6:22:53 PM: Python version set to 2.7
6:22:53 PM: Started restoring cached node version
6:22:56 PM: Finished restoring cached node version
6:22:57 PM: v12.18.0 is already installed.
6:22:58 PM: Now using node v12.18.0 (npm v6.14.4)
6:22:58 PM: Started restoring cached build plugins
6:22:58 PM: Finished restoring cached build plugins
6:22:58 PM: Attempting ruby version 2.7.1, read from environment
6:23:00 PM: Using ruby version 2.7.1
6:23:00 PM: Using PHP version 5.6
6:23:00 PM: Started restoring cached yarn cache
6:23:00 PM: Finished restoring cached yarn cache
6:23:00 PM: Started restoring cached node modules
6:23:00 PM: Finished restoring cached node modules
6:23:01 PM: Installing NPM modules using Yarn version 1.22.4
6:23:01 PM: yarn install v1.22.4
6:23:01 PM: [1/4] Resolving packages...
6:23:02 PM: success Already up-to-date.
6:23:02 PM: Done in 1.27s.
6:23:02 PM: NPM modules installed using Yarn
6:23:03 PM: Started restoring cached go cache
6:23:03 PM: Finished restoring cached go cache
6:23:03 PM: go version go1.14.4 linux/amd64
6:23:03 PM: go version go1.14.4 linux/amd64
6:23:03 PM: Installing missing commands
6:23:03 PM: Verify run directory
6:23:04 PM: 
6:23:04 PM: ────────────────────────────────────────────────────────────────
6:23:04 PM:   Netlify Build                                                 
6:23:04 PM: ────────────────────────────────────────────────────────────────
6:23:04 PM: 
6:23:04 PM: ❯ Version
6:23:04 PM:   @netlify/build 9.10.2
6:23:04 PM: 
6:23:04 PM: ❯ Flags
6:23:04 PM:   apiHost: api.netlify.com
6:23:04 PM:   cacheDir: /opt/build/cache
6:23:04 PM:   deployId: 6052ab5c2406a3000770869c
6:23:04 PM:   mode: buildbot
6:23:04 PM:   testOpts:
6:23:04 PM:     silentLingeringProcesses: ''
6:23:04 PM: 
6:23:04 PM: ❯ Current directory
6:23:04 PM:   /opt/build/repo
6:23:04 PM: 
6:23:04 PM: ❯ Config file
6:23:04 PM:   No config file was defined: using default values.
6:23:04 PM: 
6:23:04 PM: ❯ Context
6:23:04 PM:   deploy-preview
6:23:05 PM: 
6:23:05 PM: ❯ Loading plugins
6:23:05 PM:    - [email protected] from Netlify app
6:23:05 PM: 
6:23:05 PM: ────────────────────────────────────────────────────────────────
6:23:05 PM:   1. onPreBuild command from netlify-plugin-gatsby-cache        
6:23:05 PM: ────────────────────────────────────────────────────────────────
6:23:05 PM: 
6:23:06 PM: Found a Gatsby cache. We’re about to go FAST. ⚡️
6:23:06 PM: 
6:23:06 PM: (netlify-plugin-gatsby-cache onPreBuild completed in 1.1s)
6:23:06 PM: 
6:23:06 PM: ────────────────────────────────────────────────────────────────
6:23:06 PM:   2. Build command from Netlify app                             
6:23:06 PM: ────────────────────────────────────────────────────────────────
6:23:06 PM: 
6:23:06 PM: $ yarn build
6:23:06 PM: yarn run v1.22.4
6:23:06 PM: $ gatsby build
6:23:10 PM: success open and validate gatsby-configs - 0.116s
6:23:12 PM: success load plugins - 1.757s
6:23:12 PM: success onPreInit - 0.047s
6:23:12 PM: success delete html and css files from previous builds - 0.011s
6:23:12 PM: success initialize cache - 0.004s
6:23:12 PM: success copy gatsby files - 0.052s
6:23:12 PM: success onPreBootstrap - 0.015s
6:23:12 PM: success createSchemaCustomization - 0.022s
6:23:12 PM:  > Data Loaded contact.cn.md
6:23:12 PM: success Checking for changed pages - 0.000s
6:23:12 PM: success source and transform nodes - 0.251s
6:23:13 PM: success building schema - 0.750s
6:23:13 PM: info Total nodes: 206, SitePage nodes: 32 (use --verbose for breakdown)
6:23:13 PM: success createPages - 0.129s
6:23:13 PM: success Checking for changed pages - 0.000s
6:23:13 PM: success createPagesStatefully - 0.118s
6:23:13 PM: success Cleaning up stale page-data - 0.003s
6:23:13 PM: success update schema - 0.039s
6:23:13 PM: success onPreExtractQueries - 0.001s
6:23:18 PM: success extract queries from components - 4.955s
6:23:18 PM: success write out redirect data - 0.001s
6:23:18 PM: success Build manifest and related icons - 0.201s
6:23:18 PM: success onPostBootstrap - 0.210s
6:23:18 PM: info bootstrap finished - 12.027s
6:23:18 PM: success run static queries - 0.033s - 1/1 29.89/s
6:23:18 PM: success run page queries - 0.072s - 13/13 181.26/s
6:23:18 PM: success write out requires - 0.004s
6:23:28 PM: 
6:23:28 PM: gatsby-plugin-purgecss: Only processing  /opt/build/repo/src/components/all.sass
6:23:46 PM: warning "export 'convertNumberSkeletonToNumberFormatOptions' was not found in 'intl-messageformat-parser'
warning "export 'parseDateTimeSkeleton' was not found in 'intl-messageformat-parser'
warning "export 'parseDateTimeSkeleton' was not found in 'intl-messageformat-parser'
success Building production JavaScript and CSS bundles - 27.223s
6:23:46 PM: 
6:23:46 PM: gatsby-plugin-purgecss:
6:23:46 PM:  Previous CSS Size: 245.71 KB
6:23:46 PM:  New CSS Size: 96.06 KB (-60.90%)
6:23:46 PM:  Removed ~149.65 KB of CSS
6:23:46 PM: 
6:23:50 PM: success Building HTML renderer - 4.106s
6:23:51 PM: failed Building static HTML for pages - 0.738s
6:23:51 PM: error Building static HTML failed for path "/cn/contact/"
6:23:51 PM: 
6:23:51 PM:   212 |     const image = dataMarkdown.frontmatter.image
6:23:51 PM:   213 |     const { frontmatter } = dataMarkdown
6:23:51 PM: > 214 |     const imageSEO = frontmatter.image.childImageSharp.fluid.src
6:23:51 PM:       |                                        ^
6:23:51 PM:   215 |     return (
6:23:51 PM:   216 |       <Layout
6:23:51 PM:   217 |         className="container"
6:23:51 PM: 
6:23:51 PM:   WebpackError: TypeError: Cannot read property 'childImageSharp' of null
6:23:51 PM:   
6:23:51 PM:   - contacts.js:214 
6:23:51 PM:     src/templates/contacts.js:214:40
6:23:51 PM:   
6:23:51 PM: 
6:23:51 PM: error Command failed with exit code 1.
6:23:51 PM: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
6:23:51 PM: 
6:23:51 PM: ────────────────────────────────────────────────────────────────
6:23:51 PM:   "build.command" failed                                        
6:23:51 PM: ────────────────────────────────────────────────────────────────
6:23:51 PM: 
6:23:51 PM:   Error message
6:23:51 PM:   Command failed with exit code 1: yarn build
6:23:51 PM: 
6:23:51 PM:   Error location
6:23:51 PM:   In Build command from Netlify app:
6:23:51 PM:   yarn build
6:23:51 PM: 
6:23:51 PM:   Resolved config
6:23:51 PM:   build:
6:23:51 PM:     command: yarn build
6:23:51 PM:     commandOrigin: ui
6:23:51 PM:     environment:
6:23:51 PM:       - DOMAIN_NAME
6:23:51 PM:       - GATSBY_GTAG_GA_MEASUREMENT_ID
6:23:51 PM:       - GATSBY_SQUARE_ACCESS_TOKEN
6:23:51 PM:       - GATSBY_SQUARE_API_ENDPOINT
6:23:51 PM:       - GATSBY_SQUARE_APPLICATION_ID
6:23:51 PM:       - GATSBY_SQUARE_LOCATION_ADDR
6:23:51 PM:       - GATSBY_SQUARE_LOCATION_ID
6:23:51 PM:       - REVIEW_ID
6:23:51 PM:     functions: /opt/build/repo/netlify/functions
6:23:51 PM:     publish: /opt/build/repo/public
6:23:51 PM:   plugins:
6:23:51 PM:     - inputs: {}
6:23:51 PM:       origin: ui
6:23:51 PM:       package: netlify-plugin-gatsby-cache
6:23:51 PM: Caching artifacts
6:23:51 PM: Started saving node modules
6:23:51 PM: Finished saving node modules
6:23:51 PM: Started saving build plugins
6:23:51 PM: Finished saving build plugins
6:23:51 PM: Started saving yarn cache
6:23:51 PM: Finished saving yarn cache
6:23:51 PM: Started saving pip cache
6:23:51 PM: Finished saving pip cache
6:23:51 PM: Started saving emacs cask dependencies
6:23:52 PM: Finished saving emacs cask dependencies
6:23:52 PM: Started saving maven dependencies
6:23:52 PM: Finished saving maven dependencies
6:23:52 PM: Started saving boot dependencies
6:23:52 PM: Finished saving boot dependencies
6:23:52 PM: Started saving rust rustup cache
6:23:52 PM: Finished saving rust rustup cache
6:23:52 PM: Started saving go dependencies
6:23:52 PM: Finished saving go dependencies
6:23:52 PM: Build failed due to a user error: Build script returned non-zero exit code: 2
6:23:52 PM: Failing build: Failed to build site
6:23:52 PM: Failed during stage 'building site': Build script returned non-zero exit code: 2
6:23:52 PM: Finished processing build request in 1m13.968020503s

TypeError: Cannot read property 'build' of undefined

Trying out the plugin on Netlify. Not sure if I am missing something simple or something else deeper going on here.

8:17:35 PM: Build ready to start
8:17:37 PM: build-image version: 2dbd444fcdce00cf06325060a8238d5ae3e86774
8:17:37 PM: build-image tag: v3.3.7
8:17:37 PM: buildbot version: 10926ec3478dd6c0bfc84e15d24de329bb1b357f
8:17:37 PM: Fetching cached dependencies
8:17:37 PM: Starting to download cache of 254.9KB
8:17:37 PM: Finished downloading cache in 106.309483ms
8:17:37 PM: Starting to extract cache
8:17:37 PM: Failed to fetch cache, continuing with build
8:17:37 PM: Starting to prepare the repo for build
8:17:38 PM: No cached dependencies found. Cloning fresh repo
8:17:38 PM: git clone https://github.com/UWHealth/gatsby-starter-gcn
8:17:39 PM: Preparing Git Reference refs/heads/test
8:17:40 PM: Starting build script
8:17:40 PM: Installing dependencies
8:17:41 PM: v10.19.0 is already installed.
8:17:42 PM: Now using node v10.19.0 (npm v6.13.4)
8:17:42 PM: Attempting ruby version 2.6.2, read from environment
8:17:44 PM: Using ruby version 2.6.2
8:17:45 PM: Using PHP version 5.6
8:17:45 PM: Started restoring cached node modules
8:17:45 PM: Finished restoring cached node modules
8:17:45 PM: Installing NPM modules using NPM version 6.13.4
8:18:45 PM: > [email protected] install /opt/build/repo/node_modules/sharp
8:18:45 PM: > (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)
8:18:46 PM: info
8:18:46 PM: sharp Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.8.1/libvips-8.8.1-linux-x64.tar.gz
8:18:48 PM: > [email protected] postinstall /opt/build/repo/node_modules/core-js
8:18:48 PM: > node -e "try{require('./postinstall')}catch(e){}"
8:18:49 PM: Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
8:18:49 PM: The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
8:18:49 PM: > https://opencollective.com/core-js
8:18:49 PM: > https://www.patreon.com/zloirock
8:18:49 PM: Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
8:18:49 PM: > [email protected] postinstall /opt/build/repo/node_modules/core-js-pure
8:18:49 PM: > node -e "try{require('./postinstall')}catch(e){}"
8:18:49 PM: > [email protected] postinstall /opt/build/repo/node_modules/gatsby-telemetry
8:18:49 PM: > node src/postinstall.js || true
8:18:49 PM: > [email protected] postinstall /opt/build/repo/node_modules/cwebp-bin
8:18:49 PM: > node lib/install.js
8:18:50 PM: ✔ cwebp pre-build test passed successfully
8:18:50 PM: > [email protected] postinstall /opt/build/repo/node_modules/mozjpeg
8:18:50 PM: > node lib/install.js
8:18:51 PM: ✔ mozjpeg pre-build test passed successfully
8:18:51 PM: > [email protected] postinstall /opt/build/repo/node_modules/pngquant-bin
8:18:51 PM: > node lib/install.js
8:18:51 PM: ✔ pngquant pre-build test passed successfully
8:18:51 PM: > [email protected] postinstall /opt/build/repo/node_modules/gatsby/node_modules/gatsby-cli
8:18:51 PM: > node scripts/postinstall.js
8:18:52 PM: > [email protected] postinstall /opt/build/repo/node_modules/gatsby
8:18:52 PM: > node scripts/postinstall.js
8:18:56 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents):
8:18:56 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
8:18:56 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/chokidar/node_modules/fsevents):
8:18:56 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
8:18:56 PM: added 2912 packages from 1550 contributors and audited 34147 packages in 70.215s
8:19:00 PM: 114 packages are looking for funding
8:19:00 PM: run npm fund for details
8:19:00 PM: found 131 vulnerabilities (78 low, 25 moderate, 28 high)
8:19:00 PM: run npm audit fix to fix them, or npm audit for details
8:19:00 PM: NPM modules installed
8:19:00 PM: Started restoring cached go cache
8:19:00 PM: Finished restoring cached go cache
8:19:00 PM: unset GOOS;
8:19:00 PM: unset GOARCH;
8:19:00 PM: export GOROOT='/opt/buildhome/.gimme/versions/go1.12.linux.amd64';
8:19:00 PM: export PATH="/opt/buildhome/.gimme/versions/go1.12.linux.amd64/bin:${PATH}";
8:19:00 PM: go version >&2;
8:19:00 PM: export GIMME_ENV='/opt/buildhome/.gimme/env/go1.12.linux.amd64.env';
8:19:00 PM: go version go1.12 linux/amd64
8:19:00 PM: Installing missing commands
8:19:00 PM: Verify run directory
8:19:04 PM: Resolved Netlify Build version tag "latest" to "0.1.112"
8:19:04 PM: Netlify Build not installed. Installing Netlify Build version 0.1.112
8:19:23 PM: npm WARN deprecated [email protected]: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
8:19:33 PM: /opt/buildhome/.nvm/versions/node/v12.16.1/bin/netlify-build -> /opt/buildhome/.nvm/versions/node/v12.16.1/lib/node_modules/@netlify/build/src/core/bin.js
8:19:34 PM: > [email protected] postinstall /opt/buildhome/.nvm/versions/node/v12.16.1/lib/node_modules/@netlify/build/node_modules/babel-runtime/node_modules/core-js
8:19:34 PM: > node -e "try{require('./postinstall')}catch(e){}"
8:19:34 PM: > [email protected] postinstall /opt/buildhome/.nvm/versions/node/v12.16.1/lib/node_modules/@netlify/build/node_modules/core-js
8:19:34 PM: > node -e "try{require('./postinstall')}catch(e){}"
8:19:34 PM: + @netlify/[email protected]
8:19:34 PM: added 580 packages from 309 contributors in 29.394s
8:19:35 PM: Starting Netlify Build...
8:19:38 PM:
8:19:38 PM: ❯ Starting Netlify Build v0.1.112
8:19:38 PM: https://github.com/netlify/build
8:19:38 PM:
8:19:38 PM: ❯ Flags
8:19:38 PM: siteId: a49ad1a6-0175-4463-8047-b0226814537a
8:19:38 PM:
8:19:38 PM: ❯ Current directory
8:19:38 PM: /opt/build/repo
8:19:38 PM:
8:19:38 PM: ❯ Config file
8:19:38 PM: /opt/build/repo/netlify.toml
8:19:38 PM:
8:19:38 PM: ❯ Context
8:19:38 PM: production
8:19:38 PM:
8:19:40 PM: ❯ Loading plugins
8:19:40 PM: - [email protected]
8:19:40 PM:
8:19:40 PM: ❯ Running Netlify Build Lifecycle
8:19:40 PM: Found 2 commands. Let's do this!
8:19:40 PM:
8:19:40 PM: ┌────────────────────────────────────────────────────────────────┐
8:19:40 PM: │ 1. Running onPreBuild command from netlify-plugin-gatsby-cache │
8:19:40 PM: └────────────────────────────────────────────────────────────────┘
8:19:40 PM:
8:19:40 PM:
8:19:40 PM: ┌─────────────────────────────────────────────────────┐
8:19:40 PM: │ Plugin "netlify-plugin-gatsby-cache" internal error │
8:19:40 PM: └─────────────────────────────────────────────────────┘
8:19:40 PM:
8:19:40 PM: ❯ Error message
8:19:40 PM: TypeError: Cannot read property 'build' of undefined
8:19:40 PM:
8:19:40 PM: ❯ Plugin details
8:19:40 PM: ID: netlify-plugin-gatsby-cache
8:19:40 PM: Version: 0.1.2
8:19:40 PM: Repository: git+https://github.com/jlengstorf/netlify-plugin-gatsby-cache.git
8:19:40 PM: npm link: https://www.npmjs.com/package/netlify-plugin-gatsby-cache
8:19:40 PM: Report issues: https://github.com/jlengstorf/netlify-plugin-gatsby-cache/issues
8:19:40 PM:
8:19:40 PM: ❯ Error location
8:19:40 PM: In "onPreBuild" event in npm package "netlify-plugin-gatsby-cache"
8:19:40 PM: at getNetlifyCacheDirs (/opt/build/repo/node_modules/netlify-plugin-gatsby-cache/index.js:6:41)
8:19:40 PM: at preBuild (/opt/build/repo/node_modules/netlify-plugin-gatsby-cache/index.js:25:11)
8:19:40 PM: at Object.run (/opt/buildhome/.nvm/versions/node/v12.16.1/lib/node_modules/@netlify/build/src/plugins/child/main.js:82:9)
8:19:40 PM: at handleEvent (/opt/buildhome/.nvm/versions/node/v12.16.1/lib/node_modules/@netlify/build/src/plugins/child/main.js:63:43)
8:19:40 PM: at getEventsFromParent (/opt/buildhome/.nvm/versions/node/v12.16.1/lib/node_modules/@netlify/build/src/plugins/child/main.js:59:61)
8:19:40 PM: at process.on (/opt/buildhome/.nvm/versions/node/v12.16.1/lib/node_modules/@netlify/build/src/plugins/ipc.js:80:15)
8:19:40 PM: at process.emit (events.js:198:13)
8:19:40 PM: at emit (internal/child_process.js:832:12)
8:19:40 PM: at process._tickCallback (internal/process/next_tick.js:63:19)
8:19:40 PM:
8:19:41 PM: Caching artifacts
8:19:41 PM: Started saving node modules
8:19:41 PM: Finished saving node modules
8:19:41 PM: Started saving pip cache
8:19:41 PM: Finished saving pip cache
8:19:41 PM: Started saving emacs cask dependencies
8:19:41 PM: Finished saving emacs cask dependencies
8:19:41 PM: Started saving maven dependencies
8:19:41 PM: Finished saving maven dependencies
8:19:41 PM: Started saving boot dependencies
8:19:41 PM: Finished saving boot dependencies
8:19:41 PM: Started saving go dependencies
8:19:41 PM: Finished saving go dependencies
8:19:48 PM: Error running command: Build script returned non-zero exit code: 1
8:19:48 PM: Failing build: Failed to build site
8:19:49 PM: failed during stage 'building site': Build script returned non-zero exit code: 1
8:19:49 PM: Finished processing build request in 2m11.438131119s

build failing

Following is the error I am getting while deploying with this plugin. I have added this plugin in netlify.toml

Build failures

I'm not sure if this is a Gatsby issue, a netlify build issue, or this plugin, but I'm now seeing errors like this on cache enabled builds:

I have tried it without this plugin and it works fine. I've also tried it without netlify builds beta enabled and it works fine.

Local builds with and without .cache also work fine.

9:47:40 AM: failed Building production JavaScript and CSS bundles - 66.915s
9:47:40 AM: 
9:47:40 AM: error Generating JavaScript bundles failed
9:47:40 AM: Can't resolve '../../../public/static/d/210650851.json' in '/opt/build/repo/src/components/ProductPage'
9:47:40 AM: 
9:47:40 AM: 
9:47:40 AM: error Generating JavaScript bundles failed
9:47:40 AM: Can't resolve '../../public/static/d/2417117884.json' in '/opt/build/repo/src/components'
9:47:40 AM: 
9:47:40 AM: error Generating JavaScript bundles failed
9:47:40 AM: Can't resolve '../../public/static/d/2804179359.json' in '/opt/build/repo/src/components'
9:47:40 AM: 
9:47:40 AM: error Generating JavaScript bundles failed
9:47:40 AM: Can't resolve '../../public/static/d/905240021.json' in '/opt/build/repo/src/components'

Relevant gatsby deps:

    "gatsby": "^2.21.7",
    "gatsby-image": "^2.4.0",
    "gatsby-plugin-canonical-urls": "^2.3.0",
    "gatsby-plugin-manifest": "^2.4.1",
    "gatsby-plugin-material-ui": "^2.1.8",
    "gatsby-plugin-offline": "^2.2.0",
    "gatsby-plugin-react-helmet": "^3.3.0",
    "gatsby-plugin-remove-fingerprints": "^0.0.2",
    "gatsby-plugin-sharp": "^2.6.0",
    "gatsby-plugin-webpack-bundle-analyzer": "^1.0.5",
    "gatsby-source-contentful": "^2.3.1",
    "gatsby-source-elasticsearch": "^0.1.0",
    "gatsby-source-filesystem": "^2.3.0",
    "gatsby-transformer-remark": "^2.8.3",
    "gatsby-transformer-sharp": "^2.5.0",

Full build log below

9:45:22 AM: Build ready to start
9:45:24 AM: build-image version: 2dbd444fcdce00cf06325060a8238d5ae3e86774
9:45:24 AM: build-image tag: v3.3.7
9:45:24 AM: buildbot version: d305548225ac57bb00eb5a596b0b8674e76a4681
9:45:24 AM: Fetching cached dependencies
9:45:24 AM: Starting to download cache of 350.7MB
9:45:33 AM: Finished downloading cache in 8.465062079s
9:45:33 AM: Starting to extract cache
9:45:57 AM: Finished extracting cache in 24.094433922s
9:45:57 AM: Finished fetching cache in 32.69641939s
9:45:57 AM: Starting to prepare the repo for build
9:45:58 AM: Preparing Git Reference refs/heads/prod
9:45:59 AM: Different publish path detected, going to use the one specified in the Netlify configuration file: 'build' versus 'public' in the Netlify UI
9:45:59 AM: Different functions path detected, going to use the one specified in the Netlify configuration file: 'functions/dist' versus '' in the Netlify UI
9:45:59 AM: Different build command detected, going to use the one specified in the Netlify configuration file: 'npm run build' versus 'yarn build' in the Netlify UI
9:45:59 AM: Creating functions prep folder
9:45:59 AM: Starting build script
9:45:59 AM: Installing dependencies
9:46:00 AM: Started restoring cached node version
9:46:05 AM: Finished restoring cached node version
9:46:05 AM: Attempting node version '10.16.0 ' from .nvmrc
9:46:06 AM: v10.16.0 is already installed.
9:46:06 AM: Now using node v10.16.0 (npm v6.9.0)
9:46:06 AM: Attempting ruby version 2.6.2, read from environment
9:46:08 AM: Using ruby version 2.6.2
9:46:08 AM: Using PHP version 5.6
9:46:08 AM: Started restoring cached node modules
9:46:08 AM: Finished restoring cached node modules
9:46:08 AM: Started restoring cached go cache
9:46:08 AM: Finished restoring cached go cache
9:46:08 AM: unset GOOS;
9:46:08 AM: unset GOARCH;
9:46:08 AM: export GOROOT='/opt/buildhome/.gimme/versions/go1.12.linux.amd64';
9:46:08 AM: export PATH="/opt/buildhome/.gimme/versions/go1.12.linux.amd64/bin:${PATH}";
9:46:08 AM: go version >&2;
9:46:08 AM: export GIMME_ENV='/opt/buildhome/.gimme/env/go1.12.linux.amd64.env';
9:46:09 AM: go version go1.12 linux/amd64
9:46:09 AM: Installing missing commands
9:46:09 AM: Verify run directory
9:46:10 AM: 
9:46:10 AM: ┌─────────────────────────────┐
9:46:10 AM: │        Netlify Build        │
9:46:10 AM: └─────────────────────────────┘
9:46:10 AM: 
9:46:10 AM: ❯ Version
9:46:10 AM:   @netlify/build 0.4.11
9:46:10 AM: 
9:46:10 AM: ❯ Flags
9:46:10 AM:   mode: buildbot
9:46:10 AM: 
9:46:10 AM: ❯ Current directory
9:46:10 AM:   /opt/build/repo
9:46:10 AM: 
9:46:10 AM: ❯ Config file
9:46:10 AM:   /opt/build/repo/netlify.toml
9:46:10 AM: 
9:46:10 AM: ❯ Context
9:46:10 AM:   production
9:46:12 AM: 
9:46:12 AM: ❯ Loading plugins
9:46:12 AM:    - [email protected]
9:46:12 AM: 
9:46:12 AM: ┌───────────────────────────────────────────────────────────┐
9:46:12 AM: │ 1. onPreBuild command from @netlify/plugin-functions-core │
9:46:12 AM: └───────────────────────────────────────────────────────────┘
9:46:12 AM: 
9:46:12 AM: 
9:46:12 AM: (@netlify/plugin-functions-core onPreBuild completed in 6ms)
9:46:12 AM: 
9:46:12 AM: ┌────────────────────────────────────────────────────────┐
9:46:12 AM: │ 2. onPreBuild command from netlify-plugin-gatsby-cache │
9:46:12 AM: └────────────────────────────────────────────────────────┘
9:46:12 AM: 
9:46:18 AM: Found a Gatsby cache. We’re about to go FAST. ⚡️
9:46:18 AM: 
9:46:18 AM: (netlify-plugin-gatsby-cache onPreBuild completed in 5.4s)
9:46:18 AM: 
9:46:18 AM: ┌────────────────────────────────────┐
9:46:18 AM: │ 3. build.command from netlify.toml │
9:46:18 AM: └────────────────────────────────────┘
9:46:18 AM: 
9:46:18 AM: $ npm run build
9:46:18 AM: > [email protected] build /opt/build/repo
9:46:18 AM: > gatsby build --prefix-paths && netlify-lambda build functions/src
9:46:22 AM: 
9:46:22 AM: success open and validate gatsby-configs - 0.180s
9:46:24 AM: 
9:46:24 AM: success load plugins - 2.343s
9:46:24 AM: 
9:46:24 AM: success onPreInit - 0.015s
9:46:24 AM: 
9:46:24 AM: success delete html and css files from previous builds - 0.018s
9:46:24 AM: 
9:46:24 AM: success initialize cache - 0.008s
9:46:24 AM: 
9:46:24 AM: success copy gatsby files - 0.056s
9:46:24 AM: 
9:46:24 AM: success onPreBootstrap - 0.010s
9:46:24 AM: 
9:46:24 AM: success createSchemaCustomization - 0.014s
9:46:26 AM: 
9:46:26 AM: Successfully processed 571 modelresult documents
9:46:26 AM: 
9:46:26 AM: Starting to fetch data from Contentful
9:46:26 AM: 
9:46:26 AM: info Fetching default locale
9:46:26 AM: info default locale is: en-US
9:46:26 AM: info contentTypes fetched 24
9:46:26 AM: 
9:46:26 AM: 
9:46:26 AM: info Updated entries 47
9:46:26 AM: 
9:46:26 AM: 
9:46:26 AM: info Deleted entries 0
9:46:26 AM: 
9:46:26 AM: 
9:46:26 AM: info Updated assets 26
9:46:26 AM: 
9:46:26 AM: 
9:46:26 AM: info Deleted assets 0
9:46:26 AM: 
9:46:26 AM: 
9:46:26 AM: Fetch Contentful data: 896.994ms
9:46:26 AM: 
9:46:26 AM: Restricted field found for ContentType Product and field id. Prefixing with contentful.
9:46:27 AM: 
9:46:27 AM: success source and transform nodes - 2.763s
9:46:30 AM: 
9:46:30 AM: success building schema - 2.713s
9:46:32 AM: 
9:46:32 AM: success createPages - 2.236s
9:46:32 AM: success createPagesStatefully - 0.078s
9:46:32 AM: success onPreExtractQueries - 0.001s
9:46:32 AM: success update schema - 0.244s
9:46:33 AM: success extract queries from components - 0.679s
9:46:33 AM: success write out requires - 0.016s
9:46:33 AM: 
9:46:33 AM: success write out redirect data - 0.001s
9:46:33 AM: success onPostBootstrap - 0.000s
9:46:33 AM: ⠀
9:46:33 AM: 
9:46:33 AM: info bootstrap finished - 14.654 s
9:46:33 AM: 
9:46:33 AM: ⠀
9:47:30 AM: 
9:47:30 AM: warning Browserslist: caniuse-lite is outdated. Please run next command `npm update`
9:47:40 AM: failed Building production JavaScript and CSS bundles - 66.915s
9:47:40 AM: 
9:47:40 AM: error Generating JavaScript bundles failed
9:47:40 AM: Can't resolve '../../../public/static/d/210650851.json' in '/opt/build/repo/src/components/ProductPage'
9:47:40 AM: 
9:47:40 AM: 
9:47:40 AM: error Generating JavaScript bundles failed
9:47:40 AM: Can't resolve '../../public/static/d/2417117884.json' in '/opt/build/repo/src/components'
9:47:40 AM: 
9:47:40 AM: error Generating JavaScript bundles failed
9:47:40 AM: Can't resolve '../../public/static/d/2804179359.json' in '/opt/build/repo/src/components'
9:47:40 AM: 
9:47:40 AM: error Generating JavaScript bundles failed
9:47:40 AM: Can't resolve '../../public/static/d/905240021.json' in '/opt/build/repo/src/components'
9:47:40 AM: not finished run queries - 67.064s
9:47:40 AM: npm ERR! code ELIFECYCLE
9:47:40 AM: npm
9:47:40 AM: ERR! errno 1
9:47:40 AM: npm
9:47:40 AM: ERR! [email protected] build: `gatsby build --prefix-paths && netlify-lambda build functions/src`
9:47:40 AM: npm
9:47:40 AM: ERR! Exit status 1
9:47:40 AM: npm
9:47:40 AM:  ERR!
9:47:40 AM: npm ERR!
9:47:40 AM:  Failed at the [email protected] build script.
9:47:40 AM: npm ERR!
9:47:40 AM:  This is probably not a problem with npm. There is likely additional logging output above.
9:47:40 AM: npm
9:47:40 AM:  ERR! A complete log of this run can be found in:
9:47:40 AM: npm
9:47:40 AM: ERR!     /opt/buildhome/.npm/_logs/2020-05-05T07_47_40_546Z-debug.log
9:47:40 AM: 
9:47:40 AM: ┌─────────────────────────────┐
9:47:40 AM: │        Build failed         │
9:47:40 AM: └─────────────────────────────┘
9:47:40 AM: 
9:47:40 AM:   Error message
9:47:40 AM:   Command failed with exit code 1: npm run build
9:47:40 AM: 
9:47:40 AM:   Error location
9:47:40 AM:   In build.command from netlify.toml:
9:47:40 AM:   npm run build
9:47:40 AM: 
9:47:40 AM: Caching artifacts
9:47:40 AM: Started saving node modules
9:47:40 AM: Finished saving node modules
9:47:40 AM: Started saving pip cache
9:47:40 AM: Finished saving pip cache
9:47:40 AM: Started saving emacs cask dependencies
9:47:40 AM: Finished saving emacs cask dependencies
9:47:40 AM: Started saving maven dependencies
9:47:40 AM: Finished saving maven dependencies
9:47:40 AM: Started saving boot dependencies
9:47:40 AM: Finished saving boot dependencies
9:47:40 AM: Started saving go dependencies
9:47:40 AM: Finished saving go dependencies
9:47:40 AM: Error running command: Build script returned non-zero exit code: 1
9:47:40 AM: Failing build: Failed to build site
9:47:40 AM: failed during stage 'building site': Build script returned non-zero exit code: 1
9:47:41 AM: Finished processing build request in 2m16.3461734s

specify alternate cache location

The typical build cache location (/.cache) is not in the publish location (/public)
https://www.gatsbyjs.org/docs/gatsby-project-structure/

how might one configure this?

Plugin "netlify-plugin-gatsby-cache" internal error

11:39:38 PM：构建准备开始 11:39:40 PM：构建映像版本：3031d4c9e432fd7016f6279fc9ad706f9205d845 11:39:40 PM：构建图像标记：v3.3.17 11:39:40 PM：buildbot版本：1f35b3abd6e2bf5230d8edf68072840fdec1513f 11:39:40 PM：获取缓存的依赖项 11:39:40 PM：开始下载24.2MB的缓存 11:39:40 PM：225.743114ms完成下载缓存 11:39:40 PM：开始提取缓存 11:39:40 PM：在265.676305ms中完成提取缓存 11:39:40 PM：499.480418ms完成获取缓存 11:39:40 PM：开始准备构建仓库 11:39:41 PM：准备Git参考refs / heads / master 11:39:42 PM：开始构建脚本 11:39:42 PM：安装依赖项 11:39:42 PM：Python版本设置为2.7 11:39:43 PM：v12.18.0已安装。 11:39:44 PM：现在使用节点v12.18.0（npm v6.14.4） 11:39:44 PM：开始还原缓存的构建插件 11:39:44 PM：完成还原缓存的构建插件 11:39:44 PM：尝试使用Ruby 2.7.1版，从环境中读取 11:39:45 PM：使用ruby版本2.7.1 11:39:46 PM：使用PHP 5.6 11:39:46 PM：5.2已安装。 11:39:46 PM：使用Swift版本5.2 11:39:46 PM：开始还原缓存的go缓存 11:39:46 PM：完成还原缓存的go缓存 11:39:46 PM：go版本go1.14.4 linux / amd64 11:39:46 PM：go版本go1.14.4 linux / amd64 11:39:46 PM：安装缺少的命令 11:39:46 PM：验证运行目录晚上11:39:47： 11:39:47 PM：┌──────────────┐ 11:39:47 PM：│Netlify构建│ 11:39:47 PM：└──────────────┘ 晚上11:39:47： 11:39:47 PM：❯版本 11:39:47 PM：@ netlify /内部版本2.0.10 晚上11:39:47： 11:39:47 PM：❯旗帜 11:39:47 PM：deployId：5ef4c539418978000837693c 11:39:47 PM：模式：buildbot 晚上11:39:47： 11:39:47 PM：❯当前目录 11:39:47 PM：/ opt / build / repo 晚上11:39:47： 11:39:47 PM：❯配置文件 11:39:47 PM：未定义配置文件：使用默认值。晚上11:39:47： 11:39:47 PM：❯内容 11:39:47 PM：生产晚上11:39:47： 11:39:47 PM：❯正在加载插件 11:39:47 PM：-Netlify应用中的netlify-plugin-a11y @ 0.0.12 11:39:47 PM：-Netlify应用中的netlify-plugin-amp-server-side-rendering @ 1.0.2 11:39:47 PM：- 来自Netlify应用的netlify-plugin-gatsby-cache @ 0.3.0 11:39:47 PM：- 来自Netlify应用程序的netlify-plugin-html-validate @ 0.1.1 11:39:47 PM：- 来自Netlify应用的netlify-plugin-image-optim @ 0.3.0 11:39:47 PM：- 来自Netlify应用程序的netlify-plugin-minify-html @ 0.2.3 晚上11:39:48： 11:39:48 PM：┌──────────────────────────────── ────────────┐ 11:39:48 PM：│1.来自netlify-plugin-gatsby-cache的onPreBuild命令│ 11:39:48 PM：└──────────────────────────────── ────────────┘ 晚上11:39:48：晚上11:39:49： 11:39:49 PM：┌──────────────────────────────── ──────────┐ 11:39:49 PM：│插件“ netlify-plugin-gatsby-cache”内部错误│ 11:39:49 PM：└──────────────────────────────── ──────────┘ 晚上11:39:49： 11:39:49 PM：错误消息 11:39:49 PM：错误：无法缓存/ opt / build / repo，因为它是当前目录（/ opt / build / repo）或父目录晚上11:39:49： 11:39:49 PM：插件详细信息 11:39:49 PM：包裹：netlify-plugin-gatsby-cache 11:39:49 PM：版本：0.3.0 11:39:49 PM：信息库：git + https：//github.com/jlengstorf/netlify-plugin-gatsby-cache.git 11:39:49 PM：npm链接：https://www.npmjs.com/package/netlify-plugin-gatsby-cache 11:39:49 PM：报告问题：https://github.com/jlengstorf/netlify-plugin-gatsby-cache/issues 晚上11:39:49： 11:39:49 PM：错误位置 11:39:49 PM：来自Netlify应用程序的“ netlify-plugin-gatsby-cache”中的“ onPreBuild”事件 11:39:49 PM：在checkSrcPath（/opt/buildhome/.netlify-build-nvm/versions/node/v12.16.3/lib/node_modules/@netlify/build/node_modules/@netlify/cache-utils/src/ path.js：32：11） 11:39:49 PM：在getSrcPath（/opt/buildhome/.netlify-build-nvm/versions/node/v12.16.3/lib/node_modules/@netlify/build/node_modules/@netlify/cache-utils/src/ path.js：18：3） 11:39:49 PM：在parsePath（/opt/buildhome/.netlify-build-nvm/versions/node/v12.16.3/lib/node_modules/@netlify/build/node_modules/@netlify/cache-utils/src/ path.js：9：19） 11:39:49 PM：在restoreOne（/opt/buildhome/.netlify-build-nvm/versions/node/v12.16.3/lib/node_modules/@netlify/build/node_modules/@netlify/cache-utils/src/ main.js：34：40）晚上11:39:49：在/opt/buildhome/.netlify-build-nvm/versions/node/v12.16.3/lib/node_modules/@netlify/build/node_modules/@netlify/cache-utils/src/main下。 js：81：55 11:39:49 PM：在Array.map（<anonymous>） 11:39:49 PM：在allowMany（/opt/buildhome/.netlify-build-nvm/versions/node/v12.16.3/lib/node_modules/@netlify/build/node_modules/@netlify/cache-utils/src/ main.js：81：43） 11:39:49 PM：在Object.restore（/opt/buildhome/.netlify-build-nvm/versions/node/v12.16.3/lib/node_modules/@netlify/build/node_modules/@netlify/cache-utils/ src / main.js：94：32） 11:39:49 PM：在onPreBuild（/opt/buildhome/.netlify-build-plugins/node_modules/netlify-plugin-gatsby-cache/index.js:12:27） 11:39:49 PM：在Object.run（/opt/buildhome/.netlify-build-nvm/versions/node/v12.16.3/lib/node_modules/@netlify/build/src/plugins/child/run.js ：15：9）晚上11:39:49： 11:39:49 PM：已解决配置 11:39:49 PM：建立： 11:39:49 PM：发布：/ opt / build / repo 晚上11:39:49：插件： 11:39:49 PM：-输入：{} 11:39:49 PM：来源：ui 11:39:49 PM：包裹：netlify-plugin-a11y 11:39:49 PM：-输入：{} 11:39:49 PM：来源：ui 11:39:49 PM：包裹：netlify-plugin-amp-server-side-rendering 11:39:49 PM：-输入：{} 11:39:49 PM：来源：ui 11:39:49 PM：包裹：netlify-plugin-gatsby-cache 11:39:49 PM：-输入：{} 11:39:49 PM：来源：ui 11:39:49 PM：包裹：netlify-plugin-html-validate 11:39:49 PM：-输入：{} 11:39:49 PM：来源：ui 11:39:49 PM：包裹：netlify-plugin-image-optim 11:39:49 PM：-输入：{} 11:39:49 PM：来源：ui 11:39:49 PM：包裹：netlify-plugin-minify-html 11:39:49 PM：缓存工件 11:39:49 PM：开始保存构建插件 11:39:49 PM：完成保存构建插件 11:39:49 PM：开始保存点子缓存 11:39:55 PM：完成保存点子缓存 11:39:55 PM：开始保存emacs桶依赖关系 11:39:55 PM：完成保存emacs桶依赖关系 11:39:55 PM: Started saving maven dependencies 11:39:55 PM: Finished saving maven dependencies 11:39:55 PM: Started saving boot dependencies 11:39:55 PM: Finished saving boot dependencies 11:39:55 PM: Started saving go dependencies 11:39:55 PM: Finished saving go dependencies 11:39:58 PM: Error running command: Build script returned non-zero exit code: 1 11:39:58 PM: Failing build: Failed to build site 11:39:58 PM: Failed during stage 'building site': Build script returned non-zero exit code: 1 11:39:58 PM: Finished processing build request in 18.849272902s

Pages generated with gatsby-node.js stick around after deletion

Just wanted to report this issue to see if anybody else has had something similar. Haven't yet nailed down exactly why it's happening, but I suspect this plugin may be involved.

I've got a contentful datasource, which generates pages per object, deployed to netlify. I've noticed if I change the name or delete an object - the route is published with the new name, but the old built page sticks around? Looks super garbled as well too haha, like it's just the html that's left - the stylesheets it references have changed, etc.

I've verified by downloading the builds that the old pages are indeed being generated. My presumption is that they're being pulled from the cache, not recognising that the contentful source has changed.

Cleaning cache fixes everytime - and I do a fresh build always for prod so not a big issue.

But curious if anybody else has found this.

Issue caching the `.cache` directory

At the moment, this plugin caches PUBLISH_DIR/../.cache (PUBLISH_DIR was previously called BUILD_DIR). However when no "Publish directory" is set by the user, it defaults to the repository root directory.

This means the {repositoryRoot}/../.cache ends up being cached, which is probably not intended?

Wrong `PUBLISH_DIR`

Many production builds are reporting the following error:

Cannot cache /opt/build/repo because it is the current directory (/opt/build/repo) or a parent directory

This comes from this line of code in utils.cache.restore().

This is turn indicates that either PUBLISH_DIR or PUBLISH_DIR/../.cache is the build/base directory. This seems to be due to a user misconfiguration, but considering the error happened frequently, I will investigate more.

If any users having this issue is reading this, feel free to chime in.

Deploy failed due to an error in netlify-plugin-gatsby-cache plugin

9:27:43 AM: │ Plugin "netlify-plugin-gatsby-cache" internal error │
9:27:43 AM: └─────────────────────────────────────────────────────┘
9:27:43 AM:
9:27:43 AM: Error message
9:27:43 AM: Error: This plugin is missing a "manifest.yml".
9:27:43 AM: Please see the documentation at https://github.com/netlify/build#anatomy-of-a-plugin
9:27:43 AM:
9:27:43 AM: Plugin details
9:27:43 AM: Package: netlify-plugin-gatsby-cache
9:27:43 AM: Version: 0.2.1
9:27:43 AM: Repository: git+https://github.com/jlengstorf/netlify-plugin-gatsby-cache.git
9:27:43 AM: npm link: https://www.npmjs.com/package/netlify-plugin-gatsby-cache
9:27:43 AM: Report issues: https://github.com/jlengstorf/netlify-plugin-gatsby-cache/issues
9:27:43 AM:
9:27:43 AM: Error location
9:27:43 AM: While loading "netlify-plugin-gatsby-cache" from netlify.toml
9:27:43 AM: at async Promise.all (index 0)
9:27:43 AM:
9:27:43 AM: Resolved config
9:27:43 AM: build:
9:27:43 AM: command: gatsby build
9:27:43 AM: publish: /opt/build/repo/public
9:27:43 AM: plugins:
9:27:43 AM: - origin: config
9:27:43 AM: package: netlify-plugin-gatsby-cache

Should this plugin cache the publish directory?

This plugin caches PUBLISH_DIR (renamed from BUILD_DIR) which is the "Publish directory" set in the UI or in the configuration file (build.publish).

This issue is just to confirm that this is the intended behavior, i.e. that within Netlify, Gatsby always uses that publish directory to build files. Is this the case? Thanks!

Stored cache is ignored on build

Hello there,
I was using this cool plugin for a long time without any problems, but on 15.3.2021 it suddenly stopped to retrieve stored cache. I though it might be because I was running on gatsby v2, so I have updated all related libs to work on gatsby v3, but still no luck. I have also tried to clear cache. Plugin was installed via Netlify UI, I have also tried installing it via netlify.toml and throught package. After build is says that cache are stored but on next one, it says it havent found any. Here is my log.

Here is my deploy log (its private repo so cant give you link):
2:24:30 PM: Build ready to start
2:24:32 PM: build-image version: be42e453d6c8f171cc2f654acc29c0a8b60e6d93
2:24:32 PM: build-image tag: v3.7.1
2:24:32 PM: buildbot version: 449a896d650f66a48d6924703527235917156153
2:24:32 PM: Fetching cached dependencies
2:24:33 PM: Starting to download cache of 381.3MB
2:24:36 PM: Finished downloading cache in 3.783328282s
2:24:36 PM: Starting to extract cache
2:24:51 PM: Finished extracting cache in 15.215106742s
2:24:52 PM: Finished fetching cache in 19.13159458s
2:24:52 PM: Starting to prepare the repo for build
2:24:52 PM: Preparing Git Reference refs/heads/master
2:24:54 PM: Different publish path detected, going to use the one specified in the Netlify configuration file: ‘public’ versus ‘public/’ in the Netlify UI
2:24:55 PM: Starting build script
2:24:55 PM: Installing dependencies
2:24:55 PM: Python version set to 2.7
2:24:55 PM: Started restoring cached node version
2:24:59 PM: Finished restoring cached node version
2:24:59 PM: Downloading and installing node v12.13.0…
2:25:00 PM: Downloading https://nodejs.org/dist/v12.13.0/node-v12.13.0-linux-x64.tar.xz…
2:25:00 PM: Computing checksum with sha256sum
2:25:00 PM: Checksums matched!
2:25:03 PM: Now using node v12.13.0 (npm v6.12.0)
2:25:03 PM: Started restoring cached build plugins
2:25:03 PM: Finished restoring cached build plugins
2:25:03 PM: Attempting ruby version 2.6.2, read from environment
2:25:04 PM: Using ruby version 2.6.2
2:25:05 PM: Using PHP version 5.6
2:25:05 PM: Started restoring cached node modules
2:25:05 PM: Finished restoring cached node modules
2:25:05 PM: Installing NPM modules using NPM version 6.12.0
2:25:51 PM: > [email protected] install /opt/build/repo/node_modules/sharp
2:25:51 PM: > (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)
2:25:52 PM: info sharp Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.10.5/libvips-8.10.5-linux-x64.tar.br
2:25:55 PM: > [email protected] postinstall /opt/build/repo/node_modules/core-js
2:25:55 PM: > node -e “try{require(’./postinstall’)}catch(e){}”
2:25:55 PM: > [email protected] postinstall /opt/build/repo/node_modules/core-js-pure
2:25:55 PM: > node -e “try{require(’./postinstall’)}catch(e){}”
2:25:55 PM: > [email protected] postinstall /opt/build/repo/node_modules/gatsby-telemetry
2:25:55 PM: > node src/postinstall.js || true
2:25:55 PM: > [email protected] postinstall /opt/build/repo/node_modules/gatsby/node_modules/gatsby-cli
2:25:55 PM: > node scripts/postinstall.js
2:25:55 PM: > [email protected] postinstall /opt/build/repo/node_modules/gatsby
2:25:55 PM: > node scripts/postinstall.js
2:25:58 PM: npm WARN [email protected] No repository field.
2:25:58 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/webpack-dev-server/node_modules/fsevents):
2:25:58 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
2:25:58 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/watchpack-chokidar2/node_modules/fsevents):
2:25:58 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
2:25:58 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents):
2:25:58 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
2:25:58 PM: added 625 packages from 187 contributors, removed 1076 packages, updated 554 packages and audited 2748 packages in 52.471s
2:25:58 PM: found 4 vulnerabilities (3 low, 1 high)
2:25:58 PM: run npm audit fix to fix them, or npm audit for details
2:25:58 PM: NPM modules installed
2:25:58 PM: Started restoring cached go cache
2:26:00 PM: Finished restoring cached go cache
2:26:00 PM: Installing Go version 1.12
2:26:00 PM: unset GOOS;
2:26:00 PM: unset GOARCH;
2:26:00 PM: export GOROOT=’/opt/buildhome/.gimme_cache/versions/go1.12.linux.amd64’;
2:26:00 PM: export PATH="/opt/buildhome/.gimme_cache/versions/go1.12.linux.amd64/bin:{PATH}"; 2:26:00 PM: go version >&2; 2:26:00 PM: export GIMME_ENV='/opt/buildhome/.gimme_cache/env/go1.12.linux.amd64.env'; 2:26:00 PM: go version go1.12 linux/amd64 2:26:00 PM: Installing missing commands 2:26:00 PM: Verify run directory 2:26:02 PM: 2:26:02 PM: ──────────────────────────────────────────────────────────────── 2:26:02 PM: Netlify Build 2:26:02 PM: ──────────────────────────────────────────────────────────────── 2:26:02 PM: 2:26:02 PM: ❯ Version 2:26:02 PM: @netlify/build 10.2.3 2:26:02 PM: 2:26:02 PM: ❯ Flags 2:26:02 PM: deployId: 606da47e604a3c0007fa2999 2:26:02 PM: 2:26:02 PM: ❯ Current directory 2:26:02 PM: /opt/build/repo 2:26:02 PM: 2:26:02 PM: ❯ Config file 2:26:02 PM: /opt/build/repo/netlify.toml 2:26:02 PM: 2:26:02 PM: ❯ Context 2:26:02 PM: production 2:26:02 PM: 2:26:02 PM: ❯ Loading plugins 2:26:02 PM: - [email protected] from netlify.toml and package.json 2:26:02 PM: 2:26:02 PM: ──────────────────────────────────────────────────────────────── 2:26:02 PM: 1. onPreBuild command from netlify-plugin-gatsby-cache 2:26:02 PM: ──────────────────────────────────────────────────────────────── 2:26:02 PM: 2:26:02 PM: No Gatsby cache found. Building fresh. 2:26:02 PM: 2:26:02 PM: (netlify-plugin-gatsby-cache onPreBuild completed in 209ms) 2:26:02 PM: 2:26:02 PM: ──────────────────────────────────────────────────────────────── 2:26:02 PM: 2. Build command from Netlify app 2:26:02 PM: ──────────────────────────────────────────────────────────────── 2:26:02 PM: 2:26:02 PM: gatsby build
2:26:05 PM: success open and validate gatsby-configs - 0.067s
2:26:06 PM: success load plugins - 0.807s
2:26:06 PM: success onPreInit - 0.138s
2:26:06 PM: success delete html and css files from previous builds - 0.004s
2:26:06 PM: success initialize cache - 0.010s
2:26:06 PM: success copy gatsby files - 0.043s
2:26:06 PM: success onPreBootstrap - 0.016s
2:26:06 PM: success createSchemaCustomization - 0.007s
2:26:06 PM:
2:26:06 PM: gatsby-source-shopify/risoto-shop starting to fetch data from Shopify
2:26:06 PM:
2:26:06 PM: gatsby-source-shopify/risoto-shop fetched and processed Collection nodes: 186.080ms
2:26:06 PM:
2:26:06 PM: gatsby-source-shopify/risoto-shop fetched and processed Shop nodes: 178.341ms
2:26:06 PM:
2:26:06 PM: gatsby-source-shopify/risoto-shop fetched and processed ShopPolicy nodes: 182.796ms
2:26:06 PM:
2:26:06 PM: gatsby-source-shopify/risoto-shop fetched and processed Blog nodes: 195.480ms
2:26:07 PM:
2:26:07 PM: gatsby-source-shopify/risoto-shop fetched and processed Page nodes: 321.444ms
2:26:07 PM:
2:26:07 PM: gatsby-source-shopify/risoto-shop fetched and processed Article nodes: 417.496ms
2:26:12 PM: success Downloading remote files - 5.722s - 120/120 20.97/s
2:26:12 PM:
2:26:12 PM: gatsby-source-shopify/risoto-shop fetched and processed Product nodes: 5978.301ms
2:26:12 PM:
2:26:12 PM: gatsby-source-shopify/risoto-shop finished fetching data from Shopify: 5972.184ms
2:26:12 PM: success Checking for changed pages - 0.000s
2:26:12 PM: success source and transform nodes - 6.108s
2:26:13 PM: success building schema - 0.596s
2:26:13 PM: info Total nodes: 444, SitePage nodes: 36 (use --verbose for breakdown)
2:26:13 PM: success createPages - 0.054s
2:26:13 PM: success Checking for changed pages - 0.000s
2:26:13 PM: success createPagesStatefully - 0.105s
2:26:13 PM: success update schema - 0.036s
2:26:13 PM: success onPreExtractQueries - 0.001s
2:26:14 PM: success extract queries from components - 0.757s
2:26:14 PM: success write out redirect data - 0.002s
2:26:14 PM: warning The icon(static/favicon.png) you provided to ‘gatsby-plugin-manifest’ is not square.
2:26:14 PM: The icons we generate will be square and for the best results we recommend you provide a square icon.
2:26:14 PM: success Build manifest and related icons - 0.328s
2:26:14 PM: success onPostBootstrap - 0.331s
2:26:14 PM: info bootstrap finished - 11.927s
2:26:29 PM: warning Query takes too long:
2:26:29 PM: File path: /opt/build/repo/src/components/Cart/CartThumbnail.js
2:26:29 PM: warning Query takes too long:
2:26:29 PM: File path: /opt/build/repo/src/components/Product/ProductMainImage.js
2:26:29 PM: warning Query takes too long:
2:26:29 PM: File path: /opt/build/repo/src/components/ProductListing/ProductListing.js
2:26:29 PM: warning Query takes too long:
2:26:29 PM: File path: /opt/build/repo/src/components/shared/SiteMetadata.js
2:27:35 PM: success run static queries - 81.291s - 4/4 0.05/s
2:28:07 PM: success run page queries - 31.795s - 45/45 1.42/s
2:28:07 PM: success write out requires - 0.088s
2:31:44 PM: success Building production JavaScript and CSS bundles - 216.687s
2:31:46 PM: success Rewriting compilation hashes - 0.770s
2:49:42 PM: success Building HTML renderer - 9.519s
2:49:43 PM: success Building static HTML for pages - 0.730s - 45/45 61.65/s
2:49:43 PM: success Generating image thumbnails - 1408.442s - 2360/2360 1.68/s
2:49:43 PM: success onPostBuild - 0.034s
2:49:43 PM: info Done building in 1420.574906185 sec
2:49:43 PM:
2:49:43 PM: (build.command completed in 23m 40.9s)
2:49:43 PM:
2:49:43 PM: ────────────────────────────────────────────────────────────────
2:49:43 PM: 3. onPostBuild command from netlify-plugin-gatsby-cache
2:49:43 PM: ────────────────────────────────────────────────────────────────
2:49:43 PM:
2:49:48 PM: Stored the Gatsby cache to speed up future builds.
2:49:48 PM:
2:49:48 PM: (netlify-plugin-gatsby-cache onPostBuild completed in 5.2s)
2:49:48 PM:
2:49:48 PM: ────────────────────────────────────────────────────────────────
2:49:48 PM: 4. Deploy site
2:49:48 PM: ────────────────────────────────────────────────────────────────
2:49:48 PM:
2:49:48 PM: Starting to deploy site from ‘public’
2:49:49 PM: Creating deploy tree asynchronously
2:49:49 PM: Creating deploy upload records
2:49:52 PM: 58 new files to upload
2:49:52 PM: 0 new functions to upload
2:49:52 PM: Site deploy was successfully initiated
2:49:52 PM:
2:49:52 PM: (Deploy site completed in 4.1s)
2:49:53 PM:
2:49:53 PM: ────────────────────────────────────────────────────────────────
2:49:53 PM: Netlify Build Complete
2:49:53 PM: ────────────────────────────────────────────────────────────────
2:49:53 PM:
2:49:53 PM: (Netlify Build completed in 23m 51s)
2:49:53 PM: Execution timed out after 24m58.147551752s
2:49:53 PM: Error running command: Command did not finish within the time limit
2:49:53 PM: Failing build: Failed to build site
2:49:53 PM: Failed during stage ‘building site’: Command did not finish within the time limit
2:49:53 PM: Finished processing build request in 25m20.708055275s
2:49:59 PM: Starting post processing
2:49:59 PM: Post processing - HTML
2:50:03 PM: Post processing - header rules
2:50:03 PM: Post processing - redirect rules
2:50:03 PM: Post processing done
2:50:03 PM: Site is live

Broken build logs links

Build logs referenced in readme are no longer loading. Netlify page opens but the log itself does not load. Tried in Brave and Edge browsers.

Post links not updated

Hey,

I recently enabled this plugin on a Gatsby blog that I maintain. However, I was recently informed that blog posts don't show a link at the bottom of the page to newer posts anymore. If a new post is published this would link to the previous post and the previous post should update to include a link to the newest one, which it doesn't.

Is there something for cases like these, or does the previous post need to be changed every time for it to not match with the cached version so it gets rebuilt?

thanks

Issue when caching the whole repository

This plugin caches PUBLISH_DIR (renamed from BUILD_DIR) which is the "Publish directory" set in the UI or in the configuration file (build.publish). When unset, this defaults to the "build directory", which is (in most cases) the repository root directory.

However caching (and restoring) the whole repository has several issues:

It caches many directories that are not related to Gatsby but take lots of space, such as node_modules. Those should either not be cached or be cached separately from this plugin.
It caches directories that are not meant to restored across builds. For example .git (beside being big) is being restored by this plugin, which should not be the case.
It undoes any build operations inside the repository that might have happened before this plugin starts restoring the cache, leading to conflicts with other plugins, Netlify Build or the buildbot.

In short, caching the whole repository does not seem to be a viable option.

Please note that this is only an issue when no "Publish directory" was set. When one is set, caching it and restoring it should just work.

When no "Publish directory" is set, is there any specific files or directories that we could cache instead to avoid the issues described above?

Can’t uninstall plugin in netlify web interface

The uninstall option is not shown in the option panel of the plugin. The plugin still gets triggered in build processes, and we sometimes have issues with our CMS.

Is there a way to uninstall the plugin differently? Thanks in advance!

Does the UI installing process require any other configuration?

Hey @jlengstorf, I'm not sure I'm getting the setup instructions correctly.

Despite using If you don’t want to use the UI-based installation, it later says that this must be set in your netlify.toml in the [build] section. I'm not sure if automatically installing it on Netlify UI is enough, and also I can't know for sure that my plugin is working.

If you point something that could be improved on the documentation, I'd be happy to contribute :)

Thanks

It's caching an older version of the image if it has the same name

The repo shows an updated file with the same name but what get's deployed is the older version.

How does this compare to Gatsby incremental builds?

Hi, how does this plugin compare to Gatsby's new incremental builds? See https://www.gatsbyjs.org/blog/2020-04-22-announcing-incremental-builds/

Are they trying to achieve the same and are exclusive of each other, or do they complement each other?

update docs to propose GATSBY_EXPERIMENTAL_PAGE_BUILD_ON_DATA_CHANGES=true

Reason

without GATSBY_EXPERIMENTAL_PAGE_BUILD_ON_DATA_CHANGES=true build doesn't delete old pages

Build fails when you update NetlifyCMS .md files.

Not sure why this happens but every time i update .md files through the netlifyCMS the build fails. The page is successfully built if I empty the cahce and rebuild. It gave me this error:
WebpackError: TypeError: Cannot read property 'childImageSharp' of null
On the page I updated when I tried to access an image.
headerImage={post.frontmatter.headerImage.childImageSharp.fluid}
Any ideas why it behaves like this?

Make it generic?

Hi,

I'm trying to replace https://github.com/axe312ger/gatsby-plugin-netlify-cache with this plugin, but the gatsby plugin is more "generic" as it permits me to pass folders to cache as inputs.

Unfortunately, for my gatsby sites, we have a lot of images, and we did not choose to use Git LFS to handle them. Instead we sync images from S3 into a subfolder before building gatsby.

So I need to cache:

.cache
public
s3images

Unfortunately, this plugin does not permit me to add an extra folder, so I'd probably need to copy this plugin and tweak it as a local plugin to fit my need.

There's also a NextJS cache plugin here: https://github.com/pizzafox/netlify-cache-nextjs/blob/master/src/index.ts

What about making a generic cache plugin for Netlify to cover the caching needs of everybody, with a preset system for most common usecases?

I assume most sites/fwk will only need to do cache and restore from a list of paths, and nothing more. So presets can hardcode lists of paths, while inputs could allow to pass extra paths to cache/restore.

[[plugins]]
package = "netlify-plugin-cache"

    [plugins.inputs]
    preset = "gatsby"

       [[plugins.inputs.cacheFolders]]
       path = "./../s3images"

       [[plugins.inputs.cacheFolders]]
       path = "./../someDir"

beta link 404s

It looks like the beta link on the readme 404s

https://docs.netlify.com/configure-builds/plugins/?utm_source=github&utm_medium=netlify-plugin-gatsby-cache-jl&utm_campaign=devex

Improve error message when the `publish` directory is invalid

A common error seems to be for users that forgot to set a publish directory.

Should this be validated, in order to provide a better error message?

That situation can be detected by checking:

if (process.cwd() === constants.PUBLISH_DIR) {
  throw new Error(...)
}

Certain pages are not built when data changes

Using gatsby-source-sanity some document types are not getting built by Netlify when the data changes. The build is triggered, but these specific pages don't show the new data. Using the same config & dataset while building locally does build the documents in question, so it's looking like this is a cache issue. This is also happening when some documents are unpublished in Sanity - a build is triggered, but the page is retained, even though the page-data.json is not.

Is there a way to clean the gatsby cache on Netlify? Other suggestions on how to remedy this?

Getting fail almost on every build without cleaning the cache on Netlify

Not sure which plugin causes this error so I hope you'll help to find out 🙂

I suppose either this plugin or gatsby-source-wordpress-experimental causes this error

I get such error almost every time when the site is being built without cleaning the cache on Netlify

Thanks!

Error If I Don't Clear Cache Using Netlify Plugin

10:58:42 AM: ❯ Loading plugins
10:58:42 AM:    - [email protected] from Netlify app
10:58:43 AM: 
10:58:43 AM: ────────────────────────────────────────────────────────────────
10:58:43 AM:   1. onPreBuild command from netlify-plugin-gatsby-cache        
10:58:43 AM: ────────────────────────────────────────────────────────────────
10:58:43 AM: 
10:58:43 AM: Found a Gatsby cache. We’re about to go FAST. ⚡️
10:58:43 AM:

10:58:45 AM: error There was a problem loading the local build command. Gatsby may not be installed. Perhaps you need to run "npm install"? Class extends value undefined is not a constructor or null
10:58:45 AM: 
10:58:45 AM: 
10:58:45 AM:   TypeError: Class extends value undefined is not a constructor or null
10:58:45 AM:   
10:58:45 AM:   - MainTemplate.js:56 Object.<anonymous>
10:58:45 AM:     [repo]/[webpack]/lib/MainTemplate.js:56:45
10:58:45 AM:   
10:58:45 AM:   - loader:1092 Module._compile
10:58:45 AM:     node:internal/modules/cjs/loader:1092:14
10:58:45 AM:   
10:58:45 AM:   - loader:1121 Object.Module._extensions..js
10:58:45 AM:     node:internal/modules/cjs/loader:1121:10
10:58:45 AM:   
10:58:45 AM:   - loader:972 Module.load
10:58:45 AM:     node:internal/modules/cjs/loader:972:32
10:58:45 AM:   
10:58:45 AM:   - loader:813 Function.Module._load
10:58:45 AM:     node:internal/modules/cjs/loader:813:14
10:58:45 AM:   
10:58:45 AM:   - loader:996 Module.require
10:58:45 AM:     node:internal/modules/cjs/loader:996:19
10:58:45 AM:   
10:58:45 AM:   - helpers:92 require
10:58:45 AM:     node:internal/modules/cjs/helpers:92:18
10:58:45 AM:   
10:58:45 AM:   - Compilation.js:24 Object.<anonymous>
10:58:45 AM:     [repo]/[webpack]/lib/Compilation.js:24:22
10:58:45 AM:   
10:58:45 AM:   - loader:1092 Module._compile
10:58:45 AM:     node:internal/modules/cjs/loader:1092:14
10:58:45 AM:   
10:58:45 AM:   - loader:1121 Object.Module._extensions..js
10:58:45 AM:     node:internal/modules/cjs/loader:1121:10
10:58:45 AM:   
10:58:45 AM:   - loader:972 Module.load
10:58:45 AM:     node:internal/modules/cjs/loader:972:32
10:58:45 AM:   
10:58:45 AM:   - loader:813 Function.Module._load
10:58:45 AM:     node:internal/modules/cjs/loader:813:14
10:58:45 AM:   
10:58:45 AM:   - loader:996 Module.require
10:58:45 AM:     node:internal/modules/cjs/loader:996:19
10:58:45 AM:   
10:58:45 AM:   - helpers:92 require
10:58:45 AM:     node:internal/modules/cjs/helpers:92:18
10:58:45 AM:   
10:58:45 AM:   - Compiler.js:20 Object.<anonymous>
10:58:45 AM:     [repo]/[webpack]/lib/Compiler.js:20:21
10:58:45 AM:   
10:58:45 AM:   - loader:1092 Module._compile
10:58:45 AM:     node:internal/modules/cjs/loader:1092:14
10:58:45 AM:   
10:58:45 AM:

via https://app.netlify.com/sites/run-log/deploys/6050d590432356e0669e46a2

when I clear the cache, this works as expected with netlify

repo https://github.com/JackHowa/marathon-run-log/blob/main/package.json

this broke with ^3.0.0 gatsby

auto-delete old cache or store /public/static instead of all public

This is close to other repo issue
But when I tried to delete page(build it locally or in netlify). I couldn't.
There was nothing about that in sitemap. But it was in public/page-data.

So, please use public/static instead of public folder

public.netlify.cache.json not found when clearing cache

If I clear the cache, first run lead to this error. On retry it works fine.

in netlify pipeline: No Gatsby cache found. Building fresh...

Hi there,

Locally I was able to use to this plugin and it works, but in the netlify pipeline, I'm getting this message:

No Gatsby cache found. Building fresh...

I am also noticing a message above:

6:13:02 PM: Found Netlify Build that didn't match the version latest. Installing now.

It seems to be able to the save the cache properly in the onSaveCache callback, but in a pipeline it's not able to find the cached directory. It seems like it doesn't exist...

console.log("fs.existsSync(netlifyCacheDir)", fs.existsSync(netlifyCacheDir), netlifyCacheDir)
console.log("fs.existsSync(netlifyPublicDir)", fs.existsSync(netlifyPublicDir), netlifyPublicDir)

Logs the following, in the onPreBuild callback:

6:13:26 PM: fs.existsSync(netlifyCacheDir) false /opt/build/cache/gatsby/.cache
6:13:26 PM: fs.existsSync(netlifyPublicDir) false /opt/build/cache/gatsby/public

is there way we can set expiry on build cache?

I want to set expiry on build cache so that after expiry time , a new new fresh build gets created.
is it possible?

Gatsby cache plugin not update data correct

Hi,

my site: elated-hoover-b36a93
work stack: gatsby / wordpress /bitbucket
wordpress plugin: NetlifyPress v1.1.1
When I change something in wordpress it not updated correct in the netlify, only after I do clear cache and deploy site it is updated.

deploy log:

10:27:08 AM: Build ready to start
10:27:10 AM: build-image version: 7b53c5fc4445e3ec99d3949e5d1174a8c5be4f16
10:27:10 AM: build-image tag: v3.7.2
10:27:10 AM: buildbot version: a8df6d1263bb5bcc16f7b4ebb8e9a6cb904cfa8a
10:27:10 AM: Fetching cached dependencies
10:27:10 AM: Starting to download cache of 222.9MB
10:27:12 AM: Finished downloading cache in 1.59319369s
10:27:12 AM: Starting to extract cache
10:27:19 AM: Finished extracting cache in 6.833835505s
10:27:19 AM: Finished fetching cache in 8.484349284s
10:27:19 AM: Starting to prepare the repo for build
10:27:20 AM: Preparing Git Reference refs/heads/master
10:27:20 AM: Parsing package.json dependencies
10:27:22 AM: Starting build script
10:27:22 AM: Installing dependencies
10:27:22 AM: Python version set to 2.7
10:27:22 AM: Started restoring cached node version
10:27:24 AM: Finished restoring cached node version
10:27:25 AM: v12.18.0 is already installed.
10:27:26 AM: Now using node v12.18.0 (npm v6.14.4)
10:27:26 AM: Started restoring cached build plugins
10:27:26 AM: Finished restoring cached build plugins
10:27:26 AM: Attempting ruby version 2.7.1, read from environment
10:27:27 AM: Using ruby version 2.7.1
10:27:27 AM: Using PHP version 5.6
10:27:27 AM: Started restoring cached node modules
10:27:27 AM: Finished restoring cached node modules
10:27:28 AM: Started restoring cached go cache
10:27:28 AM: Finished restoring cached go cache
10:27:28 AM: go version go1.14.4 linux/amd64
10:27:28 AM: go version go1.14.4 linux/amd64
10:27:28 AM: Installing missing commands
10:27:28 AM: Verify run directory
10:27:29 AM:
10:27:29 AM: ────────────────────────────────────────────────────────────────
10:27:29 AM: Netlify Build
10:27:29 AM: ────────────────────────────────────────────────────────────────
10:27:29 AM:
10:27:29 AM: ❯ Version
10:27:29 AM: @netlify/build 11.3.2
10:27:29 AM:
10:27:29 AM: ❯ Flags
10:27:29 AM: deployId: 608a5fcc37aa9cc2b8570c0b
10:27:29 AM:
10:27:29 AM: ❯ Current directory
10:27:29 AM: /opt/build/repo
10:27:29 AM:
10:27:29 AM: ❯ Config file
10:27:29 AM: No config file was defined: using default values.
10:27:29 AM:
10:27:29 AM: ❯ Context
10:27:29 AM: production
10:27:29 AM:
10:27:29 AM: ❯ Loading plugins
10:27:29 AM: - [email protected] from Netlify app
10:27:30 AM:
10:27:30 AM: ────────────────────────────────────────────────────────────────
10:27:30 AM: 1. onPreBuild command from netlify-plugin-gatsby-cache
10:27:30 AM: ────────────────────────────────────────────────────────────────
10:27:30 AM:
10:27:31 AM: Found a Gatsby cache. We’re about to go FAST. ⚡️
10:27:31 AM:
10:27:31 AM: (netlify-plugin-gatsby-cache onPreBuild completed in 1.4s)
10:27:31 AM:
10:27:31 AM: ────────────────────────────────────────────────────────────────
10:27:31 AM: 2. Build command from Netlify app
10:27:31 AM: ────────────────────────────────────────────────────────────────
10:27:31 AM:
10:27:31 AM: $ npm run build
10:27:31 AM: > [email protected] build /opt/build/repo
10:27:31 AM: > cross-env GATSBY_EXPERIMENTAL_PAGE_BUILD_ON_DATA_CHANGES=true gatsby build --log-pages
10:27:35 AM: success open and validate gatsby-configs - 0.053s
10:27:36 AM: success load plugins - 1.206s
10:27:36 AM: success onPreInit - 0.028s
10:27:36 AM: success initialize cache - 0.004s
10:27:36 AM: success copy gatsby files - 0.053s
10:27:36 AM: success onPreBootstrap - 0.015s
10:27:36 AM: success gatsby-source-wordpress ensuring plugin requirements are met - 0.003s
10:27:37 AM: success gatsby-source-wordpress diff schemas - 0.920s
10:27:37 AM: success gatsby-source-wordpress ingest WPGraphQL schema - 1.146s
10:27:37 AM: success createSchemaCustomization - 1.247s
10:27:39 AM: success gatsby-source-wordpress fetch root fields - 1.236s
10:27:39 AM: ⠀
10:27:39 AM: info gatsby-source-wordpress update page Homepage (#58)
10:27:39 AM: ⠀
10:27:39 AM: success gatsby-source-wordpress pull updates since last build - 1.400s
10:27:39 AM: success Checking for changed pages - 0.000s
10:27:39 AM: success source and transform nodes - 1.751s
10:27:42 AM: success building schema - 2.779s
10:27:42 AM: info Total nodes: 714, SitePage nodes: 39 (use --verbose for breakdown)
10:27:42 AM: success createPages - 0.171s
10:27:42 AM: success Checking for changed pages - 0.000s
10:27:42 AM: success createPagesStatefully - 0.082s
10:27:42 AM: success Cleaning up stale page-data - 0.004s
10:27:42 AM: success update schema - 0.180s
10:27:42 AM: success onPreExtractQueries - 0.001s
10:27:44 AM: success extract queries from components - 1.318s
10:27:44 AM: warning The GraphQL query in the non-page component "/opt/build/repo/src/templates/post.tsx" will not be run.
10:27:44 AM: Exported queries are only executed for Page components. It's possible you're
10:27:44 AM: trying to create pages in your gatsby-node.js and that's failing for somereason.
10:27:44 AM: If the failing component(s) is a regular component and not intended to be a page
10:27:44 AM: component, you generally want to use a (https://gatsbyjs.org/docs/static-query)
10:27:44 AM: instead of exporting a page query.
10:27:44 AM: If you're more experienced with GraphQL, you can also export GraphQLfragments from components and compose the fragments in the Page component
10:27:44 AM: query and pass data down into the child component — https://graphql.org/learn/queries/#fragments
10:27:44 AM: success write out redirect data - 0.001s
10:27:44 AM: warning The icon(src/images/3dinnnovation_logo.png) you provided to 'gatsby-plugin-manifest' is not square.
10:27:44 AM: The icons we generate will be square and for the best results we recommend you provide a square icon.
10:27:44 AM: success Build manifest and related icons - 0.174s
10:27:44 AM: success onPostBootstrap - 0.176s
10:27:44 AM: info bootstrap finished - 12.639s
10:27:44 AM: success run static queries - 0.040s - 6/6 151.22/s
10:27:44 AM: success run page queries - 0.013s - 2/2 152.77/s
10:27:44 AM: success write out requires - 0.005s
10:28:03 AM: warning chunk styles [mini-css-extract-plugin]
10:28:03 AM: Conflicting order. Following module has been added:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/top-bar.css
10:28:03 AM: despite it was not able to fulfill desired ordering with these modules:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/faq/search-faq.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-faq-tsx * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/faq/questions-wrapper-faq.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-faq-tsx * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/faq/questions-faq.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-faq-tsx * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/product-page/breadCrumbs.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-faq-tsx - while fulfilling desired order of chunk group(s) component---src-pages-index-js, component---src-pages-products-tsx, component---src-templates-category-tsx, component---src-templates-product-tsx
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/common/page-banners.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-templates-article-tsx - while fulfilling desired order of chunk group(s) component---src-pages-about-us-tsx, component---src-pages-blog-tsx, component---src-pages-reviews-tsx
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/article/up-next.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-templates-article-tsx * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/blog/simple-blog.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-templates-article-tsx - while fulfilling desired order of chunk group(s) component---src-pages-blog-tsx
10:28:03 AM: warning chunk styles [mini-css-extract-plugin]
10:28:03 AM: Conflicting order. Following module has been added:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/login/login.css
10:28:03 AM: despite it was not able to fulfill desired ordering with these modules:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/faq/search-faq.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-faq-tsx * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/faq/questions-wrapper-faq.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-faq-tsx * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/faq/questions-faq.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-faq-tsx * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/product-page/breadCrumbs.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-faq-tsx - while fulfilling desired order of chunk group(s) component---src-pages-index-js, component---src-pages-products-tsx, component---src-templates-category-tsx, component---src-templates-product-tsx
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/common/page-banners.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-templates-article-tsx - while fulfilling desired order of chunk group(s) component---src-pages-about-us-tsx, component---src-pages-blog-tsx, component---src-pages-reviews-tsx
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/article/up-next.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-templates-article-tsx * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/blog/simple-blog.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-templates-article-tsx - while fulfilling desired order of chunk group(s) component---src-pages-blog-tsx
10:28:03 AM: warning chunk styles [mini-css-extract-plugin]
10:28:03 AM: Conflicting order. Following module has been added:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/blog/simple-blog.css
10:28:03 AM: despite it was not able to fulfill desired ordering with these modules:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/blog/eternity-banner-blog.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-blog-tsx * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/blog/blogs.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-blog-tsx * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/subscribe.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-blog-tsx - while fulfilling desired order of chunk group(s) component---src-templates-article-tsx
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/layout.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-blog-tsx - while fulfilling desired order of chunk group(s) component---src-templates-article-tsx
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/footer.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-blog-tsx - while fulfilling desired order of chunk group(s) component---src-templates-article-tsx
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/menu-bar.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-blog-tsx - while fulfilling desired order of chunk group(s) component---src-templates-article-tsx
10:28:03 AM: warning chunk styles [mini-css-extract-plugin]
10:28:03 AM: Conflicting order. Following module has been added:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/menu-bar.css
10:28:03 AM: despite it was not able to fulfill desired ordering with these modules:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/faq/search-faq.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-faq-tsx * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/faq/questions-wrapper-faq.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-faq-tsx * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/faq/questions-faq.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-faq-tsx * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/product-page/breadCrumbs.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-faq-tsx - while fulfilling desired order of chunk group(s) component---src-pages-index-js, component---src-pages-products-tsx, component---src-templates-category-tsx, component---src-templates-product-tsx
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/common/page-banners.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-templates-article-tsx - while fulfilling desired order of chunk group(s) component---src-pages-about-us-tsx, component---src-pages-blog-tsx, component---src-pages-reviews-tsx
10:28:03 AM: warning chunk styles [mini-css-extract-plugin]
10:28:03 AM: Conflicting order. Following module has been added:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/footer.css
10:28:03 AM: despite it was not able to fulfill desired ordering with these modules:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/faq/search-faq.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-faq-tsx * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/faq/questions-wrapper-faq.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-faq-tsx * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/faq/questions-faq.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-faq-tsx * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/product-page/breadCrumbs.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-faq-tsx - while fulfilling desired order of chunk group(s) component---src-pages-index-js, component---src-pages-products-tsx, component---src-templates-category-tsx, component---src-templates-product-tsx
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/common/page-banners.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-templates-article-tsx - while fulfilling desired order of chunk group(s) component---src-pages-about-us-tsx, component---src-pages-blog-tsx, component---src-pages-reviews-tsx
10:28:03 AM: warning chunk styles [mini-css-extract-plugin]
10:28:03 AM: Conflicting order. Following module has been added:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/layout.css
10:28:03 AM: despite it was not able to fulfill desired ordering with these modules:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/faq/search-faq.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-faq-tsx * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/faq/questions-wrapper-faq.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-faq-tsx * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/faq/questions-faq.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-faq-tsx * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/product-page/breadCrumbs.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-faq-tsx - while fulfilling desired order of chunk group(s) component---src-pages-index-js, component---src-pages-products-tsx, component---src-templates-category-tsx, component---src-templates-product-tsx
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/common/page-banners.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-templates-article-tsx - while fulfilling desired order of chunk group(s) component---src-pages-about-us-tsx, component---src-pages-blog-tsx, component---src-pages-reviews-tsx
10:28:03 AM: warning chunk styles [mini-css-extract-plugin]
10:28:03 AM: Conflicting order. Following module has been added:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/product-page/breadCrumbs.css
10:28:03 AM: despite it was not able to fulfill desired ordering with these modules:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/product-page/product-details.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-templates-product-tsx * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/subscribe.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-templates-product-tsx - while fulfilling desired order of chunk group(s) component---src-pages-faq-tsx, component---src-pages-index-js, component---src-pages-products-tsx, component---src-templates-category-tsx
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/magic-moments.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-templates-product-tsx - while fulfilling desired order of chunk group(s) component---src-pages-index-js, component---src-pages-products-tsx, component---src-templates-category-tsx
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/comments.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-templates-product-tsx - while fulfilling desired order of chunk group(s) component---src-pages-index-js, component---src-pages-products-tsx, component---src-templates-category-tsx
10:28:03 AM: warning chunk styles [mini-css-extract-plugin]
10:28:03 AM: Conflicting order. Following module has been added:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/comments.css
10:28:03 AM: despite it was not able to fulfill desired ordering with these modules:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/crystal-collection.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-index-js - while fulfilling desired order of chunk group(s) component---src-pages-products-tsx
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/image-card.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-index-js - while fulfilling desired order of chunk group(s) component---src-pages-products-tsx
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/category/search-product.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-products-tsx - while fulfilling desired order of chunk group(s) component---src-templates-category-tsx
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/category/filter-products.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-products-tsx - while fulfilling desired order of chunk group(s) component---src-templates-category-tsx
10:28:03 AM: warning chunk styles [mini-css-extract-plugin]
10:28:03 AM: Conflicting order. Following module has been added:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/category/filter-products.css
10:28:03 AM: despite it was not able to fulfill desired ordering with these modules:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/category/list-products.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-templates-category-tsx - while fulfilling desired order of chunk group(s) component---src-pages-products-tsx
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/category/product.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-templates-category-tsx - while fulfilling desired order of chunk group(s) component---src-pages-products-tsx
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/subscribe.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-templates-category-tsx - while fulfilling desired order of chunk group(s) component---src-pages-products-tsx
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/magic-moments.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-templates-category-tsx - while fulfilling desired order of chunk group(s) component---src-pages-products-tsx
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/banner-2.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-templates-category-tsx - while fulfilling desired order of chunk group(s) component---src-pages-products-tsx
10:28:03 AM: warning chunk styles [mini-css-extract-plugin]
10:28:03 AM: Conflicting order. Following module has been added:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/image-card.css
10:28:03 AM: despite it was not able to fulfill desired ordering with these modules:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/subscribe.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-products-tsx - while fulfilling desired order of chunk group(s) component---src-pages-index-js
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/magic-moments.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-products-tsx - while fulfilling desired order of chunk group(s) component---src-pages-index-js
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/all-products/products-promotion-1.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-products-tsx * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/category/product.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-products-tsx * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/category/search-product.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-products-tsxwarning chunk styles [mini-css-extract-plugin]
10:28:03 AM: Conflicting order. Following module has been added:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/crystal-collection.css
10:28:03 AM: despite it was not able to fulfill desired ordering with these modules:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/subscribe.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-products-tsx - while fulfilling desired order of chunk group(s) component---src-pages-index-js
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/magic-moments.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-products-tsx - while fulfilling desired order of chunk group(s) component---src-pages-index-js
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/all-products/products-promotion-1.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-products-tsx * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/category/product.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-products-tsx * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/category/search-product.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-products-tsxwarning chunk styles [mini-css-extract-plugin]
10:28:03 AM: Conflicting order. Following module has been added:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/banner-1.css
10:28:03 AM: despite it was not able to fulfill desired ordering with these modules:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/product-page/eternity-banner.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-templates-product-tsx * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/product-page/product-details.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-templates-product-tsx * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/subscribe.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-templates-product-tsx - while fulfilling desired order of chunk group(s) component---src-pages-index-js
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/magic-moments.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-templates-product-tsx - while fulfilling desired order of chunk group(s) component---src-pages-index-js
10:28:03 AM: warning chunk styles [mini-css-extract-plugin]
10:28:03 AM: Conflicting order. Following module has been added:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/banner-2.css
10:28:03 AM: despite it was not able to fulfill desired ordering with these modules:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/subscribe.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-products-tsx - while fulfilling desired order of chunk group(s) component---src-pages-index-js, component---src-templates-category-tsx
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/magic-moments.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-products-tsx - while fulfilling desired order of chunk group(s) component---src-pages-index-js, component---src-templates-category-tsx
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/all-products/products-promotion-1.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-products-tsx * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/category/product.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-products-tsx - while fulfilling desired order of chunk group(s) component---src-templates-category-tsx
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/category/search-product.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-products-tsx - while fulfilling desired order of chunk group(s) component---src-templates-category-tsx
10:28:03 AM: warning chunk styles [mini-css-extract-plugin]
10:28:03 AM: Conflicting order. Following module has been added:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/magic-moments.css
10:28:03 AM: despite it was not able to fulfill desired ordering with these modules:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/subscribe.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-contact-us-tsx - while fulfilling desired order of chunk group(s) component---src-pages-index-js, component---src-pages-products-tsx, component---src-pages-reviews-tsx, component---src-templates-category-tsx, component---src-templates-product-tsx
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/all-products/products-promotion-1.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-products-tsx * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/category/product.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-products-tsx - while fulfilling desired order of chunk group(s) component---src-templates-category-tsx, component---src-templates-product-tsx
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/category/search-product.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-products-tsx - while fulfilling desired order of chunk group(s) component---src-templates-category-tsx
10:28:03 AM: warning chunk styles [mini-css-extract-plugin]
10:28:03 AM: Conflicting order. Following module has been added:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/category/search-product.css
10:28:03 AM: despite it was not able to fulfill desired ordering with these modules:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/category/list-products.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-templates-category-tsx - while fulfilling desired order of chunk group(s) component---src-pages-products-tsx
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/category/product.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-templates-category-tsx - while fulfilling desired order of chunk group(s) component---src-pages-products-tsx
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/subscribe.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-templates-category-tsx - while fulfilling desired order of chunk group(s) component---src-pages-products-tsx
10:28:03 AM: warning chunk styles [mini-css-extract-plugin]
10:28:03 AM: Conflicting order. Following module has been added:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/subscribe.css
10:28:03 AM: despite it was not able to fulfill desired ordering with these modules:
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/all-products/products-promotion-1.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-products-tsx * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/category/product.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-pages-products-tsx - while fulfilling desired order of chunk group(s) component---src-templates-category-tsx, component---src-templates-product-tsx
10:28:03 AM: * css ./node_modules/css-loader??ref--12-oneOf-1-1!./node_modules/postcss-loader/src??postcss-2!./src/components/common/page-banners.css
10:28:03 AM: - couldn't fulfill desired order of chunk group(s) component---src-templates-article-tsx - while fulfilling desired order of chunk group(s) component---src-pages-about-us-tsx, component---src-pages-blog-tsx, component---src-pages-reviews-tsx
10:28:03 AM: success Building production JavaScript and CSS bundles - 18.505s
10:28:08 AM: success Building HTML renderer - 4.956s
10:28:08 AM: success Building static HTML for pages - 0.294s - 1/1 3.40/s
10:28:08 AM: success Delete previous page data - 0.000s
10:28:08 AM: success onPostBuild - 0.004s
10:28:08 AM: info Done building in 36.779505224 sec
10:28:08 AM: info Built pages:
10:28:08 AM: Updated page: /using-typescript/
10:28:08 AM:
10:28:08 AM: (build.command completed in 37.4s)
10:28:08 AM:
10:28:08 AM: ────────────────────────────────────────────────────────────────
10:28:08 AM: 3. onPostBuild command from netlify-plugin-gatsby-cache
10:28:08 AM: ────────────────────────────────────────────────────────────────
10:28:08 AM:
10:28:10 AM: Stored the Gatsby cache to speed up future builds.
10:28:10 AM:
10:28:10 AM: (netlify-plugin-gatsby-cache onPostBuild completed in 1.2s)
10:28:10 AM:
10:28:10 AM: ────────────────────────────────────────────────────────────────
10:28:10 AM: 4. Deploy site
10:28:10 AM: ────────────────────────────────────────────────────────────────
10:28:10 AM:
10:28:10 AM: Starting to deploy site from 'public'
10:28:10 AM: Creating deploy tree
10:28:10 AM: Creating deploy upload records
10:28:10 AM: 3 new files to upload
10:28:10 AM: 0 new functions to upload
10:28:10 AM: Site deploy was successfully initiated
10:28:10 AM:
10:28:10 AM: (Deploy site completed in 462ms)
10:28:10 AM:
10:28:10 AM: ────────────────────────────────────────────────────────────────
10:28:10 AM: Netlify Build Complete
10:28:10 AM: ────────────────────────────────────────────────────────────────
10:28:10 AM:
10:28:10 AM: (Netlify Build completed in 40.9s)
10:28:10 AM: Starting post processing
10:28:10 AM: Caching artifacts
10:28:10 AM: Post processing - HTML
10:28:10 AM: Started saving node modules
10:28:10 AM: Finished saving node modules
10:28:10 AM: Started saving build plugins
10:28:10 AM: Finished saving build plugins
10:28:10 AM: Started saving pip cache
10:28:11 AM: Finished saving pip cache
10:28:11 AM: Started saving emacs cask dependencies
10:28:11 AM: Finished saving emacs cask dependencies
10:28:11 AM: Started saving maven dependencies
10:28:11 AM: Finished saving maven dependencies
10:28:11 AM: Started saving boot dependencies
10:28:11 AM: Finished saving boot dependencies
10:28:11 AM: Started saving rust rustup cache
10:28:11 AM: Finished saving rust rustup cache
10:28:11 AM: Started saving go dependencies
10:28:11 AM: Finished saving go dependencies
10:28:11 AM: Build script success
10:28:11 AM: Post processing - header rules
10:28:11 AM: Post processing - redirect rules
10:28:11 AM: Post processing done
10:28:11 AM: Site is live ✨
10:28:39 AM: Finished processing build request in 1m28.98180368s

Thanks

Plugin breaks in @netlify/build 18.11.2

Hi there,

This plugin stopped working in between @netlify/build 18.10.0 and 18.11.2

I haven't changed my code, but my builds are triggered by a hook coming from Prismic. However, the latests builds have not been working. I'm receiving the following error:

3:21:34 PM: ────────────────────────────────────────────────────────────────
3:21:34 PM:   API error on "getLatestPluginRuns"                            
3:21:34 PM: ────────────────────────────────────────────────────────────────
3:21:34 PM: 
3:21:34 PM:   Error message
3:21:34 PM:   unknown
3:21:34 PM: 
3:21:34 PM:   Error location
3:21:34 PM:   While calling the Netlify API endpoint 'getLatestPluginRuns' with:
3:21:34 PM:   {
3:21:34 PM:     "site_id": "d7078eed-cf17-4cc8-ac82-e5f765f30c13",
3:21:34 PM:     "packages": [
3:21:34 PM:       "netlify-plugin-gatsby-cache"
3:21:34 PM:     ],
3:21:34 PM:     "state": "success"
3:21:34 PM:   }
3:21:34 PM: 
3:21:34 PM:   Error properties
3:21:34 PM:   {
3:21:34 PM:     name: 'JSONHTTPError',
3:21:34 PM:     status: 422,
3:21:34 PM:     json: { code: 422, message: "parameter 'packages' must be an array" }
3:21:34 PM:   }

Cache always empty on Deploy Preview builds

Hi! Big thanks for this plugin - it's helping to bring down the build time on our develop branch significantly.

However, on Deploy Preview builds the cache seems to always be empty - even on repeat builds. Is this a know limitation of the plugin?

We were able to remove the re-install overhead of the plugin by following the steps in netlify/build#1134 - but the yarn command still takes ~1 minute on the Deploy Preview builds for some reason - compared to ~1 second on the develop branch. (related?)

Deploy Preview log on a repeat build:

Deploy Preview #103: feature/footer-drawing@80783d2.

1:14:00 AM: Build ready to start
1:14:02 AM: build-image version: 2dbd444fcdce00cf06325060a8238d5ae3e86774
1:14:02 AM: build-image tag: v3.3.7
1:14:02 AM: buildbot version: ed44b74dccd74a30dec84aacc6e49a3511498577
1:14:02 AM: Fetching cached dependencies
1:14:02 AM: Starting to download cache of 207.6MB
1:14:10 AM: Finished downloading cache in 7.504368281s
1:14:10 AM: Starting to extract cache
1:14:18 AM: Finished extracting cache in 8.584933729s
1:14:18 AM: Finished fetching cache in 16.152955811s
1:14:18 AM: Starting to prepare the repo for build
1:14:19 AM: Preparing Git Reference pull/103/head
1:14:21 AM: Starting build script
1:14:21 AM: Installing dependencies
1:14:22 AM: Started restoring cached node version
1:14:26 AM: Finished restoring cached node version
1:14:26 AM: Attempting node version 'v10.15.1' from .nvmrc
1:14:27 AM: v10.15.1 is already installed.
1:14:27 AM: Now using node v10.15.1 (npm v6.4.1)
1:14:28 AM: Attempting ruby version 2.6.2, read from environment
1:14:29 AM: Using ruby version 2.6.2
1:14:29 AM: Using PHP version 5.6
1:14:29 AM: Started restoring cached node modules
1:14:29 AM: Finished restoring cached node modules
1:14:29 AM: Started restoring cached yarn cache
1:14:29 AM: Finished restoring cached yarn cache
1:14:30 AM: Installing NPM modules using Yarn version 1.13.0
1:14:31 AM: yarn install v1.13.0
1:14:31 AM: [1/4] Resolving packages...
1:14:32 AM: [2/4] Fetching packages...
1:15:03 AM: info [email protected]: The platform "linux" is incompatible with this module.
1:15:03 AM: info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
1:15:03 AM: info [email protected]: The platform "linux" is incompatible with this module.
1:15:03 AM: info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
1:15:03 AM: [3/4] Linking dependencies...
1:15:03 AM: warning " > [email protected]" has unmet peer dependency "webpack@^4.0.0 || ^5.0.0".
1:15:03 AM: warning "gatsby > [email protected]" has unmet peer dependency "@types/react@^15.0.0 || ^16.0.0".
1:15:03 AM: warning "gatsby > @typescript-eslint/eslint-plugin > [email protected]" has unmet peer dependency "typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta".
1:15:03 AM: warning " > [email protected]" has incorrect peer dependency "eslint@^6.6.0".
1:15:03 AM: warning "gatsby-plugin-netlify > [email protected]" has unmet peer dependency "webpack@>=4.4.0".
1:15:03 AM: warning "gatsby-plugin-transition-link > babel-preset-gatsby-package > @babel/[email protected]" has unmet peer dependency "@babel/core@^7.0.0-0".
1:15:03 AM: warning "gatsby-plugin-transition-link > babel-preset-gatsby-package > @babel/preset-flow > @babel/[email protected]" has unmet peer dependency "@babel/core@^7.0.0-0".
1:15:03 AM: warning "gatsby-plugin-transition-link > babel-preset-gatsby-package > @babel/preset-flow > @babel/plugin-transform-flow-strip-types > @babel/[email protected]" has unmet peer dependency "@babel/core@^7.0.0-0".
1:15:03 AM: warning " > [email protected]" has incorrect peer dependency "three@>=0.114".
1:15:35 AM: [4/4] Building fresh packages...
1:15:40 AM: Done in 69.20s.
1:15:40 AM: NPM modules installed using Yarn
1:15:40 AM: Started restoring cached go cache
1:15:40 AM: Finished restoring cached go cache
1:15:40 AM: unset GOOS;
1:15:40 AM: unset GOARCH;
1:15:40 AM: export GOROOT='/opt/buildhome/.gimme/versions/go1.12.linux.amd64';
1:15:40 AM: export PATH="/opt/buildhome/.gimme/versions/go1.12.linux.amd64/bin:${PATH}";
1:15:40 AM: go version >&2;
1:15:40 AM: export GIMME_ENV='/opt/buildhome/.gimme/env/go1.12.linux.amd64.env';
1:15:40 AM: go version go1.12 linux/amd64
1:15:40 AM: Installing missing commands
1:15:40 AM: Verify run directory
1:15:42 AM: 
1:15:42 AM: ┌─────────────────────────────┐
1:15:42 AM: │        Netlify Build        │
1:15:42 AM: └─────────────────────────────┘
1:15:42 AM: 
1:15:42 AM: ❯ Version
1:15:42 AM:   @netlify/build 0.4.3
1:15:42 AM: 
1:15:42 AM: ❯ Flags
1:15:42 AM:   mode: buildbot
1:15:42 AM: 
1:15:42 AM: ❯ Current directory
1:15:42 AM:   /opt/build/repo
1:15:42 AM: 
1:15:42 AM: ❯ Config file
1:15:42 AM:   /opt/build/repo/netlify.toml
1:15:42 AM: 
1:15:42 AM: ❯ Context
1:15:42 AM:   deploy-preview
1:15:44 AM: 
1:15:44 AM: ❯ Loading plugins
1:15:44 AM:    - [email protected]
1:15:44 AM: 
1:15:44 AM: ┌────────────────────────────────────────────────────────┐
1:15:44 AM: │ 1. onPreBuild command from netlify-plugin-gatsby-cache │
1:15:44 AM: └────────────────────────────────────────────────────────┘
1:15:44 AM: 
1:15:44 AM: No Gatsby cache found. Building fresh.
1:15:44 AM: 
1:15:44 AM: (netlify-plugin-gatsby-cache onPreBuild completed in 8ms)
1:15:44 AM: 
1:15:44 AM: ┌────────────────────────────────────┐
1:15:44 AM: │ 2. build.command from netlify.toml │
1:15:44 AM: └────────────────────────────────────┘
1:15:44 AM: 
1:15:44 AM: $ yarn build
1:23:34 AM: yarn run v1.13.0
1:23:34 AM: $ GATSBY_EXPERIMENTAL_PAGE_BUILD_ON_DATA_CHANGES=true gatsby build --log-pages
1:23:34 AM: success open and validate gatsby-configs - 0.113s
1:23:34 AM: success load plugins - 1.494s
1:23:34 AM: success onPreInit - 0.012s
1:23:34 AM: success initialize cache - 0.011s
1:23:34 AM: success copy gatsby files - 0.083s
1:23:34 AM: success onPreBootstrap - 0.010s
1:23:34 AM: success createSchemaCustomization - 0.006s
1:23:34 AM: success source and transform nodes - 0.696s
1:23:34 AM: success building schema - 0.471s
1:23:34 AM: success createPages - 0.222s
1:23:34 AM: success createPagesStatefully - 0.141s
1:23:34 AM: success onPreExtractQueries - 0.000s
1:23:34 AM: success update schema - 0.102s
1:23:34 AM: success extract queries from components - 0.834s
1:23:34 AM: success write out requires - 0.005s
1:23:34 AM: success write out redirect data - 0.001s
1:23:34 AM: success Build manifest and related icons - 0.446s
1:23:34 AM: success onPostBootstrap - 0.448s
1:23:34 AM: ⠀
1:23:34 AM: info bootstrap finished - 7.460 s
1:23:34 AM: ⠀
1:23:34 AM: Webpack Bundle Analyzer is started at http://127.0.0.1:3001
1:23:34 AM: Use Ctrl+C to close it
1:23:34 AM: success Building production JavaScript and CSS bundles - 83.182s
1:23:34 AM: success Rewriting compilation hashes - 0.001s
1:23:34 AM: success Downloading remote files - 13.993s - 67/67 4.79/s
1:23:34 AM: success run queries - 99.006s - 19/19 0.19/s
1:23:34 AM: (node:1633) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
1:23:34 AM: success Building static HTML for pages - 21.481s - 16/16 0.74/s
1:23:34 AM: success Delete previous page data - 0.000s
1:23:34 AM: success Generating image thumbnails - 377.603s - 468/468 1.24/s
1:23:34 AM: warning app-c4b73d405234476ae39c.js.map is 4.16 MB, and won't be precached. Configure maximumFileSizeToCacheInBytes to change this limit.
1:23:34 AM: warning static/ce6ef49ec41fd5ce26895a8ddbd70a87/b0260/b9f5c0ab-9347-462d-8d26-2d13c4233e11_14-case-antler-header02.png is 2.97 MB, and won't be precached. Configure maximumFileSizeToCacheInBytes to change this limit.
1:23:34 AM: info Generated public/sw.js, which will precache 565 files, totaling 51355309 bytes.
1:23:34 AM: The following pages will be precached:
1:23:34 AM: /offline-plugin-app-shell-fallback/index.html
1:23:34 AM: success onPostBuild - 0.452s
1:23:34 AM: info Done building in 469.796 sec
1:23:34 AM: info Built pages:
1:23:34 AM: Updated page: /preview
1:23:34 AM: Updated page: /project
1:23:34 AM: Updated page: /santa-tracker
1:23:34 AM: Updated page: /interland
1:23:34 AM: Updated page: /antler
1:23:34 AM: Updated page: /just-food-for-dogs
1:23:34 AM: Updated page: /vardagskampen
1:23:34 AM: Updated page: /proxy
1:23:34 AM: Updated page: /offline-plugin-app-shell-fallback/
1:23:34 AM: Updated page: /404/
1:23:34 AM: Updated page: /about/
1:23:34 AM: Updated page: /contact/
1:23:34 AM: Updated page: /
1:23:34 AM: Updated page: /lab/
1:23:34 AM: Updated page: /scroll-test/
1:23:34 AM: Updated page: /404.html
1:23:34 AM: Done in 470.19s.
1:23:34 AM: 
1:23:34 AM: (build.command completed in 7m 50.5s)
1:23:34 AM: 
1:23:34 AM: ┌─────────────────────────────────────────────────────────┐
1:23:34 AM: │ 3. onPostBuild command from netlify-plugin-gatsby-cache │
1:23:34 AM: └─────────────────────────────────────────────────────────┘
1:23:34 AM: 
1:23:35 AM: Stored the Gatsby cache to speed up future builds.
1:23:35 AM: 
1:23:35 AM: (netlify-plugin-gatsby-cache onPostBuild completed in 1s)
1:23:35 AM: 
1:23:35 AM: ┌─────────────────────────────┐
1:23:35 AM: │   Netlify Build Complete    │
1:23:35 AM: └─────────────────────────────┘
1:23:35 AM: 
1:23:35 AM: (Netlify Build completed in 7m 53.1s)
1:23:36 AM: Caching artifacts
1:23:36 AM: Started saving node modules
1:23:36 AM: Finished saving node modules
1:23:36 AM: Started saving yarn cache
1:23:36 AM: Finished saving yarn cache
1:23:36 AM: Started saving pip cache
1:23:36 AM: Finished saving pip cache
1:23:36 AM: Started saving emacs cask dependencies
1:23:36 AM: Finished saving emacs cask dependencies
1:23:36 AM: Started saving maven dependencies
1:23:36 AM: Finished saving maven dependencies
1:23:36 AM: Started saving boot dependencies
1:23:37 AM: Finished saving boot dependencies
1:23:37 AM: Started saving go dependencies
1:23:37 AM: Finished saving go dependencies
1:23:37 AM: Build script success
1:23:37 AM: Starting to deploy site from 'public'
1:23:37 AM: Creating deploy tree asynchronously
1:23:37 AM: Creating deploy upload records
1:23:39 AM: 23 new files to upload
1:23:39 AM: 0 new functions to upload
1:23:41 AM: Starting post processing
1:23:48 AM: Post processing done
1:23:48 AM: Site is live
1:24:26 AM: Finished processing build request in 10m24.269252737s

Working with Strapi as CMS ?

I was wondering if incremental build was working with strapi as cms. My app is building fine but on data change from strapi nothing happen in log ...

Caused "Error fetching branch"

We encountered an issue where when using the cache, Netlify would have an "Error fetching branch" during the "preparing repo" stage:

10:26:50 AM: Starting to prepare the repo for build
10:26:51 AM: Preparing Git Reference refs/heads/master
10:27:00 AM: Error fetching branch: https://github.com/datawire/getambassador.io refs/heads/master
10:27:00 AM: Creating deploy upload records
10:27:00 AM: Failing build: Failed to prepare repo
10:27:00 AM: Failed during stage 'preparing repo': exit status 1

The error first appeared seemingly spontaneously on multiple branches with unrelated changes. This error did not happen when doing a "Clear cache and deploy site", but the error would immediately return for the next cache-using deploy. We eventually resolved the issue by uninstalling then re-installing the "Gatsby cache" plugin, which seems to indite the plugin, though looking at the source of the plugin I'm flabbergasted at how this is possible.

There is a thread on the support forum with some more info: https://answers.netlify.com/t/cache-builds-fail-during-preparing-repo-step-error-fetching-branch/38856/

Perry has suggested that the package.json might be useful for tracking down the issue. I've also included the .gitmodules file, since that's the only other file that I would think might affect "Error fetching branch":

Static HTML page doesn't update on deploy when data changes

Hello there,
I have a problem with this plugin, that static generated HTML page which loads as a first has cached old data. I am using Shopify as a source of data and I have set deploy to trigger on product create/update/deletion. So for example first second or 2 shows old list of products and then, when React hydrates, new list is loaded. When I clear cache in Netlify or when I update code with something on list page, new static site is generated. Is there any way to prevent static HTML sites to be cached via this plugin?

Setup:

"gatsby": "^2.25.3",
"netlify-plugin-gatsby-cache": "^0.3.2",
"react": "^16.9.0",

Does this plugin work with yarn workspaces monorepos?

I have a monorepo managed with Lerna and yarn with a package that is my frontend (which uses Gatbsy) and another that is my CMS (Sanity Studio) both deployed on Netlify.

Here's my lerna.json just for reference

{
  "packages": [
    "packages/A",
    "packages/frontend",
    "packages/B",
    "packages/cms"
  ],
  "version": "independent",
  "npmClient": "yarn",
  "useWorkspaces": true
}

A and B packages are just dependencies of the frontend package.

I tried to think about where should I put my netlify.toml which I didn't need until now. It would look just like this:

[[plugins]]
  package = "netlify-plugin-gatsby-cache"

Do you have any suggestions on where I should put my frontend netlify.toml?

Error in netlify build after enabling plugin

/opt/build/repo/node_modules/yoga-layout-prebuilt/yoga-layout/build/Release/nbind.js:53
throw ex;
^
Error: Callback was already called.
at throwError (/opt/build/repo/node_modules/neo-async/async.js:16:11)
at /opt/build/repo/node_modules/neo-async/async.js:2818:7
at processTicksAndRejections (internal/process/task_queues.js:79:11)

Multiple Netlify CI builds fail

When pushing new changes to my deploy preview branch with incremental builds enabled, there are issues with the GatsbyJS graphQL static queries that does not happen when testing the production build locally.

I've confirmed that this issue does not happen when I clear the cache and redeploy from the deployment UI.

https://app.netlify.com/sites/leatherspa/deploys/5f0a288c08760800082f6c81
https://app.netlify.com/sites/leatherspa/deploys/5f0a0515a3a14200083346ea
https://app.netlify.com/sites/leatherspa/deploys/5f0a07501933c2c3599d7363

Here are the following builds that failed. There is a cache hit as expected and the failures are symptomatic of the underlying content changes I made between the builds. Perhaps the cache invalidation is not validating whether markdown content has changed?

Build fails when using sharp

Hi @jlengstorf,
I've tried your plugin with my Gatsby site deployed on Netlify today.
I'm using sharp module to optimise images during page generation:

gatsby-plugin-sharp

Part of my package.json (unfortunately the project is not public and I can't share the codebase):

"dependencies": {
    "gatsby": "^2.19.12",
     ...
    "gatsby-plugin-sharp": "^2.4.5",
     ...
  },

The Netlify build failed after I applied the plugin (according to the instruction).

1:42:50 PM: Starting Netlify Build...
1:42:53 PM: 
1:42:53 PM: ┌─────────────────────────────┐
1:42:53 PM: │        Netlify Build        │
1:42:53 PM: └─────────────────────────────┘
1:42:53 PM: 
1:42:53 PM: ❯ Version
1:42:53 PM:   @netlify/build 0.3.8
1:42:53 PM: 
1:42:53 PM: ❯ Flags
1:42:53 PM:   mode: buildbot
1:42:53 PM: 
1:42:53 PM: ❯ Current directory
1:42:53 PM:   /opt/build/repo
1:42:53 PM: 
1:42:53 PM: ❯ Config file
1:42:53 PM:   /opt/build/repo/netlify.toml
1:42:53 PM: 
1:42:53 PM: ❯ Context
1:42:53 PM:   production
1:42:53 PM: 
1:42:53 PM: ❯ Installing plugins
1:42:53 PM:    - netlify-plugin-gatsby-cache
1:43:35 PM: 
1:43:35 PM: ❯ Loading plugins
1:43:35 PM:    - [email protected]
1:43:35 PM: 
1:43:35 PM: ┌────────────────────────────────────────────────────────┐
1:43:35 PM: │ 1. onPreBuild command from netlify-plugin-gatsby-cache │
1:43:35 PM: └────────────────────────────────────────────────────────┘
1:43:35 PM: 
1:43:35 PM: No Gatsby cache found. Building fresh.
1:43:35 PM: 
1:43:35 PM: (netlify-plugin-gatsby-cache onPreBuild completed in 6ms)
1:43:35 PM: 
1:43:35 PM: ┌──────────────────────────────────────────────────────────────────┐
1:43:35 PM: │ 2. build.lifecycle.onBuild command from netlify.toml config file │
1:43:35 PM: └──────────────────────────────────────────────────────────────────┘
1:43:35 PM: 
1:43:35 PM: $ yarn build
1:43:39 PM: yarn run v1.9.4
1:43:39 PM: $ npm run clean && gatsby build
1:43:39 PM: > [email protected] clean /opt/build/repo
1:43:39 PM: > gatsby clean
1:43:39 PM: info Deleting .cache, public
1:43:39 PM: info Successfully deleted directories
1:43:39 PM: Using environment config: 'production'
1:43:39 PM: success open and validate gatsby-configs - 0.095s
1:43:39 PM: error
1:43:39 PM: Something went wrong installing the "sharp" module
1:43:39 PM: Module did not self-register.
1:43:39 PM: - Remove the "node_modules/sharp" directory, run "npm install" and look for errors
1:43:39 PM: - Consult the installation documentation at https://sharp.pixelplumbing.com/en/stable/install/
1:43:39 PM: - Search for this error at https://github.com/lovell/sharp/issues
1:43:39 PM: not finished load plugins - 0.196s
1:43:39 PM: error Command failed with exit code 1.
1:43:39 PM: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
1:43:39 PM: 
1:43:39 PM: ┌─────────────────────────────┐
1:43:39 PM: │        Build failed         │
1:43:39 PM: └─────────────────────────────┘
1:43:39 PM: 
1:43:39 PM:   Error message
1:43:39 PM:   Command failed with exit code 1: yarn build
1:43:39 PM: 
1:43:39 PM:   Error location
1:43:39 PM:   In configuration "build.lifecycle.onBuild" command:
1:43:39 PM:   yarn build
1:43:39 PM:

After I removed the plugin from netlify.toml the Netlify builds work again.

Generating images renditions is the main part of the build process of my website.
Is that a known issue? Maybe some hints how I can fix it?

GraphQL queries to service fail after installing plugin

Hi there

I use https://formium.io/

When I clear cache the build works, but when the cache is loaded it fails.

7:50:16 AM: success createPagesStatefully - 0.109s
7:50:16 AM: success Cleaning up stale page-data - 0.002s
7:50:16 AM: success update schema - 0.044s
7:50:16 AM: success onPreExtractQueries - 0.004s
7:50:21 AM: error There was an error in your GraphQL query:
7:50:21 AM: Unknown argument "slug" on field "formiumForm" of type "Query".
7:50:21 AM: GraphQL request:3:17
7:50:21 AM: 2 | {
7:50:21 AM: 3 | formiumForm(slug: { eq: "example" }) {
7:50:21 AM: | ^
7:50:21 AM: 4 | id
7:50:21 AM: error There was an error in your GraphQL query:
7:50:21 AM: Cannot query field "createAt" on type "FormiumForm".
7:50:21 AM: If you don't expect "createAt" to exist on the type "FormiumForm" it is most likely a typo.
However, if you expect "createAt" to exist there are a couple of solutions to common problems:
7:50:21 AM: - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server
7:50:21 AM: - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have
7:50:21 AM: - You want to optionally use your field "createAt" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add at least one entry with that field ("dummy content")
7:50:21 AM: It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "FormiumForm":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
7:50:21 AM: error There was an error in your GraphQL query:
7:50:21 AM: Cannot query field "name" on type "FormiumForm".
7:50:21 AM: If you don't expect "name" to exist on the type "FormiumForm" it is most likely a typo.
However, if you expect "name" to exist there are a couple of solutions to common problems:
7:50:21 AM: - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server
7:50:21 AM: - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have
7:50:21 AM: - You want to optionally use your field "name" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add at least one entry with that field ("dummy content")
7:50:21 AM: It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "FormiumForm":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
7:50:21 AM: error There was an error in your GraphQL query:
7:50:21 AM: Cannot query field "projectId" on type "FormiumForm".
7:50:21 AM: If you don't expect "projectId" to exist on the type "FormiumForm" it is most likely a typo.
However, if you expect "projectId" to exist there are a couple of solutions to common problems:
7:50:21 AM: - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server
7:50:21 AM: - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have
7:50:21 AM: - You want to optionally use your field "projectId" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add at least one entry with that field ("dummy content")
7:50:21 AM: It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "FormiumForm":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
7:50:21 AM: error There was an error in your GraphQL query:
7:50:21 AM: Cannot query field "slug" on type "FormiumForm".
7:50:21 AM: If you don't expect "slug" to exist on the type "FormiumForm" it is most likely a typo.
However, if you expect "slug" to exist there are a couple of solutions to common problems:
7:50:21 AM: - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server
7:50:21 AM: - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have
7:50:21 AM: - You want to optionally use your field "slug" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add at least one entry with that field ("dummy content")
7:50:21 AM: It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "FormiumForm":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
7:50:21 AM: error There was an error in your GraphQL query:
7:50:21 AM: Cannot query field "updateAt" on type "FormiumForm".
7:50:21 AM: If you don't expect "updateAt" to exist on the type "FormiumForm" it is most likely a typo.
However, if you expect "updateAt" to exist there are a couple of solutions to common problems:
7:50:21 AM: - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server
7:50:21 AM: - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have
7:50:21 AM: - You want to optionally use your field "updateAt" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add at least one entry with that field ("dummy content")
7:50:21 AM: It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "FormiumForm":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
7:50:21 AM: error There was an error in your GraphQL query:
7:50:21 AM: Cannot query field "version" on type "FormiumForm".
7:50:21 AM: If you don't expect "version" to exist on the type "FormiumForm" it is most likely a typo.
However, if you expect "version" to exist there are a couple of solutions to common problems:
7:50:21 AM: - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server
7:50:21 AM: - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have
7:50:21 AM: - You want to optionally use your field "version" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add at least one entry with that field ("dummy content")
7:50:21 AM: It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "FormiumForm":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
7:50:21 AM: failed extract queries from components - 4.900s
7:50:21 AM: npm ERR! code ELIFECYCLE
7:50:21 AM: npm ERR! errno 1
7:50:21 AM: npm ERR! [email protected] build: cross-env NODE_OPTIONS="-r esm" GATSBY_EXPERIMENTAL_PAGE_BUILD_ON_DATA_CHANGES=true gatsby build --log-pages
7:50:21 AM: npm ERR! Exit status 1
7:50:21 AM: npm ERR!
7:50:21 AM: npm ERR! Failed at the [email protected] build script.
7:50:21 AM: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
7:50:21 AM: npm ERR! A complete log of this run can be found in:
7:50:21 AM: npm ERR! /opt/buildhome/.npm/_logs/2021-01-20T05_50_21_560Z-debug.log
7:50:21 AM:
7:50:21 AM: ────────────────────────────────────────────────────────────────
7:50:21 AM: "build.command" failed
7:50:21 AM: ────────────────────────────────────────────────────────────────
7:50:21 AM:
7:50:21 AM: Error message
7:50:21 AM: Command failed with exit code 1: npm run build
7:50:21 AM:
7:50:21 AM: Error location
7:50:21 AM: In Build command from Netlify app:
7:50:21 AM: npm run build
7:50:21 AM:
7:50:21 AM: Resolved config
7:50:21 AM: build:
7:50:21 AM: base: /opt/build/repo/frontend
7:50:21 AM: command: npm run build
7:50:21 AM: commandOrigin: ui
7:50:21 AM: environment:
7:50:21 AM: - FORMIUM_TOKEN
7:50:21 AM: - GATSBY_FORMIUM_PROJECTID
7:50:21 AM: - SANITY_TOKEN
7:50:21 AM: functions: /opt/build/repo/frontend/functions
7:50:21 AM: publish: /opt/build/repo/frontend/public
7:50:21 AM: plugins:
7:50:21 AM: - inputs: {}
7:50:21 AM: origin: ui
7:50:21 AM: package: netlify-plugin-gatsby-cache
7:50:21 AM: Caching artifacts
7:50:21 AM: Started saving node modules
7:50:21 AM: Finished saving node modules
7:50:21 AM: Started saving build plugins
7:50:21 AM: Finished saving build plugins
7:50:21 AM: Started saving pip cache
7:50:21 AM: Finished saving pip cache
7:50:21 AM: Started saving emacs cask dependencies
7:50:21 AM: Finished saving emacs cask dependencies
7:50:21 AM: Started saving maven dependencies
7:50:21 AM: Finished saving maven dependencies
7:50:21 AM: Started saving boot dependencies
7:50:21 AM: Finished saving boot dependencies
7:50:21 AM: Started saving rust rustup cache
7:50:21 AM: Finished saving rust rustup cache
7:50:21 AM: Started saving go dependencies
7:50:21 AM: Finished saving go dependencies
7:50:21 AM: Build failed due to a user error: Build script returned non-zero exit code: 2
7:50:21 AM: Failing build: Failed to build site
7:50:21 AM: Failed during stage 'building site': Build script returned non-zero exit code: 2
7:50:22 AM: Finished processing build request in 1m4.958713578s

Does not detect change to component on index page

This plugin is missing a "manifest.yml"

Hi,

I am getting this error when I try to deploy.

Does anyone had this before?
About 20 days ago everything was ok.

Caching issue Ghost CMS

Content changes (updating, adding, or deleting), don't show after the first webhook triggered deploy. The changes usually show on the next or following build. Thoughts?

netlify.toml

`[build]
command = "GATSBY_EXPERIMENTAL_PAGE_BUILD_ON_DATA_CHANGES=true gatsby build --log-pages"
publish = "demo/public"

[template]
incoming-hooks = ["Ghost"]

[[plugins]]
package = "netlify-plugin-gatsby-cache"`