Home
Support Forums

Netlify deploys the editor but not the preview

Please help!

I’m stuck in the deployment of the “sanity-kitchen-sink” editor-preview example, that is outside its “local” development environment. Netlify successfully deployed the editor to

http://sanity-kitchen-sink-studio-4s8bs6r8.netlify.app

but the preview to http://sanity-kitchen-sink-web-x6tpo9s1.netlify.app

failed. The deployment log shows no error, and ends with

"GraphQL API deployed to

https://slm8njcb.api.sanity.io/v1/graphql/production/default

Build exceeded maximum allowed runtime"

Any pointers will be most welcome!

hey there, do you have a full build log you can paste here or link us to?

maximum allowed runtime indicates that your build process is needing more than the default-availble 15 minutes, but without seeing a full build log it is hard to say why.

Thank you for responding Perry! Here’s the log …
9:37:16 AM: Build ready to start
9:37:20 AM: build-image version: 8925038cf853b22d6397cdcb9904ac88b66bb383 (focal)
9:37:20 AM: build-image tag: v4.5.0
9:37:20 AM: buildbot version: 84197c5d0209353d9407aac932bd185d2d2eb582
9:37:21 AM: Building without cache
9:37:21 AM: Starting to prepare the repo for build
9:37:21 AM: No cached dependencies found. Cloning fresh repo
9:37:21 AM: git clone GitHub - Hennie53/sanity-kitchen-sink: Kitchen Sink
9:37:21 AM: Preparing Git Reference refs/heads/main
9:37:22 AM: Parsing package.json dependencies
9:37:22 AM: Different build dir detected, going to use the one specified in the Netlify configuration file: ‘’ versus ‘/’ in the Netlify UI
9:37:22 AM: Different publish path detected, going to use the one specified in the Netlify configuration file: ‘web/public’ versus ‘/web/public’ in the Netlify UI
9:37:22 AM: Starting build script
9:37:23 AM: Installing dependencies
9:37:23 AM: Python version set to 2.7
9:37:23 AM: v16.13.0 is already installed.
9:37:24 AM: Now using node v16.13.0 (npm v8.1.0)
9:37:24 AM: Started restoring cached build plugins
9:37:24 AM: Finished restoring cached build plugins
9:37:24 AM: Attempting ruby version 2.7.2, read from environment
9:37:25 AM: Using ruby version 2.7.2
9:37:26 AM: Using PHP version 8.0
9:37:26 AM: Started restoring cached node modules
9:37:26 AM: Finished restoring cached node modules
9:37:26 AM: Installing NPM modules using NPM version 8.1.0
9:37:27 AM: npm WARN old lockfile
9:37:27 AM: npm WARN old lockfile The package-lock.json file was created with an old version of npm,
9:37:27 AM: npm WARN old lockfile so supplemental metadata must be fetched from the registry.
9:37:27 AM: npm WARN old lockfile
9:37:27 AM: npm WARN old lockfile This is a one-time fix-up, please be patient…
9:37:27 AM: npm WARN old lockfile
9:37:38 AM: npm WARN deprecated urix@0.1.0: Please see GitHub - lydell/urix: [DEPRECATED] Makes Windows-style paths more unix and URI friendly.
9:37:38 AM: npm WARN deprecated har-validator@5.1.5: this library is no longer supported
9:37:38 AM: npm WARN deprecated resolve-url@0.2.1: GitHub - lydell/resolve-url: [DEPRECATED] Like Node.js’ `path.resolve`/`url.resolve` for the browser.
9:37:39 AM: npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See There’s Math.random(), and then there’s Math.random() · V8 for details.
9:37:40 AM: npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
9:37:41 AM: npm WARN deprecated mkdirp-promise@5.0.1: This package is broken and no longer maintained. ‘mkdirp’ itself supports promises now, please switch to that.
9:37:47 AM: > sanity-kitchen-sink@1.0.4 postinstall
9:37:47 AM: > lerna bootstrap
9:37:47 AM: lerna notice cli v3.22.1
9:37:47 AM: lerna info ci enabled
9:37:48 AM: lerna info Bootstrapping 2 packages
9:37:48 AM: lerna info Installing external dependencies
9:39:58 AM: lerna info Symlinking packages and binaries
9:39:58 AM: lerna success Bootstrapped 2 packages
9:39:58 AM: added 763 packages, and audited 764 packages in 3m
9:39:58 AM: 29 packages are looking for funding
9:39:58 AM: run npm fund for details
9:39:58 AM: 55 vulnerabilities (27 moderate, 27 high, 1 critical)
9:39:58 AM: To address issues that do not require attention, run:
9:39:58 AM: npm audit fix
9:39:58 AM: To address all issues (including breaking changes), run:
9:39:58 AM: npm audit fix --force
9:39:58 AM: Run npm audit for details.
9:39:58 AM: NPM modules installed
9:39:58 AM: Started restoring cached go cache
9:39:58 AM: Finished restoring cached go cache
9:39:59 AM: go version go1.16.5 linux/amd64
9:39:59 AM: go version go1.16.5 linux/amd64
9:39:59 AM: Installing missing commands
9:39:59 AM: Verify run directory
9:40:00 AM: ​
9:40:00 AM: ────────────────────────────────────────────────────────────────
9:40:00 AM: Netlify Build
9:40:00 AM: ────────────────────────────────────────────────────────────────
9:40:00 AM: ​
9:40:00 AM: ❯ Version
9:40:00 AM: @netlify/build 18.25.1
9:40:00 AM: ​
9:40:00 AM: ❯ Flags
9:40:00 AM: baseRelDir: true
9:40:00 AM: buildId: 619b48acc6e9b4b2c7bbd517
9:40:00 AM: deployId: 619b48acc6e9b4b2c7bbd519
9:40:00 AM: ​
9:40:00 AM: ❯ Current directory
9:40:00 AM: /opt/build/repo
9:40:00 AM: ​
9:40:00 AM: ❯ Config file
9:40:00 AM: No config file was defined: using default values.
9:40:00 AM: ​
9:40:00 AM: ❯ Context
9:40:00 AM: production
9:40:00 AM: ​
9:40:00 AM: ────────────────────────────────────────────────────────────────
9:40:00 AM: 1. Build command from Netlify app
9:40:00 AM: ────────────────────────────────────────────────────────────────
9:40:00 AM: ​
9:40:00 AM: $ npm run build-web
9:40:00 AM: > sanity-kitchen-sink@1.0.4 build-web
9:40:00 AM: > lerna bootstrap && (cd studio && SANITY_AUTH_TOKEN=$SANITY_DEPLOY_STUDIO_TOKEN npm run graphql-deploy) && (cd web && npm run build)
9:40:01 AM: lerna notice cli v3.22.1
9:40:01 AM: lerna info ci enabled
9:40:01 AM: lerna info Bootstrapping 2 packages
9:40:02 AM: lerna info Symlinking packages and binaries
9:40:02 AM: lerna success Bootstrapped 2 packages
9:40:02 AM: > sanity-kitchen-sink-studio@1.0.7 graphql-deploy
9:40:02 AM: > sanity graphql deploy --playground
9:40:03 AM: Dataset: production
9:40:03 AM: Tag: default
9:40:09 AM: This browser doesn’t support requestAnimationFrame. Make sure that you load a polyfill in older browsers. https://reactjs.org/link/react-polyfillsThis browser doesn’t support cancelAnimationFrame. Make sure that you load a polyfill in older browsers. https://reactjs.org/link/react-polyfillspart:@sanity/components/buttons/button-collection is deprecated. Use part:@sanity/components/buttons/button-grid
9:40:12 AM: GraphQL API deployed to:
9:40:12 AM: https://slm8njcb.api.sanity.io/v1/graphql/production/default
10:07:41 AM: Build exceeded maximum allowed runtime

Looks like at this point the build just stops and does nothing. We can increate the build time, but I don’t think that’s the problem here. The question you might need to find an answer for is, why’s the build stopping at this point? Are you expecting to see something after those lines?

1 Like

Thank you Hrish!
I’ll delve deeper, my understanding of this jig-saw is still VERY limited! I see a file resolvePreviewUrl.js under studio, where there is a “localhost” or “remote” option …
The fun continues …
HR

Hey there @Hennie53 :wave:

We hear you on the fun part-- enjoy delving deeper :slight_smile: I recommend checking out some of our Support Guides as well. A good place to start would be: [Support Guide] Frequently encountered problems during builds

If you end up wanting additional Netlify Support here, please let us know the following:

  1. The latest summary of the issue you are encountering / what you are hoping to resolve
  2. What additional debugging steps you have taken.

Thank you for answering and with the pointer Hillary! I’ll keep on drilling …
(Looks like the preview code queries the “production” dataset via GraphQL in order to build the preview, so I need to get a better understanding of how this works … The instructions from Sanity for a remote build also gives Gatsby instructions - how this fits in with Netlify is still a mistery too …)
Regards,
HR