draftbox-co / gatsby-attila-theme-starter Goto Github PK

warn Plugin @draftbox-co/gatsby-theme-ghost-attila is not compatible with your gatsby version 2.24.80 - It requires [email protected]
success open and validate gatsby-configs - 0.094s
warn Plugin @draftbox-co/gatsby-plugin-css-variables is not compatible with your gatsby version 2.24.80 - It requires [email protected]
warn Plugin @draftbox-co/gatsby-theme-ghost-attila is not compatible with your gatsby version 2.24.80 - It requires [email protected]
success load plugins - 0.355s
success onPreInit - 0.025s
success delete html and css files from previous builds - 0.003s
success initialize cache - 0.007s
success copy gatsby files - 0.014s
warn gatsby-plugin-feed was initialized in gatsby-config.js without a title in a feed.
This means that the plugin will use the default feed title, which may not match your use case.
This behavior will be removed in the next major release of gatsby-plugin-feed.
For more info, check out: https://gatsby.dev/adding-rss-feed
success onPreBootstrap - 1.738s
success createSchemaCustomization - 0.011s
success Checking for changed pages - 0.008s
success source and transform nodes - 2.550s
warn Plugin `@draftbox-co/gatsby-theme-ghost-attila` has customized the GraphQL type `GhostPost`, which has already been defined by the plugin `gatsby-source-ghost`. This could potentially
warn Plugin `@draftbox-co/gatsby-theme-ghost-attila` has customized the GraphQL type `GhostPage`, which has already been defined by the plugin `gatsby-source-ghost`. This could potentially
success building schema - 0.392s
info Total nodes: 74, SitePage nodes: 5 (use --verbose for breakdown)
success createPages - 0.041s
success Checking for changed pages - 0.001s
success createPagesStatefully - 0.062s
success update schema - 0.024s
success onPreExtractQueries - 0.003s

 ERROR #85923  GRAPHQL

There was an error in your GraphQL query:

Cannot query field "localFeatureImage" on type "GhostPage".

If you don't expect "localFeatureImage" to exist on the type "GhostPage" it is most likely a typo.
However, if you expect "localFeatureImage" 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 "localFeatureImage" 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 "GhostPage":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions

File: node_modules/@draftbox-co/gatsby-theme-ghost-attila/src/templates/pageTemplate.jsx:347:7


 ERROR #85923  GRAPHQL

There was an error in your GraphQL query:

Cannot query field "localFeatureImage" on type "GhostPost".

If you don't expect "localFeatureImage" to exist on the type "GhostPost" it is most likely a typo.
However, if you expect "localFeatureImage" 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 "localFeatureImage" 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 "GhostPost":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions

File: node_modules/@draftbox-co/gatsby-theme-ghost-attila/src/templates/postTemplate.amp.jsx:112:7


 ERROR #85923  GRAPHQL

There was an error in your GraphQL query:

Cannot query field "localFeatureImage" on type "GhostPost".

If you don't expect "localFeatureImage" to exist on the type "GhostPost" it is most likely a typo.
However, if you expect "localFeatureImage" 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 "localFeatureImage" 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 "GhostPost":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions

File: node_modules/@draftbox-co/gatsby-theme-ghost-attila/src/templates/postTemplate.jsx:371:7

failed extract queries from components - 0.480s

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/gatsby
npm ERR!   dev gatsby@"2.20.24" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer gatsby@"^4.13.1" from [email protected]
npm ERR! node_modules/gatsby-plugin-mixpanel
npm ERR!   gatsby-plugin-mixpanel@"^3.1.6" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.