npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

property-ttl

v1.0.0

Published

null out a property after ttl if it has not been accessed.

Downloads

124

Readme

property-ttl

null out a property after ttl if it has not been accessed.

if you have a case where something makes large data objects but you can't or don't want to hold them all in memory all the time. This allows you to null out those propertys if they are not being used.

var cleanup = require('property-ttl')

var registry = {
  getData:function(){
    if(!data) this.data = generateOodlesOfData()
    return this.data
  },
  data:null
}

// every 2000 ms of inactivity clear this property out.
cleanup(registry,'data',2000)

doActionWithData(registry.getData())

// `registry.data === null` === false
setTimeout(function(){
  // `registry.data === null` === true
},2010)

After 2000 ms the property is nulled out agian freeing up that memory for handling other kinds of server requests. If the peoperty was accessed every 1500 ms it would never be cleared because the ttl will keep extending on each access.

api

  • var cleanup = require('process-ttl')

  • cleanup(object, property, ttl, ongc)

    • object, the object that owns the property
    • property, the property name you want to manage. it need not be defined.
    • ttl, the time in ms you want an inactive property to hang around.
    • ongc(timeLived), OPTIONAL the ongc callback fires each time a property is gced.
  • cleanup.defaultValue === null

    • this property changes the module default value for cleared peoperties, default null