project cluttering about webpack HOT 4 CLOSED

It is possible to compile with only globally installed webpack and a webpackOptions.js file with webpack --options webpackOptions.js entry.js bundle.js. The webpack binary just looks for a locally installed webpack to support different versions in different projects. Additional loaders are installed locally (like grunt plugins).

I think that Aptana Studio blocks while it's indexing files is a issue of Aptana Studio. (They should do it asynchrous 😄 )

I hope for webpack support in Scripted once it's more mature. They're already using enhanced-resolve, the library webpack uses for resolving.

from webpack.

webpack --options webpackOptions.js entry.js bundle.js

Still seems an awful lot to write. How about and options file default and entry and bundle name declaration in that file?

Scripted looks great! They are the first I see doing good inferencing.

from webpack.

Like grunt...

I'll consider this for 0.9...

from webpack.

webpack now uses webpack.config.js in the current directory. Command line arguments will override/extend the settings.

So you can just run webpack.

I removed all loaders from the webpack dependencies, so webpack is now just the compiler. You have to install all required loaders locally.

from webpack.