Deploy TinaCMS on Nuxt 2 website failing

Hi,

Website: https://the10yearsplan.netlify.app/

Recently I migrated a Nuxt (v2) site from Forestry to TinaCMS. The migration worked and I can fire up the CMS when running the site on local dev. The deploys however fail with message:

Failed during stage ‘Install dependencies’: dependency_installation script returned non-zero exit code: 1

The full build log will be provided below.

In my package.json I have the following scripts section:

  "scripts": {
    "dev": "yarn tinacms dev -c \"nuxt\"",
    "build": "tinacms build && nuxt build",
    "start": "nuxt start",
    "generate": "tinacms build && nuxt generate",
    "lint:js": "eslint --ext \".js,.vue\" --ignore-path .gitignore .",
    "lint": "yarn lint:js"
  },

I hope anyone can guide me in the right direction. Thanks!

The full build log:

9:46:02 AM: build-image version: cd0a67ec27b8bcd87e2a257fe5ebcf1900a8021d (focal)
9:46:02 AM: buildbot version: f3871d4c438bbd4f48a8f44a50bec7489430735e
9:46:02 AM: Fetching cached dependencies
9:46:02 AM: Starting to download cache of 222.4MB
9:46:04 AM: Finished downloading cache in 2.078s
9:46:04 AM: Starting to extract cache
9:46:07 AM: Finished extracting cache in 2.845s
9:46:07 AM: Finished fetching cache in 5.013s
9:46:07 AM: Starting to prepare the repo for build
9:46:07 AM: Preparing Git Reference refs/heads/main
9:46:08 AM: Parsing package.json dependencies
9:46:10 AM: Starting to install dependencies
9:46:10 AM: Python version set to 3.8
9:46:10 AM: Attempting Ruby version 2.7.2, read from environment
9:46:11 AM: Using Ruby version 2.7.2
9:46:12 AM: Started restoring cached go cache
9:46:12 AM: Finished restoring cached go cache
9:46:12 AM: Installing Go version 1.19.5 (requested 1.19.5)
9:46:17 AM: go version go1.19.5 linux/amd64
9:46:18 AM: Using PHP version 8.0
9:46:19 AM: Started restoring cached Node.js version
9:46:20 AM: Finished restoring cached Node.js version
9:46:21 AM: v12.18.0 is already installed.
9:46:21 AM: Now using node v12.18.0 (npm v6.14.4)
9:46:21 AM: Started restoring cached build plugins
9:46:21 AM: Finished restoring cached build plugins
9:46:21 AM: Started restoring cached corepack dependencies
9:46:21 AM: Finished restoring cached corepack dependencies
9:46:21 AM: Started restoring cached yarn cache
9:46:23 AM: Finished restoring cached yarn cache
9:46:24 AM: No yarn workspaces detected
9:46:24 AM: Started restoring cached node modules
9:46:24 AM: Finished restoring cached node modules
9:46:24 AM: Installing npm packages using Yarn version 1.22.10
9:46:24 AM: yarn install v1.22.10
9:46:24 AM: [1/4] Resolving packages...
9:46:25 AM: [2/4] Fetching packages...
9:46:45 AM: info fsevents@2.3.2: The platform "linux" is incompatible with this module.
9:46:45 AM: info "fsevents@2.3.2" is an optional dependency and failed compatibility check. Excluding it from installation.
9:46:45 AM: error @rollup/pluginutils@5.0.2: The engine "node" is incompatible with this module. Expected version ">=14.0.0". Got "12.18.0"
9:46:45 AM: error Found incompatible module.
9:46:45 AM: info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
9:46:45 AM: Failed during stage 'Install dependencies': dependency_installation script returned non-zero exit code: 1
9:46:45 AM: Error during Yarn install
9:46:45 AM: Build was terminated: dependency_installation script returned non-zero exit code: 1
9:46:45 AM: Failing build: Failed to install dependencies
9:46:45 AM: Finished processing build request in 43.717s

Kind regards,
Marco

Try removing package-lock.json from your repo.

Thanks! This solved one problem: the deploy has completed. Unfortunately TinaCMS is not showing, get an empty page instead on TinaCMS.

Hi @corneelonline - We do not have any direct knowledge of tinacms - however, looking at your deploy log for your latest deploy, it appears that you might need to update your node.js in order for tinacms to work properly.

Beyond this, it just looks like some connection are being refused. Hope this helps!

Thanks Kai, all is working fine now. It seems that Tina is only working for public repos and mine was private.

Thanks for coming back and sharing that tidbit with the community! This was super helpful. :netliheart: