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

@lab009/teide

v4.0.0-beta.1

Published

Toolkit for building redux/react applications

Downloads

11

Readme

@lab009/teide

Toolkit for building redux/react applications

Install

npm install --save @lab009/teide react react-dom

Core Ideals

  • Everything should be immutable
  • Everything should work easily and be simple to understand
  • Spend time building applications rather than wiring modules together

Implementation

  • Use ES6
  • Central store is completely immutable via Immutable.js
    • And PropTypes include Immutable.js types by default
  • Easy to understand objects instead of crazy functional composition
    • Before: createStore(combineReducers(reducers), {}, compose(applyMiddleware(middleware), devtools))
    • After: createStore({middleware: middleware, reducers: reducers, initialState: {}})
  • Bundle groups of middleware, enhancers, and reducers together as "plugins"
    • One line of code to add a router and etc. to your project
    • High quality ecosystem of modules guaranteed to work well with eachother
  • Namespaced/nested actions and reducers
    • todos.create as an action corresponds to a todos.create reducer and todos in the store
  • Default enhancers
    • redux-batched-subscribe
  • Default middleware
    • redux-thunk
    • devtools
  • Dead simple Component API
    • Use ES6 classes
    • Bring back sane behavior
      • Bind component functions scope to class (like old react)
    • Never write mapDispatchToProps or mapStateToProps

Documentation

Now, check out the documentation to get started!