Sandro@DESKTOP-P01QU4V MINGW64 ~/Desktop/code/gatsby-portfolio (master)
$ gatsby develop
success open and validate gatsby-configs - 0.119s
success load plugins - 1.847s
success onPreInit - 0.050s
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 no stale data.
success initialize cache - 0.157s
success copy gatsby files - 0.112s
success onPreBootstrap - 0.025s
success createSchemaCustomization - 0.071s
success Checking for changed pages - 0.001s
success source and transform nodes - 0.555s
success building schema - 0.651s
info Total nodes: 95, SitePage nodes: 13 (use --verbose for breakdown)
success createPages - 0.076s
success Checking for changed pages - 0.000s
success createPagesStatefully - 0.102s
success update schema - 0.047s
success write out redirect data - 0.001s
success Build manifest and related icons - 0.144s
success onPostBootstrap - 0.150s
info bootstrap finished - 7.518s
success onPreExtractQueries - 0.002s
ERROR #85923 GRAPHQL
There was an error in your GraphQL query:
Cannot query field "name" on type "GithubDataDataViewer".
If you don't expect "name" to exist on the type "GithubDataDataViewer" it is
most likely a typo.
However, if you expect "name" 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 "name" 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
"GithubDataDataViewer":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
File: src\pages\repositories.js:40:11
ERROR #85923 GRAPHQL
There was an error in your GraphQL query:
Cannot query field "description" on type
"GithubDataDataViewerRepositoriesNodes".
If you don't expect "description" to exist on the type
"GithubDataDataViewerRepositoriesNodes" it is most likely a typo.
However, if you expect "description" 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 "description" 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
"GithubDataDataViewerRepositoriesNodes":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
File: src\pages\repositories.js:45:15
ERROR #85923 GRAPHQL
There was an error in your GraphQL query:
Cannot query field "homepageUrl" on type
"GithubDataDataViewerRepositoriesNodes".
If you don't expect "homepageUrl" to exist on the type
"GithubDataDataViewerRepositoriesNodes" it is most likely a typo.
However, if you expect "homepageUrl" 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 "homepageUrl" 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
"GithubDataDataViewerRepositoriesNodes":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
File: src\pages\repositories.js:46:15
ERROR #85923 GRAPHQL
There was an error in your GraphQL query:
Cannot query field "languages" on type "GithubDataDataViewerRepositoriesNodes".
If you don't expect "languages" to exist on the type
"GithubDataDataViewerRepositoriesNodes" it is most likely a typo.
However, if you expect "languages" 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 "languages" 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
"GithubDataDataViewerRepositoriesNodes":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
File: src\pages\repositories.js:51:15
ERROR #85923 GRAPHQL
There was an error in your GraphQL query:
Cannot query field "licenseInfo" on type
"GithubDataDataViewerRepositoriesNodes".
If you don't expect "licenseInfo" to exist on the type
"GithubDataDataViewerRepositoriesNodes" it is most likely a typo.
However, if you expect "licenseInfo" 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 "licenseInfo" 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
"GithubDataDataViewerRepositoriesNodes":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
File: src\pages\repositories.js:59:15
failed extract queries from components - 0.690s
success write out requires - 0.021s
success run static queries - 0.155s - 4/4 25.78/s
success run page queries - 0.022s - 3/3 136.32/s
ERROR #98123 WEBPACK
Generating development JavaScript bundle failed
C:\Users\Sandro\Desktop\code\gatsby-portfolio\src\pages\repositories.js
40:11 error Cannot query field "name" on type "GithubDataDataViewer"
graphql/template-strings
β 1 problem (1 error, 0 warnings)
File: src\pages\repositories.js
failed Building development bundle - 15.371s
What is wrong? I'm trying to start developing for 2 hours, please help me.