"No operations or fragments" error during client:codegen

[chrishandorf]

I'm running client:codegen on apollo/2.1.2 darwin-x64 node-v10.13.0
(iMac)

The endpoint is successfully reached but codegen can't seem to find any files that are specified using the --queries option. The files do exist though. I get the same error if I use --localSchemaFile=schema.json instead of --endpoint. See the 2 commands run below:

$ apollo client:codegen --target=typescript --endpoint=http://localhost:8080/graphql --queries="./src/app/graphqlPublic/*.graphql"
✔ Loading Apollo Project
✖ Generating query files with 'typescript' target
→ No operations or fragments found to generate code for.
Error: No operations or fragments found to generate code for.
at write (/.npm-global/lib/node_modules/apollo/lib/commands/client/codegen.js:58:39)
at Task.task (/.npm-global/lib/node_modules/apollo/lib/commands/client/codegen.js:83:46)

$ cat ./src/app/graphqlPublic/page-visit.graphql
query PageVisit($page: String!){
pageVisit(page:$page)
}

[ZenSoftware]

Since Apollo 2, I have been getting the same error using client:codegen. No matter what I try, I can't seem to get apollo cli to pick up the files that I have defined. Things that I have tried:

• Used the includes field defined in an apollo.config.js.
• Used the --queries flag.
• Used different glob patterns, including: *.ts files that use gql tagged template literals, *.gql and *.graphql.

The files do exist, have proper syntax, and a legitimate schema.json because I can generate types using apollo v1.

My machine specs:
Windows 10
Node v10.13.0
apollo@2.1.2

The error:

apollo client:codegen --target=typescript --outputFlat --localSchemaFile="libs/gql/schema.json" --queries="libs/**/*.gql"
 √ Loading Apollo Project
 × Generating query files with 'typescript' target
   → No operations or fragments found to generate code for.
Error: No operations or fragments found to generate code for.
    at write (C:/Users/Zen/AppData/Roaming/npm/node_modules/apollo/lib/commands/client/codegen.js:58:39)
    at Task.task (C:/Users/Zen/AppData/Roaming/npm/node_modules/apollo/lib/commands/client/codegen.js:83:46)

[chenglabs]

I have the same problem.. It can't handle relative paths in the includes field.
It only works when I configure it with the full path

apollo client:codegen src/types -c=apollo.config.js --target=typescript --outputFlat

apollo.config.js.
module.exports = {
client: {
includes: [__dirname+'/src/queries/**'],
service: {
name: "hello-service",
url: "http://localhost:4000/graphql",
}
}
}

[ZenSoftware]

@chenglabs Interesting that you managed to get it to work at least. I just tried it with absolute paths, and I was not able to get it to work. Could you please provide us with the specifications of your system you are working on?

[chrishandorf]

I used the full pathname for the --queries arg instead of the relative path used above. Still no luck. Same result and completely blocked.

[chrishandorf]

I just saw in another issue thread this command was working in apollo@1.9.2. I downgraded and yay it worked fine.

[chenglabs]

@chenglabs Interesting that you managed to get it to work at least. I just tried it with absolute paths, and I was not able to get it to work. Could you please provide us with the specifications of your system you are working on?

Hi,

check example at https://github.com/chenglabs/test_apollo_client
Quickly added some code together with create-react-app to test with
Generate the types with yarn types

[JakeDawkins]

@chenglabs I was able to reproduce the issue you were seeing. If you remove the leading / in your includes path, it should work. Like this:

module.exports = {
   client: {
     includes: ['src/queries/**'],
     service: {
       name: "pokemon",
       url: "https://graphql-pokemon.now.sh",
     }
   }
 }

[JakeDawkins]

@ZenSoftware @chrishandorf do either of you have a reproduction on codesandbox/glitch/github that I could look at?

[chenglabs]

@JakeDawkins
Hi Jake,
Tried your solution, it results in the same errors. I think it's Windows related, if I run the script in Windows Bash shell it works without any problems.

[delannoyk]

Hey.

Got the same issue on macOS so I don't think it's Windows related 🤔 Unfortunately I don't have a lot of insights to offer...

[chenglabs]

@JakeDawkins

Ok, did some debugging in the Apollo code
I think there is a bug in packages/apollo/src/Command.ts line 175
const rootURI = file://${parse(filepath).dir};
should be
const rootURI = file:///${parse(filepath).dir};

It's missing one slash.. (https://en.wikipedia.org/wiki/File_URI_scheme)
When I added the slash in node_modules\Apollo\lib\Command.js everything works.

[chrishandorf]

@chenglabs If I make the above change you suggested locally I get this:

$ apollo client:codegen --queries='src/app/graphqlPublic/*.graphql' --localSchemaFile=schema.json --target=typescript
Error: [UriError]: If a URI does not contain an authority component, then the path cannot begin with two slash characters ("//")
at _validateUri (~/.npm-global/lib/node_modules/apollo/node_modules/vscode-uri/lib/umd/index.js:57:27)

@JakeDawkins I could work on a minimal set of files to reproduce the problem if that would be helpful. I haven't used codesandbox. Is there another way I could send you the fileset?

[trevor-scheer]

This seems like the root of the issue:

Tried your solution, it results in the same errors. I think it's Windows related, if I run the script in Windows Bash shell it works without any problems.

I'm going to try to get a Windows environment set up since I need to be able to reproduce issues like this that pop up.

@chenglabs @chrishandorf I see the same issue with the 3 slashes. It looks like VSCode's URI implementation takes care of the third slash:

let uri = Uri.file('/users/me/c#-projects/');

assert.ok(uri.scheme === 'file');
assert.ok(uri.authority === '');
assert.ok(uri.path === '/users/me/c#-projects/');
assert.ok(uri.query === '');
assert.ok(uri.fragment === '');
assert.ok(uri.toString() === 'file:///users/me/c%23-projects/')

https://github.com/Microsoft/vscode-uri

@chrishandorf a repo that we can clone is best!

[chrishandorf]

@JakeDawkins @trevor-scheer please see this: https://github.com/chrishandorf/apolloError

Its completely bare bones and not working