From 2c81a633ed09a904401b1f99d8d427a125be1bce Mon Sep 17 00:00:00 2001 From: Ryan Shaw Date: Mon, 6 Mar 2017 19:30:48 -0700 Subject: [PATCH] Always print pathInfo in webpack build That way, you can run `JS_BUILD_NO_UGLIFY=1 npm run webpack-production` and it will still output a comment with the path to each Thing it defines/requires so you can more easily tell what you are looking at. But when it does uglify, it will still strip out those comments Test plan: run: JS_BUILD_NO_UGLIFY=1 npm run webpack-production The output it puts out should have comments about which module it is defining Change-Id: Ia6421f988848c1f6cc167bfe07ec0534ffc0ac79 Reviewed-on: https://gerrit.instructure.com/104204 Tested-by: Jenkins Reviewed-by: Simon Williams Product-Review: Ryan Shaw QA-Review: Ryan Shaw --- frontend_build/baseWebpackConfig.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/frontend_build/baseWebpackConfig.js b/frontend_build/baseWebpackConfig.js index 54bfe24ecd5..5f58a0bdcb8 100644 --- a/frontend_build/baseWebpackConfig.js +++ b/frontend_build/baseWebpackConfig.js @@ -71,7 +71,7 @@ module.exports = { path: path.join(__dirname, '../public', webpackPublicPath), // Add /* filename */ comments to generated require()s in the output. - pathinfo: process.env.NODE_ENV !== 'production', + pathinfo: true, filename: '[name].bundle-[chunkhash:10].js', chunkFilename: '[name].chunk-[chunkhash:10].js',