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

abstractify

v0.0.1

Published

A WIP boilerplate

Downloads

4

Readme

A WIP boilerplate project

  • [x] I'm a big believer in the monorepo -> lerna to manage sub-packages

  • [ ] Version control for packages is important -> sematic-release

  • [x] For version management, everyone should be using asdf -> .tool-versions to manage file

  • [ ] yarn is a better package manager -> yarn.lock

  • [x] There should be community github folder -> .github folder (patterned from react-boilerplate)

  • [x] Editors configuration provided -> .editorconfig

  • [x] git config -> .gitignore and .gitattribute

  • [ ] docs are important, codes are not docs -> docs folder documents everything

  • [ ] try out react-storybook

  • [ ] There should always be a sane defaults option -> create-react-app style

  • [ ] Once broken, there should be options -> yeoman

  • [ ] While working, you should be able to add new files of a certain type easily -> plop

  • [ ] static typing is extremely useful -> flowtype

  • [ ] JS build tools are helpful -> Gulp (Broccoli looks interesting)

  • [ ] Codesplitting and tree shaking make sense -> Webpack 2

  • [ ] Webpack is necessary, but config is tedious -> webpack-blocks

  • [ ] polyfill should only be done as needed -> polyfill.io a la react-universally

  • [ ] Universal code is needed as an option, less meaningless context switching and rewriting of code

  • [ ] Async is everywhere and there can be multiple outputs -> Observables

  • [ ] Functional programming is more declarative (aka easier to implement) -> use Rambda/RxJS

  • [ ] CSS-in-JS is the future for component-based systems (which are great b/c fractal)

    • styled-components
    • styletron/fela/este
  • [ ] Testing is needed -> Jest w/ enzyme is the way to go

  • [ ] CI testing makes sense and should be done -> circle CI

  • [ ] Non-nested file structures are intimidating -> follow react-boilerplate on dot-file hiding

  • [ ] Docker is composition at OS-level (not a silver bullet, but is nice)

  • [ ] Firebase makes sense as an option

  • [ ] Phoenix makes sense as an option

  • [ ] GraphQL needs to be an option (appollo)

  • [ ] zeit now is handy, set up out of box (with Docker)