M4ss1ck
commented
2 years ago I changed my GRAPHCMS_TOKEN enviroment variable with a different one just for doing something (the previous one was working with gatsby v2) and now I can use gatsby develop just fine. However, gatsby build throws the following errors
> gatsby build
success open and validate gatsby-configs, load plugins - 1.875s
success onPreInit - 0.006s
success delete worker cache from previous builds - 0.004s
success initialize cache - 0.063s
success copy gatsby files - 0.364s
success Compiling Gatsby Functions - 0.481s
success onPreBootstrap - 0.509s
success createSchemaCustomization - 0.014s
warn Calling `createTypes` in the `sourceNodes` API is deprecated. Please use: `createSchemaCustomization`.
success [gatsby-graphql-toolkit] fetching New - 0.743s
success [gatsby-graphql-toolkit] fetching Page - 0.759s
success [gatsby-graphql-toolkit] fetching ScheduledOperation - 0.753s
success [gatsby-graphql-toolkit] fetching Post - 0.786s
success [gatsby-graphql-toolkit] fetching Seo - 0.878s
success [gatsby-graphql-toolkit] fetching ScheduledRelease - 0.969s
success [gatsby-graphql-toolkit] fetching Author - 1.096s
success [gatsby-graphql-toolkit] fetching Asset - 1.116s
success [gatsby-graphql-toolkit] fetching User - 1.166s
success Checking for changed pages - 0.003s
success source and transform nodes - 2.853s
info Writing GraphQL type definitions to E:/TRABAJO/web/1. Proyectos/wasting-blog/.cache/schema.gql
success building schema - 2.400s
success createPages - 0.490s
success createPagesStatefully - 0.231s
info Total nodes: 122, SitePage nodes: 10 (use --verbose for breakdown)
success Checking for changed pages - 0.003s
success Cleaning up stale page-data - 0.005s
success onPreExtractQueries - 0.003s
warn `createResolvers` passed resolvers for type `GraphCMS_Post` that doesn't exist in the schema. Use `createTypes` to add the type before adding
resolvers.
success extract queries from components - 2.184s
success write out redirect data - 0.009s
success onPostBootstrap - 0.010s
info bootstrap finished - 15.488s
success write out requires - 0.019s
success Building production JavaScript and CSS bundles - 1.562s
success Building HTML renderer - 1.003s
success Execute page configs - 0.035s
success Caching Webpack compilations - 0.001s
ERROR #85923 GRAPHQL
There was an error in your GraphQL query:
Cannot query field "id" on type "GraphCMS_Asset".
If you don't expect "id" to exist on the type "GraphCMS_Asset" it is most likely a typo.
However, if you expect "id" to exist there are a couple of solutions to common problems:
- If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server
- The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query
and what shape they have
- You want to optionally use your field "id" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL
schema. A quick fix is to add at least one entry with that field ("dummy content")
It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy
content". Visit our docs to learn how you can define the schema for "GraphCMS_Asset":
https://www.gatsbyjs.com/docs/reference/graphql-data-layer/schema-customization#creating-type-definitions
ERROR #85923 GRAPHQL
There was an error in your GraphQL query:
Cannot query field "graphCmsAsset" on type "Query".
If you don't expect "graphCmsAsset" to exist on the type "Query" it is most likely a typo.
However, if you expect "graphCmsAsset" to exist there are a couple of solutions to common problems:
- If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server
- The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query
and what shape they have
- You want to optionally use your field "graphCmsAsset" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the
GraphQL schema. A quick fix is to add at least one entry with that field ("dummy content")
It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy
content". Visit our docs to learn how you can define the schema for "Query":
https://www.gatsbyjs.com/docs/reference/graphql-data-layer/schema-customization#creating-type-definitions
ERROR #85923 GRAPHQL
There was an error in your GraphQL query:
Cannot query field "graphCmsAsset" on type "Query".
If you don't expect "graphCmsAsset" to exist on the type "Query" it is most likely a typo.
However, if you expect "graphCmsAsset" to exist there are a couple of solutions to common problems:
- If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server
- The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query
and what shape they have
- You want to optionally use your field "graphCmsAsset" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the
GraphQL schema. A quick fix is to add at least one entry with that field ("dummy content")
It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy
content". Visit our docs to learn how you can define the schema for "Query":
https://www.gatsbyjs.com/docs/reference/graphql-data-layer/schema-customization#creating-type-definitions
ERROR #85928
An error occurred during parallel query running.
Go here for troubleshooting tips: https://gatsby.dev/pqr-feedback
Error: Worker exited before finishing task
- index.js:112 ChildProcess.<anonymous>
[wasting-blog]/[gatsby-worker@1.3.0]/[gatsby-worker]/dist/index.js:112:45
- child_process.js:277 Process.ChildProcess._handle.onexit
internal/child_process.js:277:12
not finished run queries in workers - 0.237s
ELIFECYCLE Command failed with exit code 1.
I guess it got something to do with the two warnings at the beginning, but in development (pnpm dev) there's only one and there's no error
Coffeeri
acidicX
nickmarks00
notrab
I got the following error after updating gatsby from v2 to v4
In gatsby-config.js I have
Steps to reproduce:
clone https://github.com/M4ss1ck/wasting-blog/tree/actualizar-dependencias and run
pnpm devorpnpm buildgatsby-cli info: