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

macrocosm

v0.1.0

Published

a cosmic approach to object templating macros with proxy majik

Downloads

2

Readme

macrocosm

Template Javascript Objects in a way that allows incremental change between representational domains.

Example Usage: templating a planet

our target domain is that of cosmic objects rendered on the canvas of astronomical spacetime, we want to create a few planets using a format that is only concerned with properties relevant to planets, converting to the former.


import {macrocosm} from 'macrocosm'

let planetarium = macrocosm((macro, derive)=>({
    land: macro.land,
    size:'big',
    shape: "round",
    temperature: derive(
        (distance, atmosphere)=>{
            return atmosphere / distance // the thinner the atmosphere and further away the colder it gets
        }, 
        macro.distance, //depends on
        macro.atmosphere
    )
}))

let technoplanet = planetarium.convert({
    land:"silicon",  
    distance:10,
    atmosphere: 2
})

expect(technoplanet).toEqual({
    land:'silicon',
    size:'big',
    shape: 'round',
    temperature: 0.2
})

Isn't that just executing the function?

That is what it looks like, but macrocosm abstracts some magic to enable some extra features. 'macro' here is not the object passed to convert.

Updates:

It is possible to create updates to existing templates, so that it is possible to only adjust the affected areas of a system when the description changes

let up = planetarium.update({
    land:"Ice",
    atmosphere:5    
})

expect(up).toEqual({
    land:"Ice",
    temperature:0.5
})

see how the size and shape are unaffected. This makes this tool useful for driving updates to views, which derive from models in this way.

The Magic

internally macrocosm creates a gambit, a proxied object where properties gotten are not values but blanks to fill in later. By trapping get we are able to detect exactly what has been referred to and everything else can be ignored.

Testing

npm test

ES6 only Apache-2.0 Lisence Contributions Welcome