Closed mikegleasonjr closed 6 years ago
Can we have a callback function to transform the manifest elements prior to insertion or have both paths use slashes (/)?
This is what I'm planning to do on #55
+1 - this is the 1 other hack that we're maintaining in our fork. I really like #55 ;)
I have two points:
@a-x- you are making a good point here
We should stick to the linux path even on windows so it's consistent if you relly on the key during your build process
Yep, our hack is exactly to make sure that the keys are always the same, regardless of platform. +1 for it being the default behavior.
@mikegleasonjr @weaverryan Would you mind giving me an example of webpack.config.js where this issue occurs, that will help me writing the tests (as I don't have access to a windows machine...)
ping @mikegleasonjr @weaverryan
@mikegleasonjr Good point ;)
{
context: __dirname,
entry: {
'test\\one': './fixtures/file.js',
two: './fixtures/file-two.js'
},
plugins: [
new ManifestPlugin()
]
}
Thanks @mastilver !
Hi,
The keys of the manifest on Windows are:
"path\\file.ext"
Whereas on Linux/OSX it is:
"path/file.ext"
Making it difficult to reference a resource by its key in the manifest.
Can we have a callback function to transform the manifest elements prior to insertion or have both paths use slashes (
/
)?