This doesn't work with PNP and I think it will also break in some monorepos, where, for instance, your library could be at two lower level node-module folders but apollo is at the top level deduped.
Since the apollo CLI is javascript, I would either find a way to invoke the functionality you need directly with a javascript import, or use a different library to do the job. You could probably also get away without writing to a temp file which would be cleaner.
To make the current lib work with PNP, I had to unplug both apollo and mst-gql, and then do a manual symlink between their folders to get the binary where your lib expects it to be.
This is a brittle way to go about invoking the apollo schema downloader CLI.
This doesn't work with PNP and I think it will also break in some monorepos, where, for instance, your library could be at two lower level node-module folders but apollo is at the top level deduped.
Since the apollo CLI is javascript, I would either find a way to invoke the functionality you need directly with a javascript import, or use a different library to do the job. You could probably also get away without writing to a temp file which would be cleaner.
To make the current lib work with PNP, I had to
unplug
both apollo and mst-gql, and then do a manual symlink between their folders to get the binary where your lib expects it to be.