当webpack处理你的应用程序时，它会递归构建一个依赖图（包含了你的应用程序所需要每个模块），然后把这些模块打包到少数几个budle文件中（通常是只有一个，会被浏览器加载，根据项目情况而定）。
这是令人难以置信的配置，但开始前，你只需要明白四个核心概念：entry、output、loaders、和plugins。
配置对象选项
webpack.config.js
const path = require('path'); module.exports = { // click on the name of the option to get to the detailed documentation // click on the items with arrows to show more examples / advanced options entry: ./app/entry, // string | object | array // here the application starts executing // and webpack starts bundling output: { // options related to how webpack emits results path: path.resolve(__dirname, dist), // string // the target directory for all output files // must be an absolute path (use the node.js path module) filename: bundle.js?1.1.11, // string // the filename template for entry chunks publicpath: /assets/, // string // the url to the output directory resolved relative to the html page library: mylibrary, // string, // the name of the exported library librarytarget: umd, // universal module definition // the type of the exported library /* advanced output configuration (click to show) */ }, module: { // configuration regarding modules rules: [ // rules for modules (configure loaders, parser options, etc.) { test: /\.jsx?$/, include: [ path.resolve(__dirname, app) ], exclude: [ path.resolve(__dirname, app/demo-files) ], // these are matching conditions, each accepting a regular expression or string // test and include have the same behavior, both must be matched // exclude must not be matched (takes preferrence over test and include) // best practices: // - use regexp only in test and for filename matching // - use arrays of absolute paths in include and exclude // - try to avoid exclude and prefer include issuer: { test, include, exclude }, // conditions for the issuer (the origin of the import) enforce: pre, enforce: post, // flags to apply these rules, even if they are overridden (advanced option) loader: babel-loader, // the loader which should be applied, it'll be resolved relative to the context // -loader suffix is no longer optional in webpack2 for clarity reasons // see webpack 1 upgrade guide options: { presets: [es2015] }, // options for the loader }, { test: \.html$, use: [ // apply multiple loaders and options htmllint-loader, { loader: html-loader, options: { /* ... */ } } ] }, { oneof: [ /* rules */ ] }, // only use one of these nested rules { rules: [ /* rules */ ] }, // use all of these nested rules (combine with conditions to be useful) { resource: { and: [ /* conditions */ ] } }, // matches only if all conditions are matched { resource: { or: [ /* conditions */ ] } }, { resource: [ /* conditions */ ] }, // matches if any condition is matched (default for arrays) { resource: { not: /* condition */ } } // matches if the condition is not matched ], /* advanced module configuration (click to show) */ }, resolve: { // options for resolving module requests // (does not apply to resolving to loaders) modules: [ node_modules, path.resolve(__dirname, app) ], // directories where to look for modules extensions: [.js?1.1.11, .json, .jsx, .css?1.1.11], // extensions that are used alias: { // a list of module name aliases module: new-module, // alias module -> new-module and module/path/file -> new-module/path/file only-module$: new-module, // alias only-module -> new-module, but not module/path/file -> new-module/path/file module: path.resolve(__dirname, app/third/module.js?1.1.11), // alias module -> ./app/third/module.js?1.1.11 and module/file results in error // modules aliases are imported relative to the current context }, /* alternative alias syntax (click to show) */ /* advanced resolve configuration (click to show) */ }, performance: { hints: warning, // enum maxassetsize: 200000, // int (in bytes), maxentrypointsize: 400000, // int (in bytes) assetfilter: function(assetfilename) { // function predicate that provides asset filenames return assetfilename.endswith('.css') || assetfilename.endswith('.js'); } }, devtool: source-map, // enum // enhance debugging by adding meta info for the browser devtools // source-map most detailed at the expense of build speed. context: __dirname, // string (absolute path!) // the home directory for webpack // the entry and module.rules.loader option // is resolved relative to this directory target: web, // enum // the environment in which the bundle should run // changes chunk loading behavior and available modules externals: [react, /^@angular\//], // don't follow/bundle these modules, but request them at runtime from the environment stats: errors-only, // lets you precisely control what bundle information gets displayed devserver: { proxy: { // proxy urls to backend development server '/api': 'http://localhost:3000' }, contentbase: path.join(__dirname, 'public'), // boolean | string | array, static file location compress: true, // enable gzip compression historyapifallback: true, // true for index.html upon 404, object for multiple paths hot: true, // hot module replacement. depends on hotmodulereplacementplugin https: false, // true for self-signed, object for cert authority noinfo: true, // only errors & warns on hot reload // ... }, plugins: [ // ... ], // list of additional plugins /* advanced configuration (click to show) */ }
本文档的目的是给这些概念提供一个高层次的大纲，同时提供链接给详细概念的指定用例。
entrywebpack会创建一个你所有应用程序的依赖图。这个依赖图的起始点就是已知的entry（入口）点。这个入口点告诉webpack从哪开始，并且根据已知依赖图进行打包。你可以把应用程序的入口点当作上下文根或启动你的应用程序的第一个文件。
在webpack配置对象的entry属性中定义入口点。简单示例如下：
module.exports = { entry: './path/to/my/entry/file.js' };
有几种方式声明entry属性：
1、单个entry语法
const config = { entry: './path/to/my/entry/file.js' }; module.exports = config;
2、对象语法
const config = { entry: { app: './src/app.js', vendors: './src/vendors.js' } };
3、多页面应用
const config = { entry: { pageone: './src/pageone/index.js', pagetwo: './src/pagetwo/index.js', pagethree: './src/pagethree/index.js' } };
output一旦你打包所有代码，你仍需要告诉webpack打包到哪里去。output属性会告诉webpack如何对待你的代码。
const path = require('path'); module.exports = { entry: './path/to/my/entry/file.js', output: { path: path.resolve(__dirname, 'dist'), filename: 'my-first-webpack.bundle.js' } };
以上这个例子，我们使用output.filename和output.path属性告诉webpack打包的文件名和路径
更多配置项
loaders这个配置项的目的是让webpack关注你项目的所有代码而非浏览器（这并不意味着它们会被打包到一起）。webpack把每一个文件（.css, .html, .scss, .jpg, etc.）作为一个模块。然而，webpack只知道javascript。
webpack中的loaders会转换这些文件到模块中，并添加到你的依赖图中。
在一个较高的水平，在你的webpack配置中有两个目的：
1、标识什么文件应该用一个确定的loader来转换。
2、转换后的文件可以被添加到你的依赖图中。
const path = require('path'); const config = { entry: './path/to/my/entry/file.js', output: { path: path.resolve(__dirname, 'dist'), filename: 'my-first-webpack.bundle.js' }, module: { rules: [ {test: /\.(js|jsx)$/, use: 'babel-loader'} ] } }; module.exports = config;
以上这个配置定义了一个rulues属性，用以给一个单独的模块，这个模块带有两个属性：test和use。这告诉webpack编译如下事情：
当使用require()或import语句时，路径中后缀名为.js或.jsx的文件，使用babel-loader来转换并打包。
更多配置项
plugins因为加载器只执行基于每个文件的转换，插件是最常用的（但不限于）优化行为，并且你可以自定义函数在你打包模块的编辑或块中（等等）。
该webpack插件系统极其强大，可定制。
为了使用一个插件，你只需要require()并添加到插件数组中。更多插件可通过选项自定义。由于你可以在一个配置中多次使用插件来达到不同的目的，因此你需要创建一个新的实例。
const htmlwebpackplugin = require('html-webpack-plugin'); //installed via npm const webpack = require('webpack'); //to access built-in plugins const path = require('path'); const config = { entry: './path/to/my/entry/file.js', output: { path: path.resolve(__dirname, 'dist'), filename: 'my-first-webpack.bundle.js' }, module: { rules: [ {test: /\.txt$/, use: 'raw-loader'} ] }, plugins: [ new webpack.optimize.uglifyjsplugin(), new htmlwebpackplugin({template: './src/index.html'}) ] }; module.exports = config;
webpack提供有许多开箱插件！可以从我们的插件列表中获得更多信息。
在webpack配置中使用插件是简单的，然而有许多用法值得进一步探讨。
更多配置项
简单示例var path = require('path'); var webpack = require('webpack'); var env = process.env.node_dev; var config = { entry: { consumer: './consumer/index.js', admin: './admin/index.js', // jquery: ['jquery'] }, output: { path: path.resolve(__dirname, 'dist'), publicpath: '/dist/', filename: '[name].bundle.js' }, module: { loaders: [ { test: /\.css$/, loader: 'style-loader!css-loader' }, { test: /\.less$/, loader: 'less-loader!style-loader!css-loader' }, { test: /\.sass$/, loader: 'sass-loader!style-loader!css-loader' }, { test: /\.(woff|woff2|eot|ttf|otf)$/i, loader: 'url-loader?limit=8192&name=[name].[ext]' }, { test: /\.(jpe?g|png|gif|svg)$/i, loader: 'url-loader?limit=8192&name=[name].[ext]' }, { test: /\.jsx?$/, loader: 'babel-loader', exclude: /node_modules/, include: __dirname, options: { presets: ['es2015', 'react'] }, }, { test: /\.tsx?$/, loader: 'ts-loader', exclude: /node_modules/, include: __dirname }, { test: /\.coffee$/, loader: 'coffee-loader', exclude: /node_modules/, include: __dirname } ] }, //devtool: 'source-map', //指定根路径 context: __dirname, //这里枚举的后缀名，在require时可以省略 resolve: { extensions: ['.js', '.jsx', '.json', '.ts', '.tsx', '.css'] }, plugins: [ // 这里声明的变量是全局的，可以在所有的js中使用，可以避免写一堆的require new webpack.provideplugin({ $: 'jquery', jquery: 'jquery', 'window.jquery': 'jquery', 'window.$': 'jquery', 'react': 'react', 'reactdom': 'react-dom' }), // new webpack.optimize.commonschunkplugin({ // // 与 entry 中的 jquery 对应 // name: 'jquery', // // 输出的公共资源名称 // filename: 'jquery.min.js', // // 对所有entry实行这个规则 // minchunks: infinity // }), // new webpack.noemitonerrorsplugin() ], //在html页面中使用script标签引入库，而不是打包到*.bundle.js文件中 externals: { jquery: 'jquery', react: 'react', 'react-dom' : 'reactdom' } }; //如果是生产环境，要最小化压缩js文件 if (env === 'production') { //打包时对js文件进行最小化压缩 config.plugins.push(new webpack.optimize.uglifyjsplugin({ mangle: { except: ['$super', '$', 'exports', 'require'] //以上变量‘$super’, ‘$’, ‘exports’ or ‘require’，不会被混淆 }, compress: { warnings: false } })); //消除压缩后的文件在界面引用时发出的警告 config.plugins.push(new webpack.defineplugin({ 'process.env': { node_env: json.stringify('production') } })); } module.exports = config;
以上就是webpack打包器的简单介绍的详细内容。