setInterval is not a good way to track time

[Equbuxu]

The setInterval function can "drift" over time. This is especially noticeable if you switch to another tab while the stopwatch is running. In this case chrome increases the interval to save cpu resources which makes the stopwatch tick slower. The difference can get really severe, for me the stopwatch ticks about 3 times slower when kept in background.

[1995YogeshSharma]

Do you have any suggestion for alternate approach?

[Equbuxu]

Do you have any suggestion for alternate approach?

You could store the time when the stopwatch was started and use it to calculate the passed time in the setInterval callback. In other words, right now you increment a counter roughly once per second, and I suggest instead recalculating the current time via (currentTime - startTime), also roughly once per second.