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

collux

v1.0.4

Published

flux, redux, collar.js, architecture

Downloads

6

Readme

Collux

Build Status

Another Redux framework, with architecture, data flow visualization, and much more.

Collar.js + Redux = Collux

Check out this 3 minutes video: https://www.youtube.com/watch?v=Uy_RZL8jkzQ


Why another framework?

High quality software requires every developer has the same understanding of not only the code but also the architecture. However, software is not easy to build, things goes complex when software becomes big, it is very hard to keep every one in the team to get the same level of understanding. That's why there are different architectures and corresponding frameworks to help the team to build the understanding.

Flux architecture builds a unidirectional data flow. Redux architecture manages the state of your application. But using them doesn't means that your software will definitely become easier to understand. The ultimate reason for that is your architecture, data flow, business logic are implicitly embedded into your code, (and related documents, which usually has a delay to become up-to-date). Developers need to read the code to reconstruct the architecture, the data flow, and the business logic.

Collar.js (and collar dev tool) is a small javascript library to help you reconstruct your architecture, data flow and the business logic, so that your team will never get lost no matter how large your software goes. So why not implement Redux / Flux with collar.js? You use your usual way to develop your application with Redux- and Flux-like api, and keep the architecture, data flow, and business logic updated when you modify the code. You will never lost again in your code :D.

Besides, you can benefit a lot of cool debug / dev features from the cool collar dev tool. Time travel? You don't need a special Redux dev tool to do that. Collar dev tool supports it by nature, and you can do much more than just time travel, for example, the live testing.

Check out this video: how to build a counter application with collux

https://www.youtube.com/watch?v=U49308jICzY


Developer Guide

You can get the source code of collux from github repo: collux

To build it

npm install
npm run build

To create a web module:

// for development
export NODE_ENV=dev && npm run build && npm run webpack
// for production
export NODE_ENV=production && npm run build && npm run webpack

License

MIT