Apollo-angular: 'NodeJS' has no exported member 'Timeout'.

Created on 23 May 2019 · 13Comments · Source: kamilkisiela/apollo-angular

Hello, When i added Apollo to my project this error was showed.

ERROR in node_modules/@wry/context/lib/context.d.ts(6,84): error TS2694: Namespace 'NodeJS' has no exported member 'Timeout'.

i ｢wdm｣: Failed to compile.

Versions
2.6

in progress

Source

RmilaWeb

👀7

Most helpful comment

upgrading @types/node to the latest version did the trick

Andre153 on 29 May 2019

👍5 🚀1

All 13 comments

RmilaWeb on 23 May 2019

👍2

same issue here - it is with angular + apollo.

judithprays on 23 May 2019

👍1

same issue here - it is with angular + apollo.

Angular 7 ?

RmilaWeb on 24 May 2019

Yes

On May 23, 2019, at 5:24 PM, RmilaWeb notifications@github.com wrote:

same issue here - it is with angular + apollo.

Angular 7 ?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

judithprays on 24 May 2019

Also experiencing the same issue. Fresh angular project and ng add apollo-angular.

(A work around for now is just removing node_modules/@wry/context/lib/context.d.ts)

johnbjurulf on 24 May 2019

👍1

There's an open pull request on @wry here for those wanting to be notified when this is resolved:
https://github.com/benjamn/wryware/pull/5

heuperman on 26 May 2019

👍1

upgrading @types/node to the latest version did the trick

Andre153 on 29 May 2019

👍5 🚀1

That's related to apollo-cache-inmemory and not apollo-angular itself. I fixed it, but it's not merged and released yet, here's the ongoing pull request https://github.com/benjamn/wryware/pull/5 and the related issue https://github.com/benjamn/wryware/issues/4.

I'm going to close it so please follow https://github.com/benjamn/wryware/issues/4. I will notify all you guys once it's released :))

kamilkisiela on 29 May 2019

upgrading @types/node to the latest version did the trick

Working fine 👍

sreenivasarajiv on 30 May 2019

upgrading @types/node to the latest version did the trick

Working fine

xuxusheng on 30 May 2019

Yeah but it's just a workaround, not a fix.

kamilkisiela on 30 May 2019

Same here. It happened to be an issue with the version of the "@types/node"-dependency that was defined in my devDependencies. Upgrading it to the latest version (12.0.2) fixed it for me.