-
Notifications
You must be signed in to change notification settings - Fork 470
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
Cannot use with React Native / Typescript #574
Comments
There are actually a couple of "solutions" and it is possible to use with react-native and typescript (I am doing so). The best "solution" to date is: DefinitelyTyped/DefinitelyTyped#15960 (comment) |
imo the best solution is for runtime dependencies to never depend on |
@alloy they are dev dependencies: https://github.com/apollographql/apollo-cli/blob/master/package.json#L46 |
How can that be then? Dev dependencies don’t get pulled in when adding a runtime dependency to your package, no? From @epeli’s illustration it does look like the |
My guess would be some weird lerna stuff. |
Here's the package.json from my project's https://gist.github.com/epeli/907fa4eaefa0f63d7f418e8506d7f625 It does seem to have some extra deps on it? I'm using yarn 1.7.0 if it matters. |
The
apollo
module brings in the@types/node
module as a transitive dependency which is an issue with React Native typings (@types/react-native
) because they have conflicting type definitions:DefinitelyTyped/DefinitelyTyped#16825
I know this is issue is with
@types/react-native
and/or@types/node
but that's a long standing issue with no solution in sight so I'm wondering if it would be possible to get rid of the dependency from apollo's side.The dependencies which brings it in are as follows:
The text was updated successfully, but these errors were encountered: