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

webpack-to-memory

v1.0.0

Published

Run a webpack build and get the resulting modules from memory.

Downloads

17

Readme

webpack-to-memory

Dependency Status devDependency Status Build Status Npm Version License Badges

A quick 'n dirty module to compile one or more bundles using webpack and load those compiled bundles as node modules -- all in memory!

Usage

This module exports a single function which takes a webpack compiler configured according to the webpack Node Node API (note: you can ignore the section on compiling to memory, this module takes care of that for you). The most important things to configure are the target ('node') and the libraryTarget ('commonjs2'). The exported function returns a Promise which resolves with an object mapping output filenames to compiled node modules.

const webpack = require('webpack');
const load = require('webpack-to-memory');

load(webpack({
  entry: 'index.js',
  target: 'node',
  output: {
    libraryTarget: 'commonjs2',
    filename: 'bar.js',
  },
  module: {
    loaders: [{
      test: /\.js$/,
      loaders: ['babel'],
    }],
  },
})).then(files => {
  // Now you can get the node modules.
  const bar = files['bar.js']; // `bar` now contains the `exports` object from `bar.js`
});

Caveats

All output is placed in an in-memory filesystem. Node doesn't read from this filesystem directly, so if you create multiple bundles that depend on each other your modules will fail to load (except in a few edge cases). If you have a setup such as this it is probably better to just compile out to the real filesystem ahead of time and require or import the modules as normal.

License

MIT