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

puttputt

v0.3.1

Published

a simple react component generator

Downloads

6

Readme

🚗 puttputt

a simple react component generator

✨ features

  • 💰 JS and TS ready-- renders TypeScript components if it detects any TS configs in root
  • 👉 next-gen es6
  • 👀 as-unopinionated-as-possible template code
  • 📝 generates tests (jest/enzyme) if necessary
  • 😈 redux-ready

🔮 usage

$ yarn add --dev puttputt

include a script in your package.json

scripts: {
  "generate": "puttputt"
}

✔️ prerequisites

by default, puttputt looks for an app source directory and will fail if it can't don't exist. this is a pitfall of plop not having built-in path logic.

for now, it looks for one of the following common dirs:

  • src/
  • client/
  • src/client

🔥 redux

redux generators are visible when your project is using redux (i.e. if redux is listed in your dependencies)

puttputt will generate specific templates if your app is using any of the following:

  • redux-saga
  • immutable

for redux components (actions/reducers), puttputt looks for the following directories:

  • src/
  • common/
  • src/common

🙌 shoutouts


init'd with golf ⛳️