setTimeout intercepted and requires Timer type variable to be assigned to

[jeserkin]

IMPORTANT: This repository's issues are reserved for feature requests and bug reports. Do not submit support requests here.

Steps to reproduce and a minimal demo of the problem

What steps should we try in your demo to see the problem?

1. Create class

import { Component, OnDestroy } from "@angular/core";

@Component({
  selector: 'sample',
  tempalte: '<div></div>'
})
class SampleComponent implements OnDestroy {
  private currentTimeout: number;

  public sampleMethodCall() {
    this.currentTimeout = setTimeout(() => {
      alert('working');
    }, 300);
  }

  ngOnDestroy(): any {
    return undefined;
  }
}

1. Save
2. Watch comiler consile livereload

Current behavior
On *.ts file change comiler in console shows following error
.component.ts(27,5): error TS2322: Type 'Timer' is not assignable to type 'number'.

Expected/desired behavior
Like in every setTimeout TypeScript tutorial on the web. Excpect it to return number type result, not Timer.

[mgechev]

Here's the first result when Googling the error you have, i.e.:

...
this.currentTimeout = window.setTimeout(() => {
  alert('working');
}, 300);
...

solves your problem.

[jeserkin]

Okay, but all examples on the internet don't need it to be specified. Is it only angular2-seed issue due to some typings override(priority)?

[ludohenin]

I think it is due to a core node.d.ts lib in typescript.

[nadavsinai]

@mgechev isn't adding window.XXXXXX breaks the possibility of running the app in server/worker based rendering scenario? I thought removing the node.js type definitions would help but unfortunately it doesn't seem to work, any other ideas?

[mgechev]

@nadavsinai yes, you're correct. Directly accessing window will prevent your application from running in Web Worker/Server.