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

proact

v1.0.4

Published

Opinionated universal/Electron React+Redux application boilerplate and library, etc.

Downloads

27

Readme

proact

This is an experiment to create a single source of truth to bootstrap, develop, package, and distribute universal and Electron React/Redux apps.

proact is a framework that attempts to make it easy to bootstrap an application, but also to make your application code ultimately more readable, maintanable, and production-ready.

Some view frameworks like proact as evil. The arguments are legitimate, but I grew sick of each of my applications having slightly different, slightly incompatible copies of boilerplate. My feeling is that by restricting applications to a subset of common dependencies and patterns, complexity over many applications can be reduced.

Components

  • API server - done.
  • babel config - done.
  • eslint config - done (separate repo).
  • Install instructions. TODO
  • Upgrade instructions. TODO
  • Universal server. TODO
  • API Server documentation. TODO
  • Fileserver / proxy. TODO
  • Pluggable API and server. TODO

Install

Unfortunately babel plugins, webpack + plugins, and other dependencies (which?) must be installed to the project root:

(
  export PKG=proact;
  npm info "$PKG" peerDependencies --json | command sed 's/[\{\},]//g ; s/: /@/g' | xargs npm install --save-dev "$PKG"
)

webpack and babel really make a lot of assumptions about where plugins are residing, and for the most part assume that everything is under the project root.

License

Copyright 2016, Swift Nav, All Rights Reserved.

MIT license.