Wrong hash name with 3.0
See original GitHub issueHi,
Webpack 4.20 with Symfony encore It’s working very well with the 2.7.1 version
With the 3.0.0 version my manifest json look like this
“build/svg/icons.59cf10a6f7abb6fad7fd.svg”: “/build/svg/icons.59cf10a6f7abb6fad7fd.svg”
any ideas why ? my config :
new SvgStorePlugin("svg/**/*.svg", {
output: {
chunk: { name: "svg/icons" },
filename: "svg/icons.[hash].svg",
svgo: true
},
sprite: {
prefix: "icon-",
}
})
Thanks !
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Class: Hash (Ruby 3.0.0)
A Hash maps each of its unique keys to a specific value. A Hash has certain similarities to an Array, but: An Array...
Read more >Python packages hash not matching whilst installing using pip
This error suggests that you're using pip's hash checking mode and may be trying to upgrade a package's version without upgrading the hash...
Read more >Ruby 3.0 changes - Ruby Documentation
Hash #transform_keys : argument for key renaming. Hash#transform_keys(from: to) allows to rename keys in a DRY way. Discussion: Feature #16274 ...
Read more >3 simple ways to check a file's hash with Windows - GlassWire
Or maybe it's the completely wrong file that was mistakenly uploaded to the wrong place. How can I check a file's hash on...
Read more >object-hash - npm
Generate hashes from javascript objects in node and the browser.. Latest version: 3.0.0, last published: 10 months ago.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@pfeiferbit, I took some more time digging into this and finally found what’s probably causing this. A fix for that issue is included in version
3.0.1
🚀If anyone is still running into this issue, feel free to comment on this one or open a new one.
Ah, thanks for the details. I’ll have to look into this when I’m back from travelling in a week. If you’re able to find a fix for this yourself a PR is always welcome! ✌🏼