Lou*_*is 5 javascript chunking chunks reactjs webpack
这一天我一直在努力解决这个烦人的问题,但我敢肯定,这是一个简单的问题。我试图将我的bundle.js分成多个块以优化网站加载时间。
这是我的webpack.config文件:
module.exports = {
devServer: {
historyApiFallback: true
},
entry: {
index: ["./src/index.js"],
vendor: [
"react",
"react-dom",
"react-redux",
"react-router",
"react-router-dom",
"redux"
]
},
output: {
path: __dirname + '/public/views',
filename: "[name].js",
publicPath: "/views/"
},
module: {
loaders: [
{
test: /\.js$/,
loader: "babel-loader",
exclude: [/node_modules/, /pdfmake.js$/]
},
{
test: /\.json$/,
loader: "json-loader"
}
]
},
plugins: [
new webpack.optimize.CommonsChunkPlugin({
name: "vendor",
filename: "vendor.js",
minChunks: Infinity
}),
new webpack.optimize.CommonsChunkPlugin({
name: "meta",
chunks: ["vendor"],
filename: "meta.js"
}),
new webpack.NamedModulesPlugin(),
new HtmlWebpackPlugin({
title: "Deals",
filename: __dirname + "/views/index.ejs",
template: __dirname + "/views/template.ejs",
inject: false
}),
new PreloadWebpackPlugin({
rel: "preload",
as: "script",
include: "all"
}),
new webpack.optimize.OccurrenceOrderPlugin(),
]
};
Run Code Online (Sandbox Code Playgroud)
这是我的简化index.ejs,通过运行 webpack 代码创建的文件,结果来自 template.ejs :
<!DOCTYPE html>
<html lang="en">
<head>
<link href="/pace.css" rel="stylesheet" />
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=yes">
<meta charset="utf-8">
<link rel="stylesheet" href="/style.css">
<link rel="canonical" href="http://verygoodprof.fr/" />
<link rel="preload" as="script" href="/views/index.js">
<link rel="preload" as="script" href="/views/vendor.js">
<link rel="preload" as="script" href="/views/meta.js">
</head>
<body>
<noscript>
<a href="http://enable-javascript.com/">Javascript must me enabled to use this site.</a>
</noscript>
<div class="text-center root" id="root">
</div>
</body>
</html>
Run Code Online (Sandbox Code Playgroud)
在这里,我看到我已经根据需要动态编写了预加载的块,并且这些块位于运行 webpack 代码后创建的正确文件夹中。
这是我的index.js文件(React),声明为 webpack.config 文件中的索引条目
ReactDOM.render(
<Provider store={createStoreWithMiddleware(reducers)}>
<AppInit>
<BrowserRouter>
<div style={{ height: "100%" }}>
<ProfRegisteringModal />
<Switch>
{/* <Route path="/inscription/:user" component={Registering} />
<Route path="/inscription" component={Registering} />
<Route path="/connexion" component={SigningIn} />
<Route path="/equipe" component={TeamPres} />
<Route path="/" component={AppContainer} /> */}
<Route
path="/inscription/:user"
getComponent={(location, callback) => {
require.ensure(
[],
function(require) {
callback(
null,
require("./components/registering/registering_landing_page.js")
);
},
"registerChunk"
);
}}
/>
<Route
path="/inscription"
getComponent={(location, callback) => {
require.ensure(
[],
function(require) {
callback(
null,
require("./components/registering/registering_landing_page.js")
);
},
"registerChunk"
);
}}
/>
<Route
path="/connexion"
getComponent={(location, callback) => {
require.ensure(
[],
function(require) {
callback(
null,
require("./containers/registering/signing_in.js")
);
},
"signinChunk"
);
}}
/>
<Route
path="/equipe"
getComponent={(location, callback) => {
require.ensure(
[],
function(require) {
callback(null, require("./components/team_pres.js"));
},
"teampresChunk"
);
}}
/>
<Route
path="/"
getComponent={(location, callback) => {
require.ensure(
[],
function(require) {
callback(null, require("./containers/app_container.js"));
},
"appContainerChunk"
);
}}
/>
</Switch>
</div>
</BrowserRouter>
</AppInit>
</Provider>,
document.querySelector(".root")
);
Run Code Online (Sandbox Code Playgroud)
我注意到的第一件事是应该构建的块是为供应商和元正确构建的,但不是为我的内部反应组件构建的。但这不是主要问题,事实上,在本地运行服务器时,我根本看不到我的反应应用程序。尽管当我在控制台中检查时,index.ejs 文件已正确加载。
使用包含所有内容的简单 bundle.js 文件(无块)时,一切都运行良好。使用 index.ejs 指向它作为
<script src="/views/bundle.js"></script>
Run Code Online (Sandbox Code Playgroud)
这个webpack.config文件使它工作(归功于@margaretkru):
module.exports = {
devServer: {
historyApiFallback: true
},
entry: {
app:"./src/index.js",
vendor: [
"axios",
"jquery",
"react",
"react-dom",
"react-redux",
"react-router",
"react-router-dom",
"redux"
]
},
output: {
path: __dirname + '/public/views',
filename: "[name].js",
publicPath: "/views/"
},
module: {
loaders: [
{
test: /\.js$/,
loader: "babel-loader",
exclude: [/node_modules/, /pdfmake.js$/]
},
{
test: /\.json$/,
loader: "json-loader"
}
]
},
plugins: [
new webpack.NamedModulesPlugin(),
new HtmlWebpackPlugin({
filename: __dirname + "/views/index.ejs",
template: __dirname + "/views/template.ejs",
inject: 'body',
chunks: ['vendor', 'app'],
chunksSortMode: 'manual'
}),
new PreloadWebpackPlugin({
rel: "preload",
include: ["vendor", "app"]
}),
new webpack.optimize.OccurrenceOrderPlugin(),
]
};new webpack.optimize.CommonsChunkPlugin({
name: "vendor",
minChunks: Infinity
}),
new webpack.NamedModulesPlugin(),
new HtmlWebpackPlugin({
filename: __dirname + "/views/index.ejs",
template: __dirname + "/views/template.ejs",
inject: 'body',
chunks: ['vendor', 'app'],
chunksSortMode: 'manual'
}),
new PreloadWebpackPlugin({
rel: "preload",
include: ["vendor", "app"]
}),
new webpack.optimize.OccurrenceOrderPlugin(),
]
};
Run Code Online (Sandbox Code Playgroud)
真正的问题不是加载的脚本排序,而是更多的是在“预加载”它们之后我实际上并没有加载脚本:HTMLWebpackPlugin 的“注入”行有帮助,因为它注入了这两行:
<script src="/views/vendor.js"/>
<script src="/views/app.js"/>
Run Code Online (Sandbox Code Playgroud)
在我的 index.ejs 正文中
index.ejs 中加载的脚本顺序不正确。现在它是:
<link rel="preload" as="script" href="/views/index.js">
<link rel="preload" as="script" href="/views/vendor.js">
Run Code Online (Sandbox Code Playgroud)
这意味着您的应用程序将在导致您的应用程序根本不出现index.js之前被加载。vendor.js首先,应加载应用程序的所有依赖项 ( vendor.js),然后才加载index.js,因为您需要在执行自定义代码时存在依赖项。所以应该是:
<link rel="preload" as="script" href="/views/vendor.js">
<link rel="preload" as="script" href="/views/index.js">
Run Code Online (Sandbox Code Playgroud)
编辑:
正如我们最终发现的那样,问题不在于脚本的顺序,而是由于脚本实际上并未加载到html. 为此,它们需要作为块添加HtmlWebpackPlugin并注入到index.html:
new HtmlWebpackPlugin({
title: "Deals",
filename: __dirname + "/views/index.ejs",
template: __dirname + "/views/template.ejs",
inject: 'body',
chunks: ['vendor', 'index']
})
Run Code Online (Sandbox Code Playgroud)
此外,块的配置meta被完全删除。所有其余的配置(包括PreloadWebpackPlugin)都很好。