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 🙏

© 2026 – Pkg Stats / Ryan Hefner

generator-smild

v0.1.1

Published

An opinionated generator to build JavaScript projects

Readme

generator-smild NPM version

An opinionated generator to build JavaScript projects

Transitioning from code to running code is not always easy in JavaScript. Over the years this process has become simpler thanks to projects like browserify, Webpack and ParcelJS but still some configuration caveats must be addressed to have a fully functioning solution. This project aims to give you a simpler way to configure your application in an opinionated way that can be tested and built with a single command.

Installation

First, install Yeoman and generator-smild using npm (we assume you have pre-installed node.js).

npm install -g yo generator-smild

Then generate your project:

yo smild

A guided setup is shown where three different paths are available.

Bundle setup

Mainly for frontend applications, this setup runs ParcelJS with the proper Typescript config to package source files and assets of your app that can be distributed to your users.

Features

  • Typescript support built-in
  • All ParcelJS features: HMR, bundle splitting, source maps, etc
  • React-hot-loader support
  • Parcel static plugin: simply place all of your static assets under a static directory and it will be copied to the build folder

Commands

npm start

This starts Parcel in watch mode and spawns a dev server (default port 1234) to access your frontend.

npm run build

Used to build your app in production mode with minify turned on and files revisioning enabled.

Server setup

Use this setup for running a NodeJS server app.

Features

  • Typescript built-in support
  • Live reload using Nodemon
  • Source maps support

Commands

npm start

Your main file is ran with live reload enabled.

npm run build

Source files are transpiled with tsc and put in the build folder.

Lib setup

This setup transpiles your Typescript codebase making it available for publishing on NPM.

Commands

npm start

Launches Typescript compiler in watch mode.

npm run build

The same as the command above without watch.

Common configuration

Regardless of the project type some additional useful commands will be configured for testing and linking local packages. There are two test runners available: jest or mocha.

npm test

Executes the matching unit test using the selected test runner.

npm run test-watch

The same as the command above but using watch mode to re run the test on file changes.

npm run coverage

Executes the matching unit test producing a coverage report.

npm run link [package-name]

Alias for yalc add [package-name].

npm run rm-link [package-name]

Alias for yalc remove [package-name].

npm run push

Alias for yalc push.

For a detailed explanation of yalc usage please visit the project homepage.

Common questions

After a build configuration has been created, how can I change some parameters without a manual intervention?

Just re run the generator! You will be prompted with the old inputs given, change the one you need.

License

MIT © Mattia Franchetto