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

@cgamesplay/webpack-query

v0.0.0-alpha.1

Published

CLI for inspecting webpack bundles

Downloads

2

Readme

webpack-query

A CLI tool that allows you to ask questions about your webpack bundle.

Installation

  1. Install the software:
yarn add @cgamesplay/webpack-query
  1. Set up webpack to save the stats to a well-known location using something like stats-webpack-plugin. Make sure that source is included in the output stats.

  2. Monkey-patch node_modules/webpack/lib/Stats.js

if (showSource && module._source) {
    // Old version:
	// obj.source = module._source.source();
    // New version:
    const sourceAndMap = module._source.sourceAndMap();
    obj.source = sourceAndMap.source;
    obj.sourceMap = sourceAndMap.map;
}
  1. Add an alias to your package.json to make your life easier.
"scripts": {
    "wq": "webpack-query --file path/to/stats.json",
}

Usage

Once you have that alias set up, make sure to build your webpack bundle so that the stats file is available. Then you can use the alias you created to run queries.

webpack
yarn wq dump

Examples

Where is this module imported from?

$ yarn wq list-references ./example/src/module.js
example/src/index.js:1:import { sayHello } from "./module";

Operations

dump

Output the raw webpack stats file. Potentially useful for debugging.

find-module

Given a string, try to resolve it to a specific module and then output the resolved module's identifier.

list-references

List all places in where the named module is imported.