Building schema failed: Type <type name> declared in createTypes looks like a node, but doesn't implement a Node interface

[arsinclair]

Description

With @imgix/gatsby enabled, gatsby develop and gatsby build result in the following error:

warn Type ImagesJson declared in createTypes looks like a node, but doesn't implement a Node interface. It's likely that you should add the Node interface to your type def:
type ImagesJson implements Node { ... }
If you know that you don't want it to be a node (which would mean no root queries to retrieve it), you can explicitly disable inference for it:
type ImagesJson @dontInfer { ... }
ERROR
Building schema failed
not finished building schema - 0.106s

To Reproduce
I have the following tandem configured: gatsby-source-filesystem to read a json file called images.json with data, like this:

[
    {
        "url": "https://bucket.imgix.net/images/header/splash.jpg"
    }
]

then gatsby-transformer-json to parse the JSON file, and finally @imgix/gatsby with the following configuration:

        {
            resolve: "@imgix/gatsby",
            options: {
                domain: "bucket.imgix.net",
                sourceType: ImgixSourceType.AmazonS3,
                fields: [
                    {
                        nodeType: "ImagesJson",
                        getURL: (node) => node.url,
                        fieldName: 'image'
                    }
                ]
            }
        }

If I disable @imgix/gatsby in the config - build succeeds. The JSON is parsed just fine, verified in GraphiQL.

It appears to be clear that the issue is isolated to imgix/gatsby.

Expected behaviour
No error, and an images node with stuff added to my ImagesJson object. The configuration above used to work with gatsby-plugin-imgix and Gatsby v2 before.

Information:

• imgix/gatsby version: 1.6.11
• browser version: Version 1.25.72 Chromium: 91.0.4472.101 (Official Build) (64-bit)
• OS used: Debian GNU/Linux 10 (buster)

Additional context
I'm happy to provide any additional information, if required.

[frederickfogerty]

Hi @arsinclair 👋 thanks for opening this issue. Sorry that you've had this experience - I've put this on my schedule to investigate next week. I'll provide any updates here.

[arsinclair]

Hi @cecasey wave thanks for opening this issue.

Pardon? 🙁

[frederickfogerty]

Sorry @arsinclair, I was responding to another issue at the same time and I must have got my wires crossed here!

[luqven]

Hey @arsinclair,

Having trouble reproducing the issue. Do you think you could create and link an example repo that reproduces it?

Thanks again for taking the time to report this.

[arsinclair]

Do you think you could create and link an example repo that reproduces it

Sure. Here's the repo: https://github.com/arsinclair/gatsby-image-schema-bug-reproduction

Just run npm install && npm run develop.

P.S.: I used a test image from imgix, because I can not use put my organization's endpoint. I don't know if Imgix uses Amazon.S3 as the backend for their assets.imgix.net, but it is clear that the issue is reproduced with any image.

[arsinclair]

If you comment out the @imgix/gatsby config in gatsby-config.js file and use GraphiQL, you'll see that the actual image URL is parsed okay and the type name matches:

{
  imagesJson {
  	__typename
    url
  }
}

output:

{
  "data": {
    "imagesJson": {
      "__typename": "ImagesJson",
      "url": "https://assets.imgix.net/examples/bluehat.jpg"
    }
  },
  "extensions": {}
}

[luqven]

Hey @arsinclair,

Thanks again for sending over the example repo, it was extremely helpful!

This issue should be fixed in version 1.6.12-rc.1. You can install it by running npm i @imgix/gatsby@next or npm i @imgix/gatsby@1.6.12-rc.1.

If for any reason this isn't resolved please free to comment on this issue so we can open it up again.

[lezan]

Hey @luqven, can you confirm this is fixed with 1.7.1 and there is not a regression? I am experience the same issue of @arsinclair but with ImgixSourceType.WebProxy.

[luqven]

@lezan thanks for tagging me and letting me know this issue wasn't fixed.

It appears that #138 never made it into main. I've gone ahead and PRd #154 the change and will update when it's released.

[luqven]

Hey @lezan, thanks again for letting us know this was still an issue.

The issue should be fixed in version 1.7.3. You can install it by running npm i @imgix/gatsby@latest or npm i @imgix/gatsby@1.7.3.

If for any reason this isn't resolved please free to comment on this issue so we can open it up again.