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

@drpgroup/crunch

v0.2.0

Published

Bundler for use with React & Laravel

Downloads

9

Readme

@drpgroup/crunch

Opinionated batteries-included webpack-powered bundler for our Laravel + React projects

Usage

npm install @drpgroup/crunch
npx crunch build
npx crunch dev

crunch build

Options

-e, --entry

Default: "./resources/js/app.js"

The entrypoint for the application. This currently only supports a singular entrypoint. WIP.

--noHash

Supplying this option will disable the automatic filename hashing. There isn't really a good reason to turn this on unless you want to control the hashing yourself via a custom system.

-o, --outDir

Default: "./public/dist"

The directory to place all resulting built assets into. This will include JS, CSS, images and any other statically built assets. This should be a directory that is statically-serving these resources.

This probably won't need to be changed unless you wish to place your built assets elsewhere.

-p, --publicPath

Default: "/dist/"

The path to use as the content public path base for all static assets. This is closely related to the outDir option and will be the relative folder path prefixed to any statically loaded assets.

As a general rule of thumb, this will only need to change if outDir changes.

-m, --manifestPath

Default: "./storage/app/crunch-manifest.json"

Where the crunch manifest file should be saved (including its filename).

There is no reason for this to change unless you wish to save it elsewhere, however the Laravel package config will also need to change to point to the custom filepath.