Miss-understood 'options' part about webpack HOT 3 CLOSED

The --options part either takes a json file .json or a node.js module .js.

If you do it with a .json file only options that are valid json are supported...

For options which include invalid json, i.e. RegExps or Functions you have to use a .js file:

module.exports = {
  // options
};

It's required like any other module in node.js so it may contain any code as long it exports an options object.

The best solution for blending a lodash library, which is already loaded in the browser, into webpack is to provide a web replacement.

_ = require 'lodash'

It loads the lodash library from node_modules if running in node.js.

You can provide a simple module which is loaded in the webpack build:

module.exports = window.lodash;

and save it under .../web_modules/lodash.js.

Requiring lodash will that load this module, which exports the lodash lib already loaded.

Another, less pretty, option is the write: var _ = this._ || require.valueOf()('lodash').

The require.valueOf() will be ignored by webpack, but work in node.js. ;)

from webpack.

Is this solved? Can I close it?

from webpack.

Oh, sure, thank you!

from webpack.