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

lazyasfk

v1.2.1

Published

Extremely simple lazy properties for Javascript

Downloads

13

Readme

Really simple and dependency-free lazy properties for Javascript

const lazy = require('lazyasfk')
const lazyAsync = require('lazyasfk/async')

const property = lazy(() => 'how could I be more lazy?')

console.log(property.isPresent())   // > false
console.log(property.get())         // > how could I be more lazy?
console.log(property.isPresent())   // > true

property.forget()
console.log(property.isPresent())   // > false
property.forceCompute()
console.log(property.isPresent())   // > true

// Also async

const expensiveAndTimeConsumingHttpRequestOrSomethingIdk = async () => 'foobar'

const lazyProperty = lazyAsync(expensiveAndTimeConsumingHttpRequestOrSomethingIdk)
console.log(lazyProperty.isPresent())   // > false
console.log(lazyProperty.get())         // > obviously not foobar
console.log(lazyProperty.isPresent())   // > true

lazyProperty.forget()
console.log(lazyProperty.isPresent())   // > false
lazyProperty.forceCompute()
console.log(lazyProperty.isPresent())   // > true

// Also works with params

// NOTE THAT THIS IS NOT MEMOIZATION!!!!!!!!!!!!!!!!!!!!!!!!
// THE PARAMS ARE USED ONLY FOR THE EVALUATION WHEN THE VALUE IS NOT PRESENT
// CHANGING THE PARAMS OF A PRESENT PROPERTY WILL NOT CHANGE THE OUTPUT

const withParams = lazy((a, b) => a + b) // Works with lazyAsync too
console.log(withParams.get(77, 33)) // > 100

The function names are pretty self-explanatory, I don't need I'll need to write function references for this.