npm list --depth=0)node -v): 6.11.0npm -v): 3.10.10When using mix.version after upgrading to laravel-mix 1.0.x, the output chunks are not longer hashed. I thought it could have been the check I had in the mix config to check for development environment but I moved the version call outside of that and it still wouldn't hash the bundles. I had also refactored the mix config file a little, but I reverted those changes back to the exact build script I was using on the pre 1.0 versions of mix and still nothing. I have tried remove node_modules and reinstalling to no avail.
Here is a link to the project in which I am having issues:
https://github.com/brandon14/brandonclothier.me/blob/master/webpack.mix.js
Since version 1.0 mix.version() will use query string like-
app.js?id=8e5c48eadbfdd5458ec6
So you no need to worry about it. Blade mix() will take care of all.
Read more
https://github.com/JeffreyWay/laravel-mix/blob/master/docs/versioning.md
Yes, the query string is added in the manifest file and is job longer appended to the file. Like @ankurk91 said, if you're using laravel, it's taken care of for you.
@devcircus @ankurk91 thanks! I guess I should have read the new docs. I was expecting to see a hash in the filename.
Most helpful comment
Since version 1.0 mix.version() will use query string like-
So you no need to worry about it. Blade
mix()will take care of all.Read more
https://github.com/JeffreyWay/laravel-mix/blob/master/docs/versioning.md