You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 5, 2019. It is now read-only.
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Bad optimization in template string. Changes a valid result to undefined
If the current behavior is a bug, please provide the steps to reproduce.
Js file to repro
// test.jsvarmsg=getMsg({value: 1});console.log(`${msg} <= should not be undefined`);functiongetMsg({value}){// Doesn't seem to repro if there is no multiline herereturn`\${value}`;}
Command to run
npx webpack test.js -o out.js
node out.js
The console.log is reduced to console.log("undefined <= should not be undefined")
What is the expected behavior?
The resulting bundle should print 1 <= should not be undefined
If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information such as the browser version, Node.js version, webpack version, and Operating System.
Node v9.5.0
Webpack v4.6.0
Webpack-cli v2.0.15
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Bad optimization in template string. Changes a valid result to
undefined
If the current behavior is a bug, please provide the steps to reproduce.
Js file to repro
Command to run
The
console.log
is reduced toconsole.log("undefined <= should not be undefined")
What is the expected behavior?
The resulting bundle should print
1 <= should not be undefined
If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information such as the browser version, Node.js version, webpack version, and Operating System.
Node v9.5.0
Webpack v4.6.0
Webpack-cli v2.0.15
This issue was moved from webpack/webpack#7121 by @evilebottnawi. Original issue was by @Cellule.
The text was updated successfully, but these errors were encountered: