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
Can we allow the filename and chunkFilename passed in trought the constructor to be functions instead of string only?
In our case it would make it easy to toggle the [hashcontent] for some bundles.
We would pass the option as followed: filename: (chunk) => chunk.name === "NotHashedBundle" ? '[name].css' : '[name].[contenthash].css'
Might be worth noting that the latest version of webpack also supports something simular to this in their output.
eg: filename: (data) => data.chunk.name === "NotHashedBundle" ? '[name].js' : '[name].[chunkhash].js'
The text was updated successfully, but these errors were encountered:
Quick question, at the moment I can't get the tests passing, I'm getting Error: expect(received).toEqual(expected) but the expected and received printed out after this message seem to be the same.
My encoding is the same (utf-8), from what I can see its failing on carriage return. Any hint on how to get this fixed?
berthertogen
changed the title
Feature: allow the option filename to be a function.
feat: allow the option filename to be a function
May 14, 2018
Can we allow the filename and chunkFilename passed in trought the constructor to be functions instead of string only?
In our case it would make it easy to toggle the [hashcontent] for some bundles.
We would pass the option as followed:
filename: (chunk) => chunk.name === "NotHashedBundle" ? '[name].css' : '[name].[contenthash].css'
Might be worth noting that the latest version of webpack also supports something simular to this in their output.
eg:
filename: (data) => data.chunk.name === "NotHashedBundle" ? '[name].js' : '[name].[chunkhash].js'
The text was updated successfully, but these errors were encountered: