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

babel-plugin-webpack-loaders-inline-exports

v0.4.0

Published

pick webpack-loaders exports as inline replace

Downloads

22

Readme

babel-plugin-webpack-loaders-inline-exports

Make webpack-loaders inline exports

Build Status NPM Dependencies License

webpack-loaders is cool, but it did some transforms from loader compiled result.

For each matched loader, they could transform as a commonjs module

module.exports = webpackBootstrap([
  function (module, exports, __webpack_require__){
    module.exports = __webpack_require__.p + 'xxsdfasdasd.txt';
  }
])

and we can just pick the webpackResult as inline exports

const txt = require('./some.txt');

will be

const txt = webpackBootstrap([
  function (module, exports, __webpack_require__){
    module.exports = __webpack_require__.p + 'xxsdfasdasd.txt';
  }
]);

And for some loader, they may exports with other dependences, but it will works well. in this plugin, webpackConfig will be overwrite by the special config below:

{
  entry: filename,
  output: {      
    libraryTarget: 'commonjs2',
  },
  externals: [      
    (context, subRequest, callback) => {
      if (subRequest !== filename) {
        callback(null, subRequest);
      } else {
          callback();
      }
    }
  ]
}

To make sure only process the target file which is matched by loader.

Options

all options same as webpack, and we can assign a config by the webpack config file

{
  "plugins": [
    [
       "babel-plugin-webpack-loaders-inline-exports",
       {
          "configFile": "./webpack.config.js"
       }
    ]
  ]
}

special options in babel option for this plugin will merge into webpack config.

For ava user, add set env var $PWD is needed;

{
  "plugins": [
    [
       "babel-plugin-webpack-loaders-inline-exports",
       {
          "configFile": "${PWD}/webpack.config.js"
       }
    ]
  ]
}

Warning

  • Please use this only in Node.
  • And for css-loader, should use with extract-text-webpack-plugin and don't use with style-loader
  • BABEL_DISABLE_CACHE=1 may used