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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@fees/builds

v1.0.63

Published

### WHY

Downloads

431

Readme

FEE Building Devops

WHY

  • vue-cli too complex and less supported

  • webpack too complex and just wanna start coding

  • create-react-app not transparent to understand

  • All I want to it to be hackable, do what ever I wanna

Features:

  • Simple, Convention, Best Practice, Configurable, Transparent

  • Both ES6 and Typescript are supported

  • Both React and Vue are supported

  • Jest Easy

  • Linter for scripts and styles

  • Auto formatter

  • git hooks

Development configuration

  • prettier, eslint, stylelint, browserslist integrated with package.json

  • tsconfig.json, tslint.json placed in the root

  • .babelrc.js and .postcssrc.js is optional

  • .babelrc.js is required when jest.config.js

Developing

SET UP

yarn add --dev @fees/builds

then you have a command fees-cli

CODE STRUCTURE

All source code placed in src directory

All tests placed in tests

A index.(jsx?|tsx?) in the src as entry file

SERVE FOR DEVELOPMENT

Start a dev server

fees-cli serve --host 0.0.0.0 --port 1995 --pwa --open

BUILD FOR PRODUCTION

Bundle all sources to a publicPath

fees-cli build --public-path /