[Feature Requirement] customable hash for chunk/entry names

[indooorsman]

Currenty the [hash] will result in upper case string with length of 8, could we custom it by something lke [hash:lower:16] ?

[evanw]

Can you say why you need to customize it?

[indooorsman]

Nothing special but some file system is case sensitive while some not, and in my company there's convention of using lower case for file names :)

[raviteja83]

@evanw is there a way to have the same hashId if the file has not changed? Because of the new Id's everytime, a new deployment could break the route navigation(using dynamically imported components for routes).

[jay-cheon]

@evanw
As @raviteja83 said, I found this thread while I'm having question point about,
when I configure, { splitting: true, entryNames: 'main-[hash]', chunkNames: '[name]-[hash'] }
and when I try build multiple times without changing my codebase,
only chunks files hash is keep same name but named bundle files and main entry file's hash value is changed every build time even if I didn't change any code.

So I'm just about to wonder if content is not changed, whether it's better that hash value is remained or not.