v3 - Error: Type with name "File" does not exists

[gbreux]

Hi,

I'm giving the alpha v3 a try (because I need optional field :)) but I encounter this error when I try to start :

  Error: Type with name "File" does not exists
  
  - TypeStorage.js:44 SchemaComposer.get
    [prismic]/[graphql-compose]/lib/TypeStorage.js:44:
    13
  
  - TypeMapper.js:86 TypeMapper.get
    [prismic]/[graphql-compose]/lib/TypeMapper.js:86:4
    4
  
  - TypeMapper.js:608 TypeMapper.typeFromAST
    [prismic]/[graphql-compose]/lib/TypeMapper.js:608:
    17
  
  - TypeMapper.js:105 TypeMapper.getWrapped
    [prismic]/[graphql-compose]/lib/TypeMapper.js:105:
    17
  
  - TypeMapper.js:272 TypeMapper.convertOutputFieldCon
    fig
    [prismic]/[graphql-compose]/lib/TypeMapper.js:272:
    114
  
  - configAsThunk.js:19 resolveOutputConfigAsThunk
    [prismic]/[graphql-compose]/lib/utils/configAsThun
    k.js:19:41
  
  - configAsThunk.js:37 Object.keys.forEach.name
    [prismic]/[graphql-compose]/lib/utils/configAsThun
    k.js:37:22
  
  - Array.forEach
  
  - configAsThunk.js:36 resolveOutputConfigMapAsThunk
    [prismic]/[graphql-compose]/lib/utils/configAsThun
    k.js:36:27
  
  - ObjectTypeComposer.js:147 GraphQLObjectType.gqType
    ._fields
    [prismic]/[graphql-compose]/lib/ObjectTypeComposer

Any idea where this can come from? How can I help you get more information about that?

PS: I copied the json files in their schema folder and added it to the config

[angeloashmore]

@gbreux Thanks for giving it a try! We are planning to publish a beta soon but I'll see if there's a better solution to this before we publish.

The File type is used for the gatsby-image integration. The localFile field of any image field is of type File.

You can see it here: https://github.com/angeloashmore/gatsby-source-prismic/blob/v3-beta/src/standardTypes.graphql#L70

Do you have gatsby-plugin-sharp and gatsby-transformer-sharp installed in your project?

If you are able to clear you cache, could you also try gatsby clean before trying again?

[gbreux]

I see, I reinstalled my node_modules, used gatsby clean and I don't have the gatsby plugin you mentioned, but I still have the error. Here is my dependencies:

"dependencies": {
    "gatsby": "^2.6.3",
    "query-string": "^6.5.0",
    "react": "^16.8.6",
    "react-dom": "^16.8.6",
    "react-helmet": "^5.2.1",
    "react-js-pagination": "^3.0.2",
    "react-typography": "^0.16.19",
    "styled-components": "^4.2.0",
    "typography": "^0.16.19"
  },
  "devDependencies": {
    "babel-plugin-styled-components": "^1.10.0",
    "dotenv": "^8.0.0",
    "gatsby-plugin-netlify": "^2.0.17",
    "gatsby-plugin-styled-components": "^3.0.7",
    "gatsby-plugin-typography": "^2.2.13",
    "gatsby-source-prismic": "^3.0.0-alpha.2",
    "prettier": "^1.17.0"
  }

🤔

[angeloashmore]

@gbreux Any chance your repo is open source? Could we take a look?

If not, could you create a simple repo that reproduces the issue? @asyarb tried recreating the issue with different combinations of image fields and plugins but wasn't able to get the same thing you're experiencing.

[gbreux]

Sure, here it is: https://github.com/gbreux/nodokasa

[gbreux]

Interesting, I didn't have any image field on my schemas (I don't need one). But once I added one just for testing, I don't have this error anymore.

Edit confirmed: If you have just one article published with an image field no matter where, you don't get this error

[angeloashmore]

@gbreux It's possible that we're telling Gatsby that images have a localFile field with type File, but Gatsby doesn't know what File is until one is created.

I don't have a solution in mind yet, but your diagnosis is helpful. Thank you!

[gbreux]

Happy to help, in the meantime I can just create a temporary custom type with one element and a picture that I will never use.

Hope you'll find a solution :)

[jenshandersson]

I just ran into this same issue. Created a fresh repository with 1 page (without setting any image). After setting an image in my content this error went away.

[angeloashmore]

This should be resolved upstream in gatsby-source-filesystem. 🎉

[ryanditjia]

Still getting the error even with gatsby-source-filesystem updated.

[good-idea]

I'm getting this with the latest versions installed,

    "gatsby-source-filesystem": "^2.1.22",
    "gatsby-source-prismic": "^3.0.0-beta.10",

I had shouldNormalizeImage always return false, because I don't need the images locally. That was causing the error. My hacky fix was to include one image:

gatsby-config.js

let should = true

module.exports = {
  // ...
  plugins: [
   // ...
    {
      resolve: `gatsby-source-prismic`,
      options: {
        shouldNormalizeImage: (...args) => {
          const should = once
          once = false
          return should
        },
      },
    },
  ],
}

@angeloashmore do you work for Prismic? If not, they should be sponsoring you.

[martaver]

Heya,

I'm on what I (think) is the latest release of this plugin 3.0.0-beta.15, but I'm still getting this issue.

I have a repro here: https://github.com/beaufort-asia/www/tree/repro

I'm getting it even though I published dummy articles with Image fields included and all that.

Maybe an edge case here that you missed?