Hi, @RyanPinPB. This is a public repo so I cloned it and installed the name version of node. Then I ran npm install
and npm run build
. This was the output of the build command for me locally (meaning outside of Netlify):
$ npm run build
> using-gatsby-source-wordpress-experimental@0.0.1 build /home/username/tmp/pdm-gatsby
> gatsby build
╔════════════════════════════════════════════════════════════════════════╗
║ ║
║ Gatsby collects anonymous usage analytics ║
║ to help improve Gatsby for all users. ║
║ ║
║ If you'd like to opt-out, you can use `gatsby telemetry --disable` ║
║ To learn more, checkout https://gatsby.dev/telemetry ║
║ ║
╚════════════════════════════════════════════════════════════════════════╝
success open and validate gatsby-configs - 0.055s
success load plugins - 0.989s
success onPreInit - 0.036s
success delete html and css files from previous builds - 0.003s
success initialize cache - 0.006s
success copy gatsby files - 0.022s
success onPreBootstrap - 0.013s
⠀
info gatsby-source-wordpress
This is either your first build or the cache was cleared.
Please wait while your WordPress data is synced to your Gatsby cache.
Maybe now's a good time to get up and stretch? :D
success gatsby-source-wordpress writing GraphQL queries to disk at ./WordPress/GraphQL/ - 0.298s
success gatsby-source-wordpress ingest WPGraphQL schema - 2.644s
success createSchemaCustomization - 6.701s
success gatsby-source-wordpress Tag - 2.303s - fetched 0
success gatsby-source-wordpress UserRole - 2.333s - fetched 0
success gatsby-source-wordpress Taxonomy - 2.356s - fetched 3
success gatsby-source-wordpress User - 2.549s - fetched 1
success gatsby-source-wordpress Page - 2.800s - fetched 6
success gatsby-source-wordpress fetch root fields - 3.351s
success gatsby-source-wordpress Category - 3.390s - fetched 1
success gatsby-source-wordpress ContentType - 3.475s - fetched 3
success gatsby-source-wordpress Comment - 3.480s - fetched 1
success gatsby-source-wordpress PostFormat - 3.549s - fetched 0
success gatsby-source-wordpress Menu - 3.572s - fetched 2
success gatsby-source-wordpress Post - 3.646s - fetched 2
success gatsby-source-wordpress MenuItem - 3.671s - fetched 10
success gatsby-source-wordpress MediaItem - 0.911s - fetched 1
success gatsby-source-wordpress creating nodes - 0.915s
success gatsby-source-wordpress fetching nodes - 4.594s - 30 total
success Downloading remote files - 0.301s - 1/1 3.33/s
success Checking for changed pages - 0.001s
success source and transform nodes - 5.284s
success building schema - 0.820s
info Total nodes: 149, SitePage nodes: 9 (use --verbose for breakdown)
success createPages - 0.054s
success Checking for changed pages - 0.001s
success createPagesStatefully - 0.116s
success update schema - 0.039s
success onPreExtractQueries - 0.001s
warning Using the global `graphql` tag is deprecated, and will not be supported in v3.
Import it instead like: import { graphql } from 'gatsby' in file:
/home/username/tmp/pdm-gatsby/src/pages/projects.js
success extract queries from components - 1.296s
warning The GraphQL query in the non-page component "/home/username/tmp/pdm-gatsby/src/templates/single/Page.js" will not be run.
Exported queries are only executed for Page components. It's possible you're
trying to create pages in your gatsby-node.js and that's failing for some
reason.
If the failing component(s) is a regular component and not intended to be a page
component, you generally want to use a <StaticQuery> (https://gatsbyjs.org/docs/static-query)
instead of exporting a page query.
If you're more experienced with GraphQL, you can also export GraphQL
fragments from components and compose the fragments in the Page component
query and pass data down into the child component — https://graphql.org/learn/queries/#fragments
success write out redirect data - 0.018s
⠁ vips_value_hash: no case for NULL
type 64, gchararray
generic 53, GParamString
vips_value_hash: no case for 0.000000
type 60, gdouble
generic 109, GParamDouble
vips_value_hash: no case for FALSE
type 20, gboolean
generic 76, GParamBoolean
vips_value_hash: no case for ((VipsAccess) VIPS_ACCESS_RANDOM)
type 73595104, VipsAccess
generic 80, GParamEnum
vips_value_hash: no case for FALSE
type 20, gboolean
generic 76, GParamBoolean
Segmentation fault (core dumped)
npm ERR! code ELIFECYCLE
npm ERR! errno 139
npm ERR! using-gatsby-source-wordpress-experimental@0.0.1 build: `gatsby build`
npm ERR! Exit status 139
npm ERR!
npm ERR! Failed at the using-gatsby-source-wordpress-experimental@0.0.1 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/username/.npm/_logs/2020-11-25T08_35_14_599Z-debug.log
As you can see the error is exactly the same:
success write out redirect data - 0.018s
⠁ vips_value_hash: no case for NULL
type 64, gchararray
generic 53, GParamString
vips_value_hash: no case for 0.000000
type 60, gdouble
generic 109, GParamDouble
vips_value_hash: no case for FALSE
type 20, gboolean
generic 76, GParamBoolean
vips_value_hash: no case for ((VipsAccess) VIPS_ACCESS_RANDOM)
type 73595104, VipsAccess
generic 80, GParamEnum
vips_value_hash: no case for FALSE
type 20, gboolean
generic 76, GParamBoolean
Segmentation fault (core dumped)
In other words, there is some error with your build process but Netlify isn’t causing it. This happens anytime this build is done, not just at Netlify.
Because this isn’t a Netlify specific issue, our support team won’t be able to provide more assistance. Our support scope is limited to Netlify specific issues and this is a bug in third-party code. Our support scope doesn’t include third-party code.
If you resolve the local build issue however and the build at Netlify still fails, please let us know. Also, other people here may be willing to troubleshoot this issue with you and the question is still welcome. It is just that our support team doesn’t have the resources to troubleshoot third-party code. Others are certainly welcome to do so, however.