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

webpack-exposer

v0.0.3

Published

Expose webpack internals objects

Readme

webpack-exposer

This is a simple module to expose internal __webpack_<insert name here>__ functions.

Works with webpack >= 2, best suited with NamedModulesPlugin

Explaination

Each webpack module is wrapped with this higher-level function scope:

(function(module, exports, __webpack_require__) {
  var moduleA = __webpack_require__(<name or id>)
  var moduleB = __webpack_require__(<name or id>)
  ...
})

__webpack_require__ is global until an unknown time later. This little hack attempts to recover this behavior by exposing __webpack_require__ using arguments object and the module system:

(function(module, exports, __webpack_require__) {
  (function (module, exports, wr) {
    ...
  })(arguments[0], arguments[1], arguments[2])
})

Which the arguments should subsitute equivalently. Then __webpack_require__ will be global once again, some other objects are also exposed, so there are many rooms for hacking, for example dynamic (external) module loading or module hooking.

I cannot just unwrap this function because I observed only one argument will be available. I don't know the exact reason for this.

Usage

Just import or require this file/module in your index/main file:

import 'webpack-exposer'

// equivalently
require('webpack-exposer')

If __webpack_require__ is correctly supplied, window.__webpack_require__ and window.require (and a big list of other things) will be available!

Ten cents

Add NamedModulesPlugin to your webpack setup to not get an obscured integer ID, for the sake of easy hacking! This even works for non-HMR/development environment and the result set in __webpack_modules__ are drastically different!

const { NamedModulesPlugin } = require('webpack')

module.exports = {
  ...
  plugins: [
    ...
    new NamedModulesPlugin()
  ]
}