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

@ev1stensberg/strings-loader

v1.0.0

Published

A webpack loader that takes in a module string and console.logs its content.

Readme

strings-loader

A tiny webpack loader that takes in a module's source string and console.logs its content during the build, then passes the source through unchanged. Handy for debugging exactly what webpack hands your loaders for a given file.

Install

npm install --save-dev strings-loader

Usage

Add it to a rule in webpack.config.js. Because a loader logs whatever it receives, its position in the use array matters — loaders run right-to-left, so put strings-loader last to see the raw source, or earlier to see what a previous loader produced.

module.exports = {
  module: {
    rules: [
      {
        test: /\.js$/,
        exclude: /node_modules/,
        use: [
          // ...other loaders...
          {
            loader: 'strings-loader',
            options: {
              showResource: true, // prefix each log with the file path
              // maxLength: 500,   // optionally truncate long output
            },
          },
        ],
      },
    ],
  },
};

Run your build and the content of every matched module is printed to the terminal:

[strings-loader] /project/src/hello.js
export const greeting = 'Hello from the module string!';

export function greet(name) {
  return `${greeting} — ${name}`;
}

Options

| Option | Type | Default | Description | | -------------- | --------- | ------- | ------------------------------------------------------------------ | | showResource | boolean | true | Prefix the log with the module's file path. | | maxLength | number | — | Truncate the logged content to this many characters. The source is | | | | | never truncated — only the log output is. |

How it works

A webpack loader is just a function that receives the module source and returns it (optionally transformed). This one returns the source untouched and only emits a console.log as a side effect, so it's safe to drop anywhere in a loader chain.

Try the example

npm install
npm run example

License

MIT