Gatsby.js, yarn workspaces and caching node_modules

fool · March 17, 2020, 1:38pm

Hi @pdeka - not sure what is causing that from the small log snippet you share, but I’d debug in our build image running locally:

We definitely may not be handling cache in the way that you/yarn expect though, as you can see we have some fairly specific cache handling in our build logic:

github.com

netlify/build-image/blob/xenial/run-build-functions.sh#L73-L117


      
          : ${BUNDLER_FLAGS=""}
          
          
# Feature flags are a comma-separated list.
          # The following logic relies on the fact that feature flags cannot currently
          # have escaped commas in their value. Otherwise, parsing the list as an array,
          # e.g. using `IFS="," read -ra <<<"$1"` would be needed.
          has_feature_flag() {
            if [[ "${1}," == *"${2},"* ]]
            then
              return 0
            else
              return 1
            fi
          }
          
          
install_deps() {
            [ -f $1 ] || return 0
            [ -f $3 ] || return 0
          
          
  SHA1="$(shasum $1)-$2"

This file has been truncated. show original

Topic		Replies	Views
Improved caching for yarn workspaces Updates building	7	3487	May 6, 2021
No yarn workspaces detected despite using workspaces for build command Support settings-config , building , caching	15	6757	February 3, 2022
After activating Build Plugins Beta my site no longer caches yarn node_modules (Gatsby incremental builds) Support building , deployment , gatsby	4	1636	May 22, 2020
Yarn 2 needs proper support in builds Features building , caching	8	3306	August 14, 2021
Node version caching Support deployment , gatsby	6	1537	March 7, 2020

Gatsby.js, yarn workspaces and caching node_modules

Related topics