Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Multiple definitions for query

See original GitHub issue

Issue Description

Do you mind taking a look at this starter? I am getting the error show below in vscode-apollo, and I’m not sure if I should start here, or with vscode-apollo. It almost seems like it could be happening because the query exists in the image component, as well as in plugin-documents.graphql.

I’ve noticed this same error in other repositories, and from time to time it will make the plugin crash. Disabling one or the other of

// apollo.config.js
        includes: [
            `${__dirname}/src/**/*.{ts,tsx}`,
            `${__dirname}/.gatsby/graphql/plugin-documents.graphql`,
        ], // eslint-disable-line graphql/template-strings

will fix the error, but then I don’t get full support from the plugin.

If this is not an issue caused by a conflict between gatsby-plugin-typegen and vscode-apollo, or a misconfiguration, but is instead an issue solely with vscode-apollo, then I will open an issue there.

Issue Analytics

State:
Created 3 years ago
Comments:14 (14 by maintainers)

Top GitHub Comments

2reactions

Js-Brechtcommented, Feb 28, 2020

Can you try again on the latest version? (v1.1.1)

Same problem.

I think I have found one issue:

  console.log(path.resolve(basePath, 'src'));
  console.log(trackedSource.keys());
  process.exit(0);

  const pluginDocuments = Object.values(emitPluginDocuments).some(Boolean) && (
    stripIndent(
      Array.from(trackedSource.entries())
        .filter(([componentPath]) => !componentPath.startsWith(path.resolve(basePath, 'src')))
        .map(([, source]) => source.rawSDL)
        .join('\n'),
    )
  );

will return

D:\dev\source\gatsby\gatsby-starter-pnpm-ts\src
[Map Iterator] {
  'D:/dev/source/gatsby/gatsby-starter-pnpm-ts/src/components/seo.tsx',
  'D:/dev/source/gatsby/gatsby-starter-pnpm-ts/src/layouts/main.tsx',
  'D:/dev/source/gatsby/gatsby-starter-pnpm-ts/src/components/image.tsx',
  'D:/dev/source/gatsby/gatsby-starter-pnpm-ts/node_modules/.pnpm/registry.npmjs.org/gatsby-transformer-sharp/2.3.13_04195f47e3c92d97e09f933485bf4df6/node_modules/gatsby-transformer-sharp/src/fragments.js' }

So, path.resolve() is returning non-posix compliant paths on Windows, while the trackedSource entries are (semi) posix compliant.

If I change that section to normalize componentPath:

  const pluginDocuments = Object.values(emitPluginDocuments).some(Boolean) && (
    stripIndent(
      Array.from(trackedSource.entries())
        .filter(([componentPath]) => !path.normalize(componentPath).startsWith(path.resolve(basePath, 'src')))
        .map(([, source]) => source.rawSDL)
        .join('\n'),
    )
  );

I get the desired results

1reaction

Js-Brechtcommented, Mar 8, 2020

I will copy the conversation to a new issue