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

poochie

v0.3.4

Published

Reactive frontend library

Downloads

4

Readme

Poochie

Build Status npm version Test Coverage

Poochie is one outrageous microframework.

Examples

[Poochie - TodoMVC] (https://github.com/garious/poochie-todomvc)

[More Examples] (https://github.com/garious/poochie-examples)

Why Poochie

I failed to find a web framework that allowed me to write a web app with the following properties:

  • The application description should be a single data-driven, declarative expression.
  • It should be possible to incrementally add dynamic behavior and maintain 100% line and branch coverage.
  • It should be possible to introduce components without affecting the existing behavior.

Poochie vs Mercury

Poochie and Mercury are similar in scope. Both provide libraries and programming techniques for defining testable, dynamic components in JavaScript. Some differences:

  • Poochie does not use virtual-dom
  • Poochie is compact, it's 1.8kb min.gzip.js, that's 5 times smaller than Mercury.
  • Poochie is lean, it's an afternoon's read, under 500 LoC.

Poochie chooses a slightly different abstraction than Mercury. Both implement the concept of observable variables that represent the application's dynamic behavior. But with Mercury, one keeps the app's state machine separate from the application. The application is then rendered from snapshots of that state, and then the DOM is diff'ed against the previous rendering to determine what changed. With Poochie, the virtual DOM is aware of observables. When the virtual DOM is rendered, the renderer detects the presence of observables, and sets up handlers that modify the DOM directly. No diffs needed.

Inspirations

  • Yoink
  • Mercury.js
  • Bacon.js
  • Fran
  • RxJS

Development

To download this package's dependencies:

$ npm install

To lint the code and run the unit tests:

$ npm test