RMD006 — Timer still running after unmount

A setInterval or setTimeout outlived its component, so it will fire into something that no longer exists.

Use @interval / @timeout for a clock that starts at mount, or the Timeout and Interval hooks for one the component starts itself:

private t = this.use(Timeout, () => ({ run: this.done }));
// this.t.start(ms), and this.t.stop() to end it early

Both clear themselves on teardown, so there is no id to keep.

Next

• All diagnostics — every code the framework can report.
• Checking your app — the faults proved from the source, before anything runs.