No error message when types aren't generated because of anonymous GraphQL queries

[JagdCake]

I'm working on a TypeScript starter using gatsby-starter-default as a base. I followed the steps in this blog post to get TypeScript support, however on the last step — generating the types using this plugin — the types weren't being generated.

Running npm run develop displayed success messages:

success [gatsby-plugin-codegen] saved localSchemaFile: ./schema.json
success [gatsby-plugin-codegen] saved apollo config:
success [gatsby-plugin-codegen] types for typescript generated

Both the schema and config files showed up, but the __generated__ directories didn't.

I tried node_modules/apollo/bin/run client:codegen -c apollo.config.js --target=typescript --outputFlat gql-types.d.ts and I got an error: Apollo does not support anonymous operations, which led me to this comment. Naming the queries fixed the problem.

[daugsbi]

Yes, all queries need a unique name (compare with apollographql/apollo-tooling#670).

I've tried to reproduce the incorrect success message. When I do not name one query it shows me the following

Do you have any additional information or a repository to share?

[JagdCake]

git clone --branch gql-types https://github.com/JagdCake/gatsby-typescript-tailwind-starter.git. The query in src/components/seo.tsx is anonymous and when I run npm run develop there is no error, git status shows only the apollo config and schema.json.

[daugsbi]

Thanks for the reproduction 👍
As a temporary workaround set the plugin option watch to false.

I need to check if it's possible to keep the file watchers of apollo and still be compatible with the newest version of gatsby-cli (>=2.8.28).

Please keep the issue open

[daugsbi]

I've changed the default option watch to false. For people still wanted to use the watch mode the best solution is to set it the following way:
watch: process.env.NODE_ENV === "development" ? true : false

As a result you get the error message during build time instead of development.