TypeError: Cannot read property 'activities' of undefined

nerdy_horse · April 27, 2020, 8:59am

I need advice to debug deploy Netlify App

Build is failing which is strange as it works on my local and the only difference between the previous build and the new one is the one where I added few more md files. No configuraiton changes. Can someone please help with this?

Github link: GitHub - nerdyhorse/nerdy-horse-blog: An anonymous blog by nerdy horse
in case someone needs it to debug it.

nerdy_horse · April 27, 2020, 7:37pm

I even reverted back the code to the last successful deployment. It is breaking for them too.

perry · April 27, 2020, 10:29pm

hey there,

this seems to be a gatsby error:

github.com/gatsbyjs/gatsby

TypeError: Cannot read property 'activities' of undefined in yoga-layout-prebuilt

opened 06:28AM - 17 Apr 20 UTC

closed 08:21AM - 17 Apr 20 UTC

ochronus

type: bug

## Description gatsby build and gatsby develop both throw the error above. ### Steps to reproduce git checkout npm i ./node_modules/.bin/gatsby develop or ./node_modules/.bin/gatsby build https://github.com/ochronus/ochronus.online-gatsby ### Expected result Gatsby should build the site ### Actual result Gatsby threw an error ### Environment ``` System: OS: macOS 10.15.4 CPU: (4) x64 Intel(R) Core(TM) i7-7567U CPU @ 3.50GHz Shell: 3.1.0 - /usr/local/bin/fish Binaries: Node: 13.13.0 - /usr/local/bin/node Yarn: 1.22.4 - /usr/local/bin/yarn npm: 6.14.4 - /usr/local/bin/npm Languages: Python: 3.8.0 - /Users/ochronus/.pyenv/shims/python Browsers: Chrome: 81.0.4044.113 Firefox: 75.0 Safari: 13.1 npmPackages: gatsby: ^2.19.49 => 2.19.49 gatsby-cli: ^2.11.9 => 2.11.9 gatsby-image: ^2.3.3 => 2.3.3 gatsby-plugin-canonical-urls: ^2.2.2 => 2.2.2 gatsby-plugin-draft: 0.0.5 => 0.0.5 gatsby-plugin-feed: ^2.4.2 => 2.4.2 gatsby-plugin-google-analytics: ^2.1.38 => 2.1.38 gatsby-plugin-manifest: ^2.3.3 => 2.3.3 gatsby-plugin-netlify: ^2.2.2 => 2.2.2 gatsby-plugin-netlify-cache: ^1.2.0 => 1.2.0 gatsby-plugin-offline: ^3.1.2 => 3.1.2 gatsby-plugin-react-helmet: ^3.2.3 => 3.2.3 gatsby-plugin-s3: ^0.3.3 => 0.3.3 gatsby-plugin-sharp: ^2.5.3 => 2.5.3 gatsby-plugin-sitemap: ^2.3.3 => 2.3.3 gatsby-plugin-typography: ^2.4.2 => 2.4.2 gatsby-remark-copy-linked-files: ^2.2.1 => 2.2.1 gatsby-remark-images: ^3.2.1 => 3.2.1 gatsby-remark-prismjs: ^3.3.36 => 3.3.36 gatsby-remark-responsive-iframe: ^2.3.1 => 2.3.1 gatsby-remark-smartypants: ^2.2.2 => 2.2.2 gatsby-source-filesystem: ^2.2.2 => 2.2.2 gatsby-transformer-remark: ^2.7.1 => 2.7.1 gatsby-transformer-sharp: ^2.4.3 => 2.4.3 npmGlobalPackages: gatsby-cli: 2.11.9 ```

if you scroll down to the bottom, you can see some tips that might help:

"I was seeing the same issue in our ci after a package-lock file update, which worked fine locally. gatsby-cli is not in in package.json, but added to package-lock.json as dependency of gatsby.

Bumping gatsby version to 2.20.24 (and clean reinstall, reset of package-lock) solved it for me as well. I never saw this on my local environment though."

nerdy_horse · April 30, 2020, 2:25pm

Actually I fixed it.
The issue was gatsby-cli recently had a version bump, which was breaking the older gatsby versions. I bumped in my system and could reproduce the issue. All I had to do is bump up the gatsby libraries I was using and it fixed the issue.