You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When setting the moduleResolution on tsconfig to nodenext causes Apollo Elements not to work anymore.
The type inference is totally broken and the query.data field defaults to unknown.
This is caused by the following problem:
Interface 'ApolloQueryControllerOptions<D, V>' cannot simultaneously extend types 'ApolloControllerOptions<D, V>' and 'Partial<WatchQueryOptions<Variables<D, V>, Data<D>>>'. Named property 'context' of types 'ApolloControllerOptions<D, V>' and 'Partial<WatchQueryOptions<Variables<D, V>, Data<D>>>' are not identical.ts(2320)
Expected Behavior
It should also work fine in nodenext
Version
2.1.2
The text was updated successfully, but these errors were encountered:
#278 or something like it might one day fix this. Unfortunately it does appear that there may have been breaking changes to apollo's rather gnarly internal types in a minor release, or at least that ts 4.9 broke the existing types. If you'd like to take a stab at this i'd be happy to review
Package
@apollo-elements/core
Description
When setting the
moduleResolution
on tsconfig tonodenext
causes Apollo Elements not to work anymore.The type inference is totally broken and the
query.data
field defaults tounknown
.This is caused by the following problem:
Interface 'ApolloQueryControllerOptions<D, V>' cannot simultaneously extend types 'ApolloControllerOptions<D, V>' and 'Partial<WatchQueryOptions<Variables<D, V>, Data<D>>>'. Named property 'context' of types 'ApolloControllerOptions<D, V>' and 'Partial<WatchQueryOptions<Variables<D, V>, Data<D>>>' are not identical.ts(2320)
Expected Behavior
It should also work fine in
nodenext
Version
2.1.2
The text was updated successfully, but these errors were encountered: