Gatsby: Error: Cannot create as TypeComposer the following value: Date.
_Note: This is partially a continuation of issue https://github.com/gatsbyjs/gatsby/issues/13278, which was closed (seemingly prematurely?) by the gatsbot._
Description
After updating my site's node modules to their wanted versions, I can no longer successfully build the dev version of a current project.
As far as I can tell based on my actions and on the issue cited above, this is an issue relating to clashing version requirements of graphql.
Here is the error message I am getting:
โ building schema
error UNHANDLED REJECTION
Error: Cannot create as TypeComposer the following value: Date.
However, I'm really uncertain of how to resolve the issue and get my site building again. The typical escape hatch of rm -rf node_modules and reinstalling didn't do it. :)
Thanks so much to anyone who is able to give me some insight on this! I'll update this thread if I discover a way forward.
Here's the full
gatsby develop result and error (Click to expand)
~/code/typemedia18 master โ 16m โ โ โ
โถ gatsby develop
success open and validate gatsby-configs - 0.014 s
success load plugins - 0.397 s
success onPreInit - 0.009 s
success initialize cache - 0.020 s
success copy gatsby files - 0.030 s
success onPreBootstrap - 0.007 s
success source and transform nodes - 5.705 s
โ building schema
error UNHANDLED REJECTION
Error: Cannot create as TypeComposer the following value: Date.
- SchemaComposer.js:365 SchemaComposer.createTempTC
[typemedia18]/[graphql-compose]/lib/SchemaComposer.js:365:11
- SchemaComposer.js:563 SchemaComposer.addAsComposer
[typemedia18]/[graphql-compose]/lib/SchemaComposer.js:563:27
- schema-composer.js:21 createSchemaComposer
[typemedia18]/[gatsby]/dist/schema/schema-composer.js:21:18
- index.js:44 Object.<anonymous>
[typemedia18]/[gatsby]/dist/schema/index.js:44:28
- Generator.next
- new Promise
- index.js:67 Object.build
[typemedia18]/[gatsby]/dist/schema/index.js:67:17
- index.js:340
[typemedia18]/[gatsby]/dist/bootstrap/index.js:340:32
- Generator.next
Steps to reproduce
I wish I could provide a demo site, but this is happening on a project that is currently under wraps and relatively complex (so it seems hard to recreate in a simplified version). I could provide my package.json or similar, if useful.
Here were the steps that led to this issue:
I was having trouble making image updates in a markdown document update (a separate issue), and didn't want to
gatsby clean, then wait for 15 minutes to regen all my site's thumbnails. I thought there must be a better way.I checked
npm outdatedto see what dependencies might be outdated. Sure enough, I'm several versions behind on several packages.
npm update summary (Click to expand)
โถ npm outdated
Package Current Wanted Latest Location
@babel/core 7.4.4 7.4.5 7.4.5 typemedia-2018
@mdx-js/mdx 1.0.16 1.0.20 1.0.20 typemedia-2018
@mdx-js/react 1.0.16 1.0.20 1.0.20 typemedia-2018
gatsby 2.4.2 2.7.5 2.7.5 typemedia-2018
gatsby-image 2.0.41 2.1.2 2.1.2 typemedia-2018
gatsby-plugin-netlify-cache 1.1.0 1.2.0 1.2.0 typemedia-2018
gatsby-plugin-offline 2.1.0 2.1.1 2.1.1 typemedia-2018
gatsby-plugin-sharp 2.0.36 2.1.2 2.1.2 typemedia-2018
gatsby-plugin-transition-link 1.12.3 1.12.4 1.12.4 typemedia-2018
gatsby-remark-copy-linked-files 2.0.12 2.0.13 2.0.13 typemedia-2018
gatsby-remark-images 3.0.11 3.0.14 3.0.14 typemedia-2018
gatsby-source-filesystem 2.0.33 2.0.37 2.0.37 typemedia-2018
gatsby-transformer-sharp 2.1.19 2.1.20 2.1.20 typemedia-2018
gsap 2.1.2 2.1.3 2.1.3 typemedia-2018
polished 3.3.0 3.4.0 3.4.0 typemedia-2018
prettier 1.17.0 1.17.1 1.17.1 typemedia-2018
typescript 3.4.5 3.5.1 3.5.1 typemedia-2018
webpack 4.30.0 4.32.2 4.32.2 typemedia-2018
- So, I used
npm updateto update my dependencies. This included quite a few items seeking "a peer dependency of"graphql@^0.11.0 || ^0.12.0 || ^0.13.0.
npm update (Click to expand)
~/code/typemedia18 master โ 2m โ โ
โถ npm update
npm WARN deprecated [email protected]: This module has moved and is now available at @hapi/joi. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated [email protected]: core-js@<2.6.5 is no longer maintained. Please, upgrade to core-js@3 or at least to actual version of core-js@2.
npm WARN deprecated [email protected]: This module has moved and is now available at @hapi/topo. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated [email protected]: This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
> [email protected] postinstall /Users/stephennixon/code/typemedia18/node_modules/cwebp-bin
> node lib/install.js
โ cwebp pre-build test passed successfully
> [email protected] postinstall /Users/stephennixon/code/typemedia18/node_modules/gatsby-telemetry
> node src/postinstall.js
npm WARN [email protected] requires a peer of graphql@^0.6.0 || ^0.7.0 || ^0.8.0-b || ^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
+ [email protected]
+ @mdx-js/[email protected]
+ @babel/[email protected]
+ [email protected]
+ [email protected]
+ [email protected]
+ @mdx-js/[email protected]
+ [email protected]
+ [email protected]
+ [email protected]
+ [email protected]
+ [email protected]
+ [email protected]
+ [email protected]
+ [email protected]
+ [email protected]
+ [email protected]
+ [email protected]
added 89 packages from 841 contributors, removed 10 packages, updated 86 packages, moved 2 packages and audited 35203 packages in 32.11s
found 0 vulnerabilities
- So, I ran
npm install graphql@^0.13.0. Now, I got a request forgraphql@^14.1.0and another forgraphql@^14.1.0.
Summary (Click to expand)
โถ npm install graphql@^0.13.0
npm WARN @gatsbyjs/[email protected] requires a peer of graphql@^14.1.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^14.1.1 but none is installed. You must install peer dependencies yourself.
+ [email protected]
added 1 package, updated 1 package and audited 35205 packages in 8.544s
found 0 vulnerabilities
- I figured that
npm install graphql@^14.1.1should install a version that also supported the very old versions asked for as "peer dependencies," so I ran that. It installed[email protected].
Summary (Click to expand)
~/code/typemedia18 master โ 11m โ โ โ
โถ npm install graphql@^14.1.1
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.6.0 || ^0.7.0 || ^0.8.0-b || ^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
+ [email protected]
updated 1 package and audited 35205 packages in 9.649s
found 0 vulnerabilities
And, I'm now left with my current problem, error UNHANDLED REJECTION. In case it's useful beyond my summary above, here is the whole terminal log of this whole flow, which includes a couple of repeated steps out of npm confusion:
Long terminal flow (Click to expand)
~/code/typemedia18 master โ 0m
โถ gd
success open and validate gatsby-configs โ 0.006 s
success load plugins โ 0.453 s
success onPreInit โ 0.009 s
success initialize cache โ 0.005 s
success copy gatsby files โ 0.053 s
success onPreBootstrap โ 0.005 s
success source and transform nodes โ 1.233 s
success building schema โ 0.202 s
success createPages โ 0.033 s
success createPagesStatefully โ 0.029 s
success onPreExtractQueries โ 0.002 s
success update schema โ 0.028 s
success extract queries from components โ 0.162 s
success run static queries โ 2.841 s โ 7/7 2.46 queries/second
success run page queries โ 0.006 s โ 5/5 881.00 queries/second
success write out page data โ 0.003 s
success write out redirect data โ 0.000 s
success Build manifest and related icons โ 0.066 s
success onPostBootstrap โ 0.067 s
info bootstrap finished - 6.810 s
DONE Compiled successfully in 2257ms 6:16:49 PM
You can now view typemedia-2018 in the browser.
http://localhost:8000/
View GraphiQL, an in-browser IDE, to explore your site's data and schema
http://localhost:8000/___graphql
Note that the development build is not optimized.
To create a production build, use npm run build
info โน ๏ฝขwdm๏ฝฃ:
info โน ๏ฝขwdm๏ฝฃ: Compiled successfully.
~/code/typemedia18 master โ 0m โ
โถ npm outdated
Package Current Wanted Latest Location
@babel/core 7.4.4 7.4.5 7.4.5 typemedia-2018
@mdx-js/mdx 1.0.16 1.0.20 1.0.20 typemedia-2018
@mdx-js/react 1.0.16 1.0.20 1.0.20 typemedia-2018
gatsby 2.4.2 2.7.5 2.7.5 typemedia-2018
gatsby-image 2.0.41 2.1.2 2.1.2 typemedia-2018
gatsby-plugin-netlify-cache 1.1.0 1.2.0 1.2.0 typemedia-2018
gatsby-plugin-offline 2.1.0 2.1.1 2.1.1 typemedia-2018
gatsby-plugin-sharp 2.0.36 2.1.2 2.1.2 typemedia-2018
gatsby-plugin-transition-link 1.12.3 1.12.4 1.12.4 typemedia-2018
gatsby-remark-copy-linked-files 2.0.12 2.0.13 2.0.13 typemedia-2018
gatsby-remark-images 3.0.11 3.0.14 3.0.14 typemedia-2018
gatsby-source-filesystem 2.0.33 2.0.37 2.0.37 typemedia-2018
gatsby-transformer-sharp 2.1.19 2.1.20 2.1.20 typemedia-2018
gsap 2.1.2 2.1.3 2.1.3 typemedia-2018
polished 3.3.0 3.4.0 3.4.0 typemedia-2018
prettier 1.17.0 1.17.1 1.17.1 typemedia-2018
typescript 3.4.5 3.5.1 3.5.1 typemedia-2018
webpack 4.30.0 4.32.2 4.32.2 typemedia-2018
~/code/typemedia18 master โ 0m โ โ
โถ npm install
audited 34874 packages in 6.957s
found 0 vulnerabilities
~/code/typemedia18 master โ 1m โ
โถ npm outdated
Package Current Wanted Latest Location
@babel/core 7.4.4 7.4.5 7.4.5 typemedia-2018
@mdx-js/mdx 1.0.16 1.0.20 1.0.20 typemedia-2018
@mdx-js/react 1.0.16 1.0.20 1.0.20 typemedia-2018
gatsby 2.4.2 2.7.5 2.7.5 typemedia-2018
gatsby-image 2.0.41 2.1.2 2.1.2 typemedia-2018
gatsby-plugin-netlify-cache 1.1.0 1.2.0 1.2.0 typemedia-2018
gatsby-plugin-offline 2.1.0 2.1.1 2.1.1 typemedia-2018
gatsby-plugin-sharp 2.0.36 2.1.2 2.1.2 typemedia-2018
gatsby-plugin-transition-link 1.12.3 1.12.4 1.12.4 typemedia-2018
gatsby-remark-copy-linked-files 2.0.12 2.0.13 2.0.13 typemedia-2018
gatsby-remark-images 3.0.11 3.0.14 3.0.14 typemedia-2018
gatsby-source-filesystem 2.0.33 2.0.37 2.0.37 typemedia-2018
gatsby-transformer-sharp 2.1.19 2.1.20 2.1.20 typemedia-2018
gsap 2.1.2 2.1.3 2.1.3 typemedia-2018
polished 3.3.0 3.4.0 3.4.0 typemedia-2018
prettier 1.17.0 1.17.1 1.17.1 typemedia-2018
typescript 3.4.5 3.5.1 3.5.1 typemedia-2018
webpack 4.30.0 4.32.2 4.32.2 typemedia-2018
~/code/typemedia18 master โ 2m โ โ
โถ npm update
npm WARN deprecated [email protected]: This module has moved and is now available at @hapi/joi. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated [email protected]: core-js@<2.6.5 is no longer maintained. Please, upgrade to core-js@3 or at least to actual version of core-js@2.
npm WARN deprecated [email protected]: This module has moved and is now available at @hapi/topo. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated [email protected]: This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
> [email protected] postinstall /Users/stephennixon/code/typemedia18/node_modules/cwebp-bin
> node lib/install.js
โ cwebp pre-build test passed successfully
> [email protected] postinstall /Users/stephennixon/code/typemedia18/node_modules/gatsby-telemetry
> node src/postinstall.js
npm WARN [email protected] requires a peer of graphql@^0.6.0 || ^0.7.0 || ^0.8.0-b || ^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
+ [email protected]
+ @mdx-js/[email protected]
+ @babel/[email protected]
+ [email protected]
+ [email protected]
+ [email protected]
+ @mdx-js/[email protected]
+ [email protected]
+ [email protected]
+ [email protected]
+ [email protected]
+ [email protected]
+ [email protected]
+ [email protected]
+ [email protected]
+ [email protected]
+ [email protected]
+ [email protected]
added 89 packages from 841 contributors, removed 10 packages, updated 86 packages, moved 2 packages and audited 35203 packages in 32.11s
found 0 vulnerabilities
~/code/typemedia18 master โ 4m โ
โถ npm update dev
~/code/typemedia18 master โ 5m โ
โถ npm update --dev
~/code/typemedia18 master โ 5m โ
โถ npm update --dev
~/code/typemedia18 master โ 5m โ
โถ npm -v
6.9.0
~/code/typemedia18 master โ 6m โ
โถ npm install graphql
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.6.0 || ^0.7.0 || ^0.8.0-b || ^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
+ [email protected]
updated 1 package and audited 35205 packages in 7.537s
found 0 vulnerabilities
~/code/typemedia18 master โ 7m โ
โถ npm install graphql@^0.13.0
npm WARN @gatsbyjs/[email protected] requires a peer of graphql@^14.1.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^14.1.1 but none is installed. You must install peer dependencies yourself.
+ [email protected]
added 1 package, updated 1 package and audited 35205 packages in 8.544s
found 0 vulnerabilities
~/code/typemedia18 master โ 7m โ
โถ gd
success open and validate gatsby-configs - 0.018 s
success load plugins - 0.423 s
success onPreInit - 0.009 s
info One or more of your plugins have changed since the last time you ran Gatsby. As
a precaution, we're deleting your site's cache to ensure there's not any stale
data
success initialize cache - 0.069 s
success copy gatsby files - 0.030 s
success onPreBootstrap - 0.005 s
success source and transform nodes - 5.738 s
โ building schema
error UNHANDLED REJECTION
Error: Cannot create as TypeComposer the following value: Date.
- SchemaComposer.js:365 SchemaComposer.createTempTC
[typemedia18]/[graphql-compose]/lib/SchemaComposer.js:365:11
- SchemaComposer.js:563 SchemaComposer.addAsComposer
[typemedia18]/[graphql-compose]/lib/SchemaComposer.js:563:27
- schema-composer.js:21 createSchemaComposer
[typemedia18]/[gatsby]/dist/schema/schema-composer.js:21:18
- index.js:44 Object.<anonymous>
[typemedia18]/[gatsby]/dist/schema/index.js:44:28
- Generator.next
- new Promise
- index.js:67 Object.build
[typemedia18]/[gatsby]/dist/schema/index.js:67:17
- index.js:340
[typemedia18]/[gatsby]/dist/bootstrap/index.js:340:32
- Generator.next
~/code/typemedia18 master โ 9m โ โ โ
โถ rm -rf node_modules
~/code/typemedia18 master โ 10m โ โ
โถ rm -rf .cache
~/code/typemedia18 master โ 10m โ โ
โถ npm install
> [email protected] install /Users/stephennixon/code/typemedia18/node_modules/fsevents
> node install
node-pre-gyp WARN Using request for node-pre-gyp https download
[fsevents] Success: "/Users/stephennixon/code/typemedia18/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node" is installed via remote
> [email protected] install /Users/stephennixon/code/typemedia18/node_modules/sharp
> (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)
info sharp Using cached /Users/stephennixon/.npm/_libvips/libvips-8.7.4-darwin-x64.tar.gz
> [email protected] install /Users/stephennixon/code/typemedia18/node_modules/node-sass
> node scripts/install.js
Cached binary found at /Users/stephennixon/.npm/node-sass/4.12.0/darwin-x64-64_binding.node
> [email protected] postinstall /Users/stephennixon/code/typemedia18/node_modules/pose-core
> node ./scripts/postinstall.js || exit 0
+-------------------------------------------------+
| |
| Hey! Using Pose commercially? |
| |
| Pose is completely open source. |
| Its continued development relies on |
| contributions and sponsorship. |
| |
| Join us: patreon.com/popmotion |
| |
+-------------------------------------------------+
> [email protected] postinstall /Users/stephennixon/code/typemedia18/node_modules/gatsby-telemetry
> node src/postinstall.js
> [email protected] postinstall /Users/stephennixon/code/typemedia18/node_modules/cwebp-bin
> node lib/install.js
โ cwebp pre-build test passed successfully
> [email protected] postinstall /Users/stephennixon/code/typemedia18/node_modules/mozjpeg
> node lib/install.js
โ mozjpeg pre-build test passed successfully
> [email protected] postinstall /Users/stephennixon/code/typemedia18/node_modules/pngquant-bin
> node lib/install.js
โ pngquant pre-build test passed successfully
> [email protected] postinstall /Users/stephennixon/code/typemedia18/node_modules/node-sass
> node scripts/build.js
Binary found at /Users/stephennixon/code/typemedia18/node_modules/node-sass/vendor/darwin-x64-64/binding.node
Testing binary
Binary is fine
> [email protected] postinstall /Users/stephennixon/code/typemedia18/node_modules/styled-components
> node ./scripts/postinstall.js || exit 0
(node:17591) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGINT listeners added. Use emitter.setMaxListeners() to increase limit
Use styled-components at work? Consider supporting our development efforts at https://opencollective.com/styled-components
added 2155 packages from 1899 contributors and audited 35205 packages in 25.444s
found 0 vulnerabilities
~/code/typemedia18 master โ 11m โ โ
โถ gd
success open and validate gatsby-configs - 0.018 s
success load plugins - 0.511 s
success onPreInit - 0.015 s
success initialize cache - 0.010 s
success copy gatsby files - 0.054 s
success onPreBootstrap - 0.007 s
success source and transform nodes - 6.796 s
โ building schema
error UNHANDLED REJECTION
Error: Cannot create as TypeComposer the following value: Date.
- SchemaComposer.js:365 SchemaComposer.createTempTC
[typemedia18]/[graphql-compose]/lib/SchemaComposer.js:365:11
- SchemaComposer.js:563 SchemaComposer.addAsComposer
[typemedia18]/[graphql-compose]/lib/SchemaComposer.js:563:27
- schema-composer.js:21 createSchemaComposer
[typemedia18]/[gatsby]/dist/schema/schema-composer.js:21:18
- index.js:44 Object.<anonymous>
[typemedia18]/[gatsby]/dist/schema/index.js:44:28
- Generator.next
- new Promise
- index.js:67 Object.build
[typemedia18]/[gatsby]/dist/schema/index.js:67:17
- index.js:340
[typemedia18]/[gatsby]/dist/bootstrap/index.js:340:32
- Generator.next
~/code/typemedia18 master โ 11m โ โ โ
โถ npm install graphql@^14.1.1
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.6.0 || ^0.7.0 || ^0.8.0-b || ^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
+ [email protected]
updated 1 package and audited 35205 packages in 9.649s
found 0 vulnerabilities
~/code/typemedia18 master โ 12m โ โ
โถ gd
success open and validate gatsby-configs - 0.020 s
success load plugins - 0.496 s
success onPreInit - 0.010 s
success initialize cache - 0.033 s
success copy gatsby files - 0.049 s
success onPreBootstrap - 0.007 s
success source and transform nodes - 6.551 s
โ building schema
error UNHANDLED REJECTION
Error: Cannot create as TypeComposer the following value: Date.
- SchemaComposer.js:365 SchemaComposer.createTempTC
[typemedia18]/[graphql-compose]/lib/SchemaComposer.js:365:11
- SchemaComposer.js:563 SchemaComposer.addAsComposer
[typemedia18]/[graphql-compose]/lib/SchemaComposer.js:563:27
- schema-composer.js:21 createSchemaComposer
[typemedia18]/[gatsby]/dist/schema/schema-composer.js:21:18
- index.js:44 Object.<anonymous>
[typemedia18]/[gatsby]/dist/schema/index.js:44:28
- Generator.next
- new Promise
- index.js:67 Object.build
[typemedia18]/[gatsby]/dist/schema/index.js:67:17
- index.js:340
[typemedia18]/[gatsby]/dist/bootstrap/index.js:340:32
- Generator.next
~/code/typemedia18 master โ 16m โ โ โ
โถ gatsby develop
success open and validate gatsby-configs - 0.014 s
success load plugins - 0.397 s
success onPreInit - 0.009 s
success initialize cache - 0.020 s
success copy gatsby files - 0.030 s
success onPreBootstrap - 0.007 s
success source and transform nodes - 5.705 s
โ building schema
error UNHANDLED REJECTION
Error: Cannot create as TypeComposer the following value: Date.
- SchemaComposer.js:365 SchemaComposer.createTempTC
[typemedia18]/[graphql-compose]/lib/SchemaComposer.js:365:11
- SchemaComposer.js:563 SchemaComposer.addAsComposer
[typemedia18]/[graphql-compose]/lib/SchemaComposer.js:563:27
- schema-composer.js:21 createSchemaComposer
[typemedia18]/[gatsby]/dist/schema/schema-composer.js:21:18
- index.js:44 Object.<anonymous>
[typemedia18]/[gatsby]/dist/schema/index.js:44:28
- Generator.next
- new Promise
- index.js:67 Object.build
[typemedia18]/[gatsby]/dist/schema/index.js:67:17
- index.js:340
[typemedia18]/[gatsby]/dist/bootstrap/index.js:340:32
- Generator.next
Expected result
Ideally, my updated dependencies should work without issue, and the site should build as it did before, but maybe with a few improvements to performance, etc.
Actual result
Errors, probably related to graphql versions.
Environment
my gatsby info (Click to expand)
System:
OS: macOS 10.14.5
CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
Shell: 5.3 - /bin/zsh
Binaries:
Node: 10.15.3 - /usr/local/bin/node
Yarn: 1.15.2 - /usr/local/bin/yarn
npm: 6.9.0 - ~/.npm-global/bin/npm
Languages:
Python: 3.7.3 - /usr/local/opt/python/libexec/bin/python
Browsers:
Chrome: 74.0.3729.169
Firefox: 67.0
Safari: 12.1.1
npmPackages:
gatsby: ^2.7.5 => 2.7.5
gatsby-image: ^2.1.2 => 2.1.2
gatsby-mdx: ^0.6.2 => 0.6.3
gatsby-plugin-google-analytics: ^2.0.20 => 2.0.20
gatsby-plugin-layout: ^1.0.11 => 1.0.15
gatsby-plugin-manifest: ^2.0.9 => 2.1.1
gatsby-plugin-netlify-cache: ^1.2.0 => 1.2.0
gatsby-plugin-offline: ^2.1.1 => 2.1.1
gatsby-plugin-react-helmet: ^3.0.2 => 3.0.12
gatsby-plugin-sass: ^2.0.11 => 2.0.11
gatsby-plugin-sharp: ^2.1.2 => 2.1.2
gatsby-plugin-styled-components: ^3.0.4 => 3.0.7
gatsby-plugin-transition-link: ^1.12.4 => 1.12.4
gatsby-remark-copy-linked-files: ^2.0.13 => 2.0.13
gatsby-remark-images: ^3.0.14 => 3.0.14
gatsby-source-filesystem: ^2.0.37 => 2.0.37
gatsby-transformer-remark: ^2.2.0 => 2.3.12
gatsby-transformer-sharp: ^2.1.20 => 2.1.20
npmGlobalPackages:
gatsby-cli: 2.5.12
question or discussion
thundernixon
All 2 comments
The graphql module generally doesn't work well when there are multiple different versions installed.
Can you try removing your node_modules, deleting the package-lock.json file and re-running npm
install? Then try building your site again.
You should be able to see which versions of graphql are installed with npm list | grep " graphql@". Ideally (despite the peered warnings) you should just see [email protected].
If that doesn't work either. Can you try using yarn to install your dependencies? You can run yarn why graphql to see if there are multiple versions of the graphql module.
m-allanson
on 30 May 2019
❤5
🎉5
👍3
Hey @m-allanson, thanks so much for your help today on troubleshooting this!
The thing that solved it for me was deleting the package-lock.json (along with node_modules) and reinstalling with npm.
I think that is something I found at one point in the past, too, so I don't know why I forgot it yesterday. ๐ Well, hopefully this post helps someone else out, too!
thundernixon
on 30 May 2019
🎉6
👍2
Was this page helpful?
0 / 5 - 0 ratings
Related issues
kuworking
ยท
115Comments
blainekasten
ยท
130Comments
cutemachine
ยท
112Comments
jp887
ยท
98Comments
omrllm
ยท
83Comments
Most helpful comment
The graphql module generally doesn't work well when there are multiple different versions installed.
Can you try removing your
node_modules, deleting thepackage-lock.jsonfile and re-runningnpm install? Then try building your site again.You should be able to see which versions of
graphqlare installed withnpm list | grep " graphql@". Ideally (despite the peered warnings) you should just see[email protected].If that doesn't work either. Can you try using
yarnto install your dependencies? You can runyarn why graphqlto see if there are multiple versions of the graphql module.