-
-
Notifications
You must be signed in to change notification settings - Fork 8.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Specifying output.filename
disables auto-minify in production mode
#6732
Comments
Cannot reproduce with Node v8.9.4 and webpack 4.1.1. Could you attach an example? |
I don't think this is a bug, but a user error instead. |
I am able to reproduce this consistently by un-commenting the file name
line. That said, the file name did have a query string attached to it for
cache busting. I'll try removing that when I get a chance. (I would still
consider that a bug, but I have no idea if that is actually the issue.)
This is a private repository, but I will see if I can assemble a minimal
example as well.
…On Tue, Mar 13, 2018 at 1:43 AM Tobias Koppers ***@***.***> wrote:
I don't think this is a bug, but a user error instead.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#6732 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADdko45Yd6GCSbciy-wmqDRLoAjzp6Skks5td4awgaJpZM4SnGaO>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Specifying
output.filename
inwebpack.config.js
disables output minification in production mode. When commenting out that single line of config, it works as intended.If the current behavior is a bug, please provide the steps to reproduce.
Specify
output: { filename: 'foo.js' } }
andmode: 'production'
in Webpack config and runwebpack
CLIWhat is the expected behavior?
Always minify the output bundle.
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 8.9.4, Webpack 4.1.1, macOS 10.12.6
The text was updated successfully, but these errors were encountered: