I just updated to gatsby-plugin image and made some necessary package upgrades with gatsbyjs and have no issues locally but Netlify is having issues deploying my site in staging

Support
,
1

I just updated to gatsby-plugin image and made some necessary package upgrades with gatsbyjs and have no issues locally but Netlify is having issues deploying my site in staging. Here is what I got in the console (partial because too long):

Started saving yarn cache
6:17:03 PM: node:internal/modules/cjs/loader:936
6:17:03 PM: throw err;
6:17:03 PM: ^
6:17:03 PM: Error: Cannot find module ‘./reducers/page-tree’
6:17:03 PM: Require stack:
6:17:03 PM: - /opt/build/repo/node_modules/gatsby-cli/lib/reporter/redux/index.js
6:17:03 PM: - /opt/build/repo/node_modules/gatsby-cli/lib/reporter/redux/actions.js
6:17:03 PM: - /opt/build/repo/node_modules/gatsby-cli/lib/reporter/reporter.js
6:17:03 PM: - /opt/build/repo/node_modules/gatsby/dist/redux/reducers/program.js
6:17:03 PM: - /opt/build/repo/node_modules/gatsby/dist/redux/reducers/index.js
6:17:03 PM: - /opt/build/repo/node_modules/gatsby/dist/redux/index.js
6:17:03 PM: - /opt/build/repo/node_modules/gatsby/dist/utils/jobs/worker-messaging.js
6:17:03 PM: - /opt/build/repo/node_modules/gatsby/dist/utils/worker/child/index.js
6:17:03 PM: - /opt/build/repo/node_modules/gatsby-worker/dist/child.js
6:17:03 PM: at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
6:17:03 PM: at Function.Module._load (node:internal/modules/cjs/loader:778:27)
6:17:03 PM: at Module.require (node:internal/modules/cjs/loader:1005:19)
6:17:03 PM: at require (node:internal/modules/cjs/helpers:102:18)
6:17:03 PM: at Object. (/opt/build/repo/node_modules/gatsby-cli/lib/reporter/redux/index.js:10:17)
6:17:03 PM: at Module._compile (node:internal/modules/cjs/loader:1101:14)
6:17:03 PM: at Object.Module._extensions…js (node:internal/modules/cjs/loader:1153:10)
6:17:03 PM: at Module.load (node:internal/modules/cjs/loader:981:32)
6:17:03 PM: at Function.Module._load (node:internal/modules/cjs/loader:822:12)
6:17:03 PM: at Module.require (node:internal/modules/cjs/loader:1005:19) {
6:17:03 PM: code: ‘MODULE_NOT_FOUND’,
6:17:03 PM: requireStack: [
6:17:03 PM: ‘/opt/build/repo/node_modules/gatsby-cli/lib/reporter/redux/index.js’,
6:17:03 PM: ‘/opt/build/repo/node_modules/gatsby-cli/lib/reporter/redux/actions.js’,
6:17:03 PM: ‘/opt/build/repo/node_modules/gatsby-cli/lib/reporter/reporter.js’,
6:17:03 PM: ‘/opt/build/repo/node_modules/gatsby/dist/redux/reducers/program.js’,
6:17:03 PM: ‘/opt/build/repo/node_modules/gatsby/dist/redux/reducers/index.js’,
6:17:03 PM: ‘/opt/build/repo/node_modules/gatsby/dist/redux/index.js’,
6:17:03 PM: ‘/opt/build/repo/node_modules/gatsby/dist/utils/jobs/worker-messaging.js’,
6:17:03 PM: ‘/opt/build/repo/node_modules/gatsby/dist/utils/worker/child/index.js’,
6:17:03 PM: ‘/opt/build/repo/node_modules/gatsby-worker/dist/child.js’
6:17:03 PM: ]
6:17:03 PM: }
6:17:03 PM: node:internal/modules/cjs/loader:936
6:17:03 PM: throw err;
6:17:03 PM: ^
6:17:03 PM: Error: Cannot find module ‘./reducers/page-tree’
6:17:03 PM: Require stack:
6:17:03 PM: - /opt/build/repo/node_modules/gatsby-cli/lib/reporter/redux/index.js
6:17:03 PM: - /opt/build/repo/node_modules/gatsby-cli/lib/reporter/redux/actions.js
6:17:03 PM: - /opt/build/repo/node_modules/gatsby-cli/lib/reporter/reporter.js
6:17:03 PM: - /opt/build/repo/node_modules/gatsby/dist/redux/reducers/program.js
6:17:03 PM: - /opt/build/repo/node_modules/gatsby/dist/redux/reducers/index.js
6:17:03 PM: - /opt/build/repo/node_modules/gatsby/dist/redux/index.js
6:17:03 PM: - /opt/build/repo/node_modules/gatsby/dist/utils/jobs/worker-messaging.js
6:17:03 PM: - /opt/build/repo/node_modules/gatsby/dist/utils/worker/child/index.js
6:17:03 PM: - /opt/build/repo/node_modules/gatsby-worker/dist/child.js
6:17:03 PM: at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
6:17:03 PM: at Function.Module._load (node:internal/modules/cjs/loader:778:27)
6:17:03 PM: at Module.require (node:internal/modules/cjs/loader:1005:19)
6:17:03 PM: at require (node:internal/modules/cjs/helpers:102:18)
6:17:03 PM: at Object. (/opt/build/repo/node_modules/gatsby-cli/lib/reporter/redux/index.js:10:17)
6:17:03 PM: at Module._compile (node:internal/modules/cjs/loader:1101:14)
6:17:03 PM: at Object.Module._extensions…js (node:internal/modules/cjs/loader:1153:10)
6:17:03 PM: at Module.load (node:internal/modules/cjs/loader:981:32)
6:17:03 PM: at Function.Module._load (node:internal/modules/cjs/loader:822:12)
6:17:03 PM: at Module.require (node:internal/modules/cjs/loader:1005:19) {
6:17:03 PM: code: ‘MODULE_NOT_FOUND’,
6:17:03 PM: requireStack: [
6:17:03 PM: ‘/opt/build/repo/node_modules/gatsby-cli/lib/reporter/redux/index.js’,
6:17:03 PM: ‘/opt/build/repo/node_modules/gatsby-cli/lib/reporter/redux/actions.js’,
6:17:03 PM: ‘/opt/build/repo/node_modules/gatsby-cli/lib/reporter/reporter.js’,
6:17:03 PM: ‘/opt/build/repo/node_modules/gatsby/dist/redux/reducers/program.js’,
6:17:03 PM: ‘/opt/build/repo/node_modules/gatsby/dist/redux/reducers/index.js’,
6:17:03 PM: ‘/opt/build/repo/node_modules/gatsby/dist/redux/index.js’,
6:17:03 PM: ‘/opt/build/repo/node_modules/gatsby/dist/utils/jobs/worker-messaging.js’,
6:17:03 PM: ‘/opt/build/repo/node_modules/gatsby/dist/utils/worker/child/index.js’,
6:17:03 PM: ‘/opt/build/repo/node_modules/gatsby-worker/dist/child.js’
6:17:03 PM: ]
6:17:03 PM: }
6:17:03 PM: node:internal/modules/cjs/loader:936
6:17:03 PM: throw err;
6:17:03 PM: ^
6:17:03 PM: Error: Cannot find module ‘./reducers/page-tree’
6:17:03 PM: Require stack:
6:17:03 PM: - /opt/build/repo/node_modules/gatsby-cli/lib/reporter/redux/index.js
6:17:03 PM: - /opt/build/repo/node_modules/gatsby-cli/lib/reporter/redux/actions.js
6:17:03 PM: - /opt/build/repo/node_modules/gatsby-cli/lib/reporter/reporter.js
6:17:03 PM: - /opt/build/repo/node_modules/gatsby/dist/redux/reducers/program.js
6:17:03 PM: - /opt/build/repo/node_modules/gatsby/dist/redux/reducers/index.js
6:17:03 PM: - /opt/build/repo/node_modules/gatsby/dist/redux/index.js
6:17:03 PM: - /opt/build/repo/node_modules/gatsby/dist/utils/jobs/worker-messaging.js
6:17:03 PM: - /opt/build/repo/node_modules/gatsby/dist/utils/worker/child/index.js
6:17:03 PM: - /opt/build/repo/node_modules/gatsby-worker/dist/child.js
6:17:03 PM: at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
6:17:03 PM: at Function.Module._load (node:internal/modules/cjs/loader:778:27)
6:17:03 PM: at Module.require (node:internal/modules/cjs/loader:1005:19)
6:17:03 PM: at require (node:internal/modules/cjs/helpers:102:18)
6:17:03 PM: at Object. (/opt/build/repo/node_modules/gatsby-cli/lib/reporter/redux/index.js:10:17)
6:17:03 PM: at Module._compile (node:internal/modules/cjs/loader:1101:14)
6:17:03 PM: at Object.Module._extensions…js (node:internal/modules/cjs/loader:1153:10)
6:17:03 PM: at Module.load (node:internal/modules/cjs/loader:981:32)
6:17:03 PM: at Function.Module._load (node:internal/modules/cjs/loader:822:12)
6:17:03 PM: at Module.require (node:internal/modules/cjs/loader:1005:19) {
6:17:03 PM: code: ‘MODULE_NOT_FOUND’,
6:17:03 PM: requireStack: [
6:17:03 PM: ‘/opt/build/repo/node_modules/gatsby-cli/lib/reporter/redux/index.js’,
6:17:03 PM: ‘/opt/build/repo/node_modules/gatsby-cli/lib/reporter/redux/actions.js’,
6:17:03 PM: ‘/opt/build/repo/node_modules/gatsby-cli/lib/reporter/reporter.js’,
6:17:03 PM: ‘/opt/build/repo/node_modules/gatsby/dist/redux/reducers/program.js’,
6:17:03 PM: ‘/opt/build/repo/node_modules/gatsby/dist/redux/reducers/index.js’,
6:17:03 PM: ‘/opt/build/repo/node_modules/gatsby/dist/redux/index.js’,
6:17:03 PM: ‘/opt/build/repo/node_modules/gatsby/dist/utils/jobs/worker-messaging.js’,
6:17:03 PM: ‘/opt/build/repo/node_modules/gatsby/dist/utils/worker/child/index.js’,
6:17:03 PM: ‘/opt/build/repo/node_modules/gatsby-worker/dist/child.js’
6:17:03 PM: ]
6:17:03 PM: }
6:18:27 PM: Execution timed out after 18m22.021290212s
6:18:27 PM: Error running command: Command did not finish within the time limit
6:18:27 PM: Creating deploy upload records
6:18:27 PM: Failing build: Failed to build site
6:18:28 PM: Failed during stage ‘building site’: Command did not finish within the time limit
6:18:28 PM: Finished processing build request in 18m31.403907118s

3

The problem is here. :slightly_smiling_face:

If you could let us know the site name, we can increase the build time limit for it.

4

Hi Hrishkesh,

I re-installed my node_modules several times after making some more dep changes, and finally was able to achieve a successful build on GatsbyJS. It idd not start with simply too long a load time. I don’t know that Netlify works seamlessly with gatsby-plugin-image. And that is what is idfferent now about my site, and why i think, even after being successful with my deployment to my site, that 18+ minutes of build time (double what it used to be before my code refactor), that this time is optimal. It is very expensive, and will only get more expensive with each time i add incremental content to the site. In fact, I added very little (only one image) after this migration (which just happened days ago) to gatsby-plugin-image from gatsby-image. I don’ t think it is a Netlify issue per se. I think it is the way that Gatsby is configured and works. I have to think about what framework/library would be best for me to build in which the build time is not so expensive and also is scaleable. I don’t think Gatsby is so scaleable! I am thinking either Next.js or Eleventy. What has been Netlify’s experience with either of those when it comes to scalability and performance? this will be a major undertaking, so I am taking my time to find out what the best solution for me will be. Thanks in advance for any feedback you may have!

5

Hey there, @interglobalmedia :wave:

Thanks for taking the time to share that feedback with us. I am glad you were able to achieve a successful build!

We understand how many options there are when it comes to frameworks! As a company, we support thousands of developers who build with Next.js on Netlify, and have some great resources for testing it out. Have you used Next.js before? If you haven’t, a good resource for Next.js is our Next.js from the ground up mission on our Jamstack Explorers page.

Additionally, if you wanted to explore what working with these frameworks feels like for you, we have templates for both Eleventy and Next.js that you could sample with a practice site.

Lastly, our blog has some in depth tutorials for both Next.js and Eleventy..

If you have specific questions about scalability, please let me know. Otherwise, I am more than happy to share additional resources that will help you find the best fit!

6

Hi Hillary,

Thanks so much for your info. I will definitely check it all out. I’m playing around a bit with Eleventy right now, and will checkout your docs as well. Have never used Next.js before, but want to try it out as well. And then decide which way I want to go afterwards. Again thanks for your help!