New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Code generation broken on 2.12.3 #1329
Comments
I always run into this problem when I have |
I have same issue with that. Seems like it's broken since
|
Investigated this a little bit, here's what I found out: When
As If anyone gets
go to this line and replace this:
with this:
|
We're also exhibiting this issue! @hwillson |
The same issue for me :( P.S if you want to use lates version of |
This should be resolved in #1355 (published as Please note the comments in the mentioned PR, as this fix comes with some caveats that we cannot work around, unfortunately. There is a range of |
Aside from somehow being orders of magnitude faster than npm, it also makes it easier to install into arbitrary directories, which is especially useful for potentially getting around a very strange docker bug on Johanna's system. ## Notes * Upgraded apollo to get around apollographql/apollo-tooling#1329. * I tried using a tool to convert our `package-lock.json` to a `yarn.lock` but it didn't work, so I just built our `yarn.lock` directly from the `package.json`. This has resulted in some intermediate dependencies being different, which ultimately required me to upgrade a few packages. * One such package was `@testing-library/react`, which uncovered #707 (which we will deal with separately).
Aside from somehow being orders of magnitude faster than npm, it also makes it easier to install into arbitrary directories, which is especially useful for potentially getting around a very strange docker bug on Johanna's system. ## Notes * Upgraded apollo to get around apollographql/apollo-tooling#1329. * I tried using a tool to convert our `package-lock.json` to a `yarn.lock` but it didn't work, so I just built our `yarn.lock` directly from the `package.json`. This has resulted in some intermediate dependencies being different, which ultimately required me to upgrade a few packages. * One such package was `@testing-library/react`, which uncovered #707 (which we will deal with separately).
Trying to generate typescript typings with the command:
npx apollo client:codegen --includes='./src/**/*.tsx' --addTypename --target=typescript --globalTypesFile='src/typings/globalSchemaTypes.d.ts'
This works fine with apollo@2.12.2 and below but breaks from version 2.12.3 to the current release
the error I get is kinda cryptic:
another interesting detail: if I don't have apollo installed and run the command above it will work fine, but using the latest release (npx will download it on the fly)
The text was updated successfully, but these errors were encountered: