timestore | Multiple timers manager , especially good for games | Game Engine library

Specifically to your code, it seems that you are always setting your localstorage value. You would have to check if the value from the local storage exists before you populate it. This is achieved by using the getItem method in the WebStorage specification, which explicitly returns null if the item does not exist. As per the specs, if the given key does not exist in the list associated with the object then this method must return null.

I have made the use of session storage functionality which is similar to local storage- the difference being that session storage life cycle is that of a session in a browser. The value is lost as soon as you close the browser. I have used the getitem, setitem and remvoveitem methods of session storage to achieve the functionality. Hope this helps.

I have included below a code snippet which will grab and parse JSON from the link you provided.

The answer above is close but there are some things to consider. The query you are running is basically:

You can set the default value when you start the timer - see my example below. You might want to adjust the functionality of Start button accordingly, as it also calls the start() method of the timer. Please note i used different key for your localStorage (just in case you already have a set value in your browser) and i store only seconds which gets incremented everytime the event secondsUpdated is fired. There is no need for your own setInterval, as you can use the interval of the timer fired with the above mentioned event.

You can use the 'take' function #. E.g.

Looking at your use case I would suggest to modify your approach to the problem. Obviously you're creating items with an "expiry date" (or something similar, I'll be using the term "expired" in the following). The expiry is 24 hours from the time where the item was created.

I would not save the value for timeLeft to the DB, but rather recalculate it dynamically upon querying. (1) It's redundant, as it can be calculated from the current time and the time value, as far as I understood your question, (2) you would have to update the timeleft property continuously which seems awkward.

You can make use of Mongoose's virtuals.

Changes to the Schema to make sure, that the virtuals are returned when creating objects:

You can use moment diff method.

Here a working example: