You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am receiving below error when running : 'npm run develop' , specifically Cannot query field "altText" on type "hwgraphql_NodeWithFeaturedImageToMediaItemConnectionEdge".
and error Generating development JavaScript bundle failed
success open and validate gatsby-configs - 0.041s
success load plugins - 1.801s
success onPreInit - 0.118s
success initialize cache - 0.020s
success copy gatsby files - 0.089s
success onPreBootstrap - 0.031s
success createSchemaCustomization - 0.027s
success Checking for changed pages - 0.003s
success source and transform nodes - 7.512s
Found schema 'hwgraphql', traversing for fields with name 'sourceUrl'
success building schema - 1.759s
error There was an error in your GraphQL query:
Cannot query field "altText" on type "hwgraphql_NodeWithFeaturedImageToMediaItemConnectionEdge".
If you don't expect "altText" to exist on the type "hwgraphql_NodeWithFeaturedImageToMediaItemConnectionEdge" it is most likely a typo.
However, if you expect "altText" 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 "altText" 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 "hwgraphql_NodeWithFeaturedImageToMediaItemConnectionEdge": https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
error There was an error in your GraphQL query:
Cannot query field "sourceUrl" on type "hwgraphql_NodeWithFeaturedImageToMediaItemConnectionEdge".
If you don't expect "sourceUrl" to exist on the type "hwgraphql_NodeWithFeaturedImageToMediaItemConnectionEdge" it is most likely a typo.
However, if you expect "sourceUrl" 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 "sourceUrl" 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 "hwgraphql_NodeWithFeaturedImageToMediaItemConnectionEdge": https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
error There was an error in your GraphQL query:
Cannot query field "sourceUrlSharp" on type "hwgraphql_NodeWithFeaturedImageToMediaItemConnectionEdge".
If you don't expect "sourceUrlSharp" to exist on the type "hwgraphql_NodeWithFeaturedImageToMediaItemConnectionEdge" it is most likely a typo.
However, if you expect "sourceUrlSharp" 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 "sourceUrlSharp" 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 "hwgraphql_NodeWithFeaturedImageToMediaItemConnectionEdge": https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
error "gatsby-wordpress-theme-phoenix" threw an error while running the createPages lifecycle:
I am receiving below error when running : 'npm run develop' , specifically
Cannot query field "altText" on type "hwgraphql_NodeWithFeaturedImageToMediaItemConnectionEdge".
and
error Generating development JavaScript bundle failed
encinoe@web:~/my-gatsby-project$ npm run develop
success open and validate gatsby-configs - 0.041s
success load plugins - 1.801s
success onPreInit - 0.118s
success initialize cache - 0.020s
success copy gatsby files - 0.089s
success onPreBootstrap - 0.031s
success createSchemaCustomization - 0.027s
success Checking for changed pages - 0.003s
success source and transform nodes - 7.512s
Found schema 'hwgraphql', traversing for fields with name 'sourceUrl'
success building schema - 1.759s
error There was an error in your GraphQL query:
Cannot query field "altText" on type "hwgraphql_NodeWithFeaturedImageToMediaItemConnectionEdge".
If you don't expect "altText" to exist on the type "hwgraphql_NodeWithFeaturedImageToMediaItemConnectionEdge" it is most likely a typo.
However, if you expect "altText" to exist there are a couple of solutions to common problems:
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 "hwgraphql_NodeWithFeaturedImageToMediaItemConnectionEdge":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
error There was an error in your GraphQL query:
Cannot query field "sourceUrl" on type "hwgraphql_NodeWithFeaturedImageToMediaItemConnectionEdge".
If you don't expect "sourceUrl" to exist on the type "hwgraphql_NodeWithFeaturedImageToMediaItemConnectionEdge" it is most likely a typo.
However, if you expect "sourceUrl" to exist there are a couple of solutions to common problems:
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 "hwgraphql_NodeWithFeaturedImageToMediaItemConnectionEdge":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
error There was an error in your GraphQL query:
Cannot query field "sourceUrlSharp" on type "hwgraphql_NodeWithFeaturedImageToMediaItemConnectionEdge".
If you don't expect "sourceUrlSharp" to exist on the type "hwgraphql_NodeWithFeaturedImageToMediaItemConnectionEdge" it is most likely a typo.
However, if you expect "sourceUrlSharp" to exist there are a couple of solutions to common problems:
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 "hwgraphql_NodeWithFeaturedImageToMediaItemConnectionEdge":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
error "gatsby-wordpress-theme-phoenix" threw an error while running the createPages lifecycle:
Cannot read property 'HWGraphQL' of undefined
8 | // Create all pages.
9 | exports.createPages = async ( { actions, graphql } ) => {
TypeError: Cannot read property 'HWGraphQL' of undefined
pages.js:64
[my-gatsby-project]/[gatsby-wordpress-theme-phoenix]/create-pages/pages.js:64:50
pages.js:61 fetchPosts
[my-gatsby-project]/[gatsby-wordpress-theme-phoenix]/create-pages/pages.js:61:10
pages.js:71 module.exports
[my-gatsby-project]/[gatsby-wordpress-theme-phoenix]/create-pages/pages.js:71:2
gatsby-node.js:10 Object.exports.createPages
[my-gatsby-project]/[gatsby-wordpress-theme-phoenix]/gatsby-node.js:10:2
api-runner-node.js:460 runAPI
[my-gatsby-project]/[gatsby]/src/utils/api-runner-node.js:460:16
From previous event:
api-runner-node.js:589 Promise.catch.decorateEvent.pluginName
[my-gatsby-project]/[gatsby]/src/utils/api-runner-node.js:589:9
From previous event:
api-runner-node.js:588
[my-gatsby-project]/[gatsby]/src/utils/api-runner-node.js:588:14
timers.js:461 processImmediate
internal/timers.js:461:21
From previous event:
api-runner-node.js:561
[my-gatsby-project]/[gatsby]/src/utils/api-runner-node.js:561:13
From previous event:
api-runner-node.js:477 module.exports
[my-gatsby-project]/[gatsby]/src/utils/api-runner-node.js:477:3
create-pages.ts:25 createPages
[my-gatsby-project]/[gatsby]/src/services/create-pages.ts:25:9
interpreter.js:722 Interpreter.exec
[my-gatsby-project]/[xstate]/lib/interpreter.js:722:27
interpreter.js:204 Interpreter.execute
[my-gatsby-project]/[xstate]/lib/interpreter.js:204:22
interpreter.js:224 Interpreter.update
[my-gatsby-project]/[xstate]/lib/interpreter.js:224:18
interpreter.js:125
[my-gatsby-project]/[xstate]/lib/interpreter.js:125:23
scheduler.js:60 Scheduler.process
[my-gatsby-project]/[xstate]/lib/scheduler.js:60:13
scheduler.js:44 Scheduler.schedule
[my-gatsby-project]/[xstate]/lib/scheduler.js:44:14
interpreter.js:121 Interpreter.send
[my-gatsby-project]/[xstate]/lib/interpreter.js:121:29
interpreter.js:840 actor.id
[my-gatsby-project]/[xstate]/lib/interpreter.js:840:23
info Total nodes: 66, SitePage nodes: 1 (use --verbose for breakdown)
failed createPages - 0.457s
success Checking for changed pages - 0.001s
success createPagesStatefully - 0.141s
success update schema - 0.031s
success write out redirect data - 0.002s
success Build manifest and related icons - 0.173s
success onPostBootstrap - 0.176s
info bootstrap finished - 20.418s
success onPreExtractQueries - 0.001s
success extract queries from components - 1.035s
success write out requires - 0.203s
success run static queries - 0.824s - 2/2 2.43/s
success run page queries - 0.022s - 1/1 45.43/s
error Generating development JavaScript bundle failed
error Generating development JavaScript bundle failed
error Generating development JavaScript bundle failed
failed Building development bundle - 13.442s
The text was updated successfully, but these errors were encountered: