gatsby-source-datocms
gatsby-source-datocms copied to clipboard
datocms
Build task is failing: "Encountered an error parsing the provided GraphQL type definitions"
One of our projects is no longer building. We receive the following error:
success open and validate gatsby-configs, load plugins - 3.911s
success onPreInit - 0.010s
success delete worker cache from previous builds - 0.010s
success initialize cache - 0.248s
success copy gatsby files - 0.350s
success Compiling Gatsby Functions - 0.541s
success onPreBootstrap - 0.569s
success loading DatoCMS schema - 1.277s
success createSchemaCustomization - 1.381s
success loading DatoCMS content - 2.350s
success Checking for changed pages - 0.005s
success source and transform nodes - 2.687s
info Writing GraphQL type definitions to C:/project/.cache/schema.gql
success building schema - 4.403s
success createPages - 0.002s
success createPagesStatefully - 0.200s
info Total nodes: 379, SitePage nodes: 3 (use --verbose for breakdown)
success Checking for changed pages - 0.002s
success onPreExtractQueries - 0.002s
success loading DatoCMS schema - 0.004s
success loading DatoCMS schema - 0.002s
success extract queries from components - 7.958s
ERROR
Encountered an error parsing the provided GraphQL type definitions:
Argument "from" of required type "String!" was not provided.
823 | mimeType: String
824 | colors: [DatoCmsColorField]
825 | blurhash: String
826 | originalId: String
827 | url(imgixParams: DatoCmsImgixParams): String
> 828 | createdAt: Date @dateformat @proxy(fromNode: false)
| ^
829 | video: DatoCmsAssetVideo
830 | fluid(maxWidth: Int = 800, maxHeight: Int, sizes: String, imgixParams: DatoCmsImgixParams, forceBlurhash: Boolean): DatoCmsFluid
831 | sizes(maxWidth: Int = 800, maxHeight: Int, sizes: String, imgixParams: DatoCmsImgixParams, forceBlurhash: Boolean): DatoCmsFluid
832 | fixed(width: Int = 400, height: Int, forceBlurhash: Boolean, imgixParams: DatoCmsImgixParams): DatoCmsFixed
833 | resolutions(width: Int = 400, height: Int, forceBlurhash: Boolean, imgixParams: DatoCmsImgixParams): DatoCmsFixed
success loading DatoCMS schema - 0.003s
ERROR
Encountered an error parsing the provided GraphQL type definitions:
Argument "from" of required type "String!" was not provided.
823 | mimeType: String
824 | colors: [DatoCmsColorField]
825 | blurhash: String
826 | originalId: String
827 | url(imgixParams: DatoCmsImgixParams): String
> 828 | createdAt: Date @dateformat @proxy(fromNode: false)
| ^
829 | video: DatoCmsAssetVideo
830 | fluid(maxWidth: Int = 800, maxHeight: Int, sizes: String, imgixParams: DatoCmsImgixParams, forceBlurhash: Boolean): DatoCmsFluid
831 | sizes(maxWidth: Int = 800, maxHeight: Int, sizes: String, imgixParams: DatoCmsImgixParams, forceBlurhash: Boolean): DatoCmsFluid
832 | fixed(width: Int = 400, height: Int, forceBlurhash: Boolean, imgixParams: DatoCmsImgixParams): DatoCmsFixed
833 | resolutions(width: Int = 400, height: Int, forceBlurhash: Boolean, imgixParams: DatoCmsImgixParams): DatoCmsFixed
ERROR
Encountered an error parsing the provided GraphQL type definitions:
Argument "from" of required type "String!" was not provided.
823 | mimeType: String
824 | colors: [DatoCmsColorField]
825 | blurhash: String
826 | originalId: String
827 | url(imgixParams: DatoCmsImgixParams): String
> 828 | createdAt: Date @dateformat @proxy(fromNode: false)
| ^
829 | video: DatoCmsAssetVideo
830 | fluid(maxWidth: Int = 800, maxHeight: Int, sizes: String, imgixParams: DatoCmsImgixParams, forceBlurhash: Boolean): DatoCmsFluid
831 | sizes(maxWidth: Int = 800, maxHeight: Int, sizes: String, imgixParams: DatoCmsImgixParams, forceBlurhash: Boolean): DatoCmsFluid
832 | fixed(width: Int = 400, height: Int, forceBlurhash: Boolean, imgixParams: DatoCmsImgixParams): DatoCmsFixed
833 | resolutions(width: Int = 400, height: Int, forceBlurhash: Boolean, imgixParams: DatoCmsImgixParams): DatoCmsFixed
ERROR
UNHANDLED REJECTION Worker exited before finishing task
Error: Worker exited before finishing task
This only happens when running the build task. npm run develop works just fine.
I tested on a vanilla install to ensure this was not related to the specific project. The same issue occurs. Here is the package.json file for the vanilla install:
{
"name": "vanilla",
"version": "1.0.0",
"private": true,
"description": "Vanilla",
"author": "Author",
"keywords": [
"gatsby"
],
"scripts": {
"develop": "gatsby develop",
"start": "gatsby develop",
"build": "gatsby build",
"serve": "gatsby serve",
"clean": "gatsby clean"
},
"dependencies": {
"gatsby": "^4.6.0",
"gatsby-plugin-google-analytics": "^4.6.0",
"gatsby-plugin-image": "^2.6.0",
"gatsby-plugin-manifest": "^4.6.0",
"gatsby-plugin-react-helmet": "^5.6.0",
"gatsby-plugin-sharp": "^4.6.0",
"gatsby-plugin-sitemap": "^5.6.0",
"gatsby-source-datocms": "^3.0.11",
"gatsby-source-filesystem": "^4.6.0",
"gatsby-transformer-remark": "^5.6.0",
"gatsby-transformer-sharp": "^4.6.0",
"react": "^17.0.1",
"react-dom": "^17.0.1",
"react-helmet": "^6.1.0"
}
}
I have also tried using 2 completeley different datocms instances from different client projects by switching out the apiToken in gatsby-config.js. The issue occurs, no matter what instance is used.
Dev Environment
- Windows 10
- node.js 14.18.1
Netlify is also failing to build.
We have exactly the same problems since this morning...
success open and validate gatsby-configs, load plugins - 2.342s
success onPreInit - 0.013s
success initialize cache - 0.156s
success copy gatsby files - 0.051s
success Compiling Gatsby Functions - 0.165s
success onPreBootstrap - 0.188s
success loading DatoCMS schema - 1.252s
success createSchemaCustomization - 1.386s
success loading DatoCMS content - 96.604s
success Checking for changed pages - 0.016s
success source and transform nodes - 101.651s
info Writing GraphQL type definitions to /Users/ben/Documents/Programmier Projekte/sevdesk-website-2020/.cache/schema.gql
warn There are conflicting field types in your data.
If you have explicitly defined a type for those fields, you can safely ignore this warning message.
Otherwise, Gatsby will omit those fields from the GraphQL schema.
If you know all field types in advance, the best strategy is to explicitly define them with the `createTypes` action, and skip inference with the `@dontInfer` directive.
See https://www.gatsbyjs.org/docs/actions/#createTypes
RecordsJson.logics.destination.componentId:
- type: number
value: 1
- type: string
value: 'integer'
success building schema - 3.866s
success createPages - 6.770s
success createPagesStatefully - 0.087s
info Total nodes: 258806, SitePage nodes: 1367 (use --verbose for breakdown)
success Checking for changed pages - 0.001s
success onPreExtractQueries - 0.001s
success extract queries from components - 6.327s
warn The GraphQL query in the non-page component "/Users/ben/Documents/Programmier Projekte/sevdesk-website-2020/src/templates/presseMitteilung.js" will not be run.
Exported queries are only executed for Page components. It's possible you're
trying to create pages in your gatsby-node.js and that's failing for some
reason.
If the failing component(s) is a regular component and not intended to be a page
component, you generally want to use a <StaticQuery> (https://gatsbyjs.org/docs/static-query)
instead of exporting a page query.
If you're more experienced with GraphQL, you can also export GraphQL
fragments from components and compose the fragments in the Page component
query and pass data down into the child component — https://graphql.org/learn/queries/#fragments
success write out redirect data - 0.027s
success Build manifest and related icons - 1.433s
success onPostBootstrap - 1.493s
info bootstrap finished - 126.823s
info changed file at /Users/ben/Documents/Programmier Projekte/sevdesk-website-2020/src/data/personalization/records.json
info changed file at /Users/ben/Documents/Programmier Projekte/sevdesk-website-2020/src/data/personalization/config.json
info changed file at /Users/ben/Documents/Programmier Projekte/sevdesk-website-2020/src/data/abtests.json
info changed file at /Users/ben/Documents/Programmier Projekte/sevdesk-website-2020/src/data/sales.json
success write out requires - 0.109s
success loading DatoCMS schema - 0.077s
success loading DatoCMS schema - 0.004s
success loading DatoCMS schema - 0.002s
success loading DatoCMS schema - 0.007s
success loading DatoCMS schema - 0.002s
ERROR
Encountered an error parsing the provided GraphQL type definitions:
Argument "from" of required type "String!" was not provided.
851 | mimeType: String
852 | colors: [DatoCmsColorField]
853 | blurhash: String
854 | originalId: String
855 | url(imgixParams: DatoCmsImgixParams): String
> 856 | createdAt: Date @dateformat @proxy(fromNode: false)
| ^
857 | video: DatoCmsAssetVideo
858 | fluid(maxWidth: Int = 800, maxHeight: Int, sizes: String, imgixParams: DatoCmsImgixParams, forceBlurhash: Boolean): DatoCmsFluid
859 | sizes(maxWidth: Int = 800, maxHeight: Int, sizes: String, imgixParams: DatoCmsImgixParams, forceBlurhash: Boolean): DatoCmsFluid
860 | fixed(width: Int = 400, height: Int, forceBlurhash: Boolean, imgixParams: DatoCmsImgixParams): DatoCmsFixed
861 | resolutions(width: Int = 400, height: Int, forceBlurhash: Boolean, imgixParams: DatoCmsImgixParams): DatoCmsFixed
success loading DatoCMS schema - 0.001s
success loading DatoCMS schema - 0.006s
success loading DatoCMS schema - 0.001s
ERROR
Encountered an error parsing the provided GraphQL type definitions:
Argument "from" of required type "String!" was not provided.
851 | mimeType: String
852 | colors: [DatoCmsColorField]
853 | blurhash: String
854 | originalId: String
855 | url(imgixParams: DatoCmsImgixParams): String
> 856 | createdAt: Date @dateformat @proxy(fromNode: false)
| ^
857 | video: DatoCmsAssetVideo
858 | fluid(maxWidth: Int = 800, maxHeight: Int, sizes: String, imgixParams: DatoCmsImgixParams, forceBlurhash: Boolean): DatoCmsFluid
859 | sizes(maxWidth: Int = 800, maxHeight: Int, sizes: String, imgixParams: DatoCmsImgixParams, forceBlurhash: Boolean): DatoCmsFluid
860 | fixed(width: Int = 400, height: Int, forceBlurhash: Boolean, imgixParams: DatoCmsImgixParams): DatoCmsFixed
861 | resolutions(width: Int = 400, height: Int, forceBlurhash: Boolean, imgixParams: DatoCmsImgixParams): DatoCmsFixed
success loading DatoCMS schema - 0.001s
ERROR
Encountered an error parsing the provided GraphQL type definitions:
Argument "from" of required type "String!" was not provided.
851 | mimeType: String
852 | colors: [DatoCmsColorField]
853 | blurhash: String
854 | originalId: String
855 | url(imgixParams: DatoCmsImgixParams): String
> 856 | createdAt: Date @dateformat @proxy(fromNode: false)
| ^
857 | video: DatoCmsAssetVideo
858 | fluid(maxWidth: Int = 800, maxHeight: Int, sizes: String, imgixParams: DatoCmsImgixParams, forceBlurhash: Boolean): DatoCmsFluid
859 | sizes(maxWidth: Int = 800, maxHeight: Int, sizes: String, imgixParams: DatoCmsImgixParams, forceBlurhash: Boolean): DatoCmsFluid
860 | fixed(width: Int = 400, height: Int, forceBlurhash: Boolean, imgixParams: DatoCmsImgixParams): DatoCmsFixed
861 | resolutions(width: Int = 400, height: Int, forceBlurhash: Boolean, imgixParams: DatoCmsImgixParams): DatoCmsFixed
ERROR
UNHANDLED REJECTION Worker exited before finishing task
Error: Worker exited before finishing task
- index.js:113 ChildProcess.<anonymous>
[sevdesk-website-2020]/[gatsby-worker]/dist/index.js:113:45
- node:events:390 ChildProcess.emit
node:events:390:28
- child_process:290 Process.ChildProcess._handle.onexit
node:internal/child_process:290:12
not finished Building production JavaScript and CSS bundles - 145.430s
Gatsby Cloud is also not building.
Dev Environment
- Apple macOS Monterey 12.1 (Apple M1 Pro)
- node.js 16.13.1
Hey @stefanoverna
Unfortunately it does not work with the v3.0.11. and v3.0.12 We tested it too at this morning.
What was the previous release that was working?
Hi, I am also working at sevdesk.
v3.0.11. was working fine but we got randomly the error with no changes at all in the project. It appeared "over night".
Hi @stefanoverna I am having this problem too. I am using v3.0.12.
I didn't upgrade any package, it just happen when rebuild my project using gatsby build with the working package.json a few days back. FYI I got no problem running gatsby develop.
I guess the problem is caused by the changes in the backend.
We're working with the Gatsby team on this, but I'll try to write something down here too.
A recent bug report we received was that the following sorting did not work correctly (results were randomly sorted, basically the sort part was completely ignored):
query MyQuery {
allDatoCmsPost(sort: {fields: [date], order: DESC}) {
edges { ... }
}
}
Now, in this query, date is a custom field of the Post model, and it's important to know that every node that we generate with this plugin has the following format:
{
id: 'DatoCmsPost-100945017-en',
parent: null,
children: [],
internal: { ... },
locale: 'en',
entityPayload: {
id: '100945017',
type: 'item',
attributes: [Object],
relationships: [Object],
meta: [Object]
},
seoMetaTags___NODE: 'DatoCmsSeoMetaTags-DatoCmsPost-100945017-en',
}
That is, we basically store the exact entity we get from our Content Management API inside a entityPayload property. The date field exposed in GraphQL is actually a "virtual" field, with a custom resolver that looks into entityPayload and returns the correct information. This allows to basically "lazy load" fields only when a query actually needs them, which is great.
Now. The way Gatsby works, is that if some of the "virtual" fields are required for filtering/sorting — like in the query above — it needs to "materialize" those fields, so that the filtering/sorting functions have all the information they need.
The result on the node is this:
{
id: 'DatoCmsPost-100945017-en',
parent: null,
children: [],
internal: { ... },
locale: 'en',
entityPayload: {
id: '100945017',
type: 'item',
attributes: [Object],
relationships: [Object],
meta: [Object]
},
seoMetaTags___NODE: 'DatoCmsSeoMetaTags-DatoCmsPost-100945017-en',
__gatsby_resolved: { date: '2020-03-06', meta: [Object] }
}
See the last __gatsby_resolved bit? That's the result of the materialization! The part of Gatsby code that finds the fields that need to be materialized for sorting is this one here — specifically the needsResolve bit. Basically, if the field has a resolver, it needs to be materialized, which makes sense.
Now the strage thing is that for fields that have the dateformat extension, needsResolve is only true if the same field is also a proxy.
We tried to add the proxy extension to dates https://github.com/datocms/gatsby-source-datocms/commit/839e6ee819a049db97e53c90349ed1ae3cb46157, and BOOM, problem solved!
At least in our tests.
But now we're getting these reports from you guys. Gatsby people is telling us that the proxy extension needs a from argument (which is the error you're getting)... but we don't really need that proxy thing in the first place, we already have a custom resolver! What's the underlying reason of this check? 😢
We're trying to figure out with them if there is some kind of bug/edge-case in Gatsby, or we're doing something wrong on our side.
In the meantime, I can assure you we didn't change anything on the response formats of our API, so it seems VERY strange that this error came up without upgrading some versions in your yarn.lock file.
I'll keep you posted!
Thanks for the update! We will also continue to look for a solution until then. :)
Oh, yeah! The version worked! Thanks :)
success open and validate gatsby-configs, load plugins - 2.475s
success onPreInit - 0.012s
success initialize cache - 0.195s
success copy gatsby files - 0.059s
success Compiling Gatsby Functions - 0.191s
success onPreBootstrap - 0.218s
success loading DatoCMS schema - 1.240s
success createSchemaCustomization - 1.363s
success loading DatoCMS content - 108.496s
success Checking for changed pages - 0.016s
success source and transform nodes - 113.168s
info Writing GraphQL type definitions to /Users/ben/Documents/Programmier Projekte/sevdesk-website-2020/.cache/schema.gql
warn There are conflicting field types in your data.
If you have explicitly defined a type for those fields, you can safely ignore this warning message.
Otherwise, Gatsby will omit those fields from the GraphQL schema.
If you know all field types in advance, the best strategy is to explicitly define them with the `createTypes` action, and skip inference with the `@dontInfer` directive.
See https://www.gatsbyjs.org/docs/actions/#createTypes
RecordsJson.logics.destination.componentId:
- type: number
value: 1
- type: string
value: 'integer'
success building schema - 4.031s
success createPages - 6.262s
success createPagesStatefully - 0.095s
info Total nodes: 258903, SitePage nodes: 1367 (use --verbose for breakdown)
success Checking for changed pages - 0.001s
success onPreExtractQueries - 0.001s
success extract queries from components - 5.171s
warn The GraphQL query in the non-page component "/Users/ben/Documents/Programmier Projekte/sevdesk-website-2020/src/templates/presseMitteilung.js" will not be run.
Exported queries are only executed for Page components. It's possible you're
trying to create pages in your gatsby-node.js and that's failing for some
reason.
If the failing component(s) is a regular component and not intended to be a page
component, you generally want to use a <StaticQuery> (https://gatsbyjs.org/docs/static-query)
instead of exporting a page query.
If you're more experienced with GraphQL, you can also export GraphQL
fragments from components and compose the fragments in the Page component
query and pass data down into the child component — https://graphql.org/learn/queries/#fragments
success write out redirect data - 0.019s
success Build manifest and related icons - 0.938s
success onPostBootstrap - 0.997s
info bootstrap finished - 136.715s
info changed file at /Users/ben/Documents/Programmier Projekte/sevdesk-website-2020/src/data/personalization/records.json
info changed file at /Users/ben/Documents/Programmier Projekte/sevdesk-website-2020/src/data/personalization/config.json
info changed file at /Users/ben/Documents/Programmier Projekte/sevdesk-website-2020/src/data/abtests.json
success write out requires - 0.061s
info changed file at /Users/ben/Documents/Programmier Projekte/sevdesk-website-2020/src/data/sales.json
success loading DatoCMS schema - 0.120s
success loading DatoCMS schema - 0.001s
success loading DatoCMS schema - 0.005s
success loading DatoCMS schema - 0.002s
success loading DatoCMS schema - 0.005s
success loading DatoCMS schema - 0.013s
success loading DatoCMS schema - 0.006s
success loading DatoCMS schema - 0.003s
success loading DatoCMS schema - 0.001s
success Building production JavaScript and CSS bundles - 150.838s
success Building HTML renderer - 34.695s
success Execute page configs - 0.026s
success Caching Webpack compilations - 0.002s
success run queries in workers - 9.092s - 1384/1384 152.22/s
success Merge worker state - 0.544s
success Rewriting compilation hashes - 0.014s
info Wrote out 27606 node page manifest files in 5764 ms.
info unstable_createNodeManifest produced warnings [11801, 11803]. Visit https://gatsby.dev/nodemanifest for more info on Node Manifests
success Writing page-data.json files to public directory - 1.473s - 1367/1367 928.05/s
success Building static HTML for pages - 4.217s - 1367/1367 324.14/s
success index to Algolia - 4.177s - Done!
warn [gatsby-plugin-netlify] Your site has 1367 pages, which means that the generated headers file could become very large. Consider disabling "mergeCachingHeaders" and "mergeLinkHeaders"
in your plugin config
info [gatsby-plugin-netlify] Creating SSR redirects...
info [gatsby-plugin-netlify] Created 0 SSR redirects...
info [gatsby-plugin-netlify] No Netlify functions needed. Skipping...
success onPostBuild - 6.742s
info Done building in 351.856007458 sec
Pages
┌ src/templates/autor-page.js
│ ├ /autoren/fabian-silberer/
│ └ /autoren/peter-sutter/
├ src/templates/landingpageKarriere.js
│ ├ /karriere/sales/
│ └ ...9 more pages available
├ src/templates/lpa-template.js
│ ├ /lpa-fotografie/
│ └ ...19 more pages available
├ src/templates/integrationen-template.js
│ ├ /integrationen/penta/
│ └ ...25 more pages available
├ src/templates/landingpagePaid.js
│ ├ /dividendenbackpacker/
│ └ ...32 more pages available
├ src/templates/kundenstimmen-template.js
│ ├ /kundenstimmen/webchaniker/
│ └ ...39 more pages available
├ src/templates/vorlagen-template.js
│ ├ /anzahlungsrechnung-muster/
│ └ ...68 more pages available
├ src/templates/landingpage-branchen.js
│ ├ /branchen/e-commerce/
│ └ ...65 more pages available
├ src/templates/customTemplate.js
│ ├ /orgamax-alternative/
│ └ ...263 more pages available
├ src/templates/article.js
│ ├ /lexikon/belegnummer/
│ └ ...413 more pages available
├ src/templates/blog-post.js
│ ├ /blog/content-marketing/
│ └ ...355 more pages available
├ src/templates/categories/marketing.js
│ ├ /kategorie/marketing/
│ └ /kategorie/marketing/2/
├ src/templates/categories/divers.js
│ └ /kategorie/divers/
├ src/templates/categories/finanzen.js
│ ├ /kategorie/finanzen/
│ └ ...8 more pages available
├ src/templates/categories/persoenlichkeit.js
│ ├ /kategorie/persoenlichkeit/
│ └ /kategorie/persoenlichkeit/2/
├ src/templates/categories/rechtliches.js
│ ├ /kategorie/rechtliches/
│ └ ...3 more pages available
├ src/templates/categories/inspiration.js
│ ├ /kategorie/inspiration/
│ └ ...7 more pages available
├ src/templates/categories/unternehmensfuehrung.js
│ ├ /kategorie/unternehmensfuehrung/
│ └ ...6 more pages available
├ src/templates/blog.js
│ ├ /blog/
│ └ ...29 more pages available
├ src/pages/404.js
│ ├ /404/
│ └ /404.html
├ src/pages/loginNews.js
│ └ /loginNews/
└ src/pages/store.js
└ /store/
╭────────────────────────────────────────────────────────────────╮
│ │
│ (SSG) Generated at build time │
│ D (DSG) Deferred static generation - page generated at runtime │
│ ∞ (SSR) Server-side renders at runtime (uses getServerData) │
│ λ (Function) Gatsby function │
│ │
╰────────────────────────────────────────────────────────────────╯
⠀
You can now view sevdesk-website in the browser.
⠀
http://localhost:9000/
This is what solved the issue: https://github.com/datocms/gatsby-source-datocms/commit/e5011baabf712c12002a8ce21e589fa09973270f
Honestly, nothing makes sense here. Hope Gatsby will explain the reasoning behind this, because we're just 🤷🏻
In the meantime, we've released the fix as a minor: 3.0.14
Thanks @stefanoverna and the DatoCMS team for fixing this so quickly! You guys are awesome!!!! Also, the fix is hilarious
Wow. I ran into this while upgrading from Gatsby 3 to Gatsby 4 and you probably saved me several hours of debugging, thank you!
I hate the incredibly hack-y-ness of the fix, but it works!
