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

universal-tree

v0.0.2

Published

Tiny wrapper around Baobab for an OOTB universal state tree

Downloads

8

Readme

universal-tree

NOTE: This is a WIP and not production ready yet

Tiny wrapper around Baobab for an OOTB universal state tree.

Example

Create your universal tree

const tree = require('universal-tree')

const state = module.exports = tree({
  colors: ['yellow', 'purple'],
  name: 'Glorious colors'
})

Import and just use it on the client

const state = require('./state')

state.on('update', () => render())

And import and just use it on the server

const state = require('./state')

app.locals.state = state

app.get('/article', (req, res) => {
  Article.find((err, article) => {

    // IMPORTANT: Make sure to only update your state all at once, right before rendering
    state.set({ title: article.title })
    res.render('article')
  })
})

Wait, WAT? Isn't that going to leak state across requests?

Here in lies the big exprimental gamble. We're clearing the state tree out on every event loop tick when used on the server. Since Node's HTTP servers don't handle requests synchronously, we're hoping that's enough to ensure nothing weird happens. We're also turning off Baobab's persistence, immutability, and all that other client-side-useful stuff in hopes it's enough to make performance not dramatically suffer with this approach.

Caveats

  • Must use only use JSON primative data in tree for clone perf
  • Only update your state all at once, right before rendering

Contributing

Please fork the project and submit a pull request with tests. Install node modules npm install and run tests with npm test.

License

MIT