Attempt to fix issue #353 where the plugin fails to handle file name with special characters like @.
The root cause of the issue is that filename extracted from tag src attribute is a URI encoded string (e.g. 'index%40production.js'), so this PR aims to solve it by adding a decoding step when accessing the assets object from webpack.
How has this been tested?
A new test case where it's configuration has all JavaScript assets output with @ in the filename is added. This is check and run to make sure the output files are properly inlined.
Description
Attempt to fix issue #353 where the plugin fails to handle file name with special characters like
@
.The root cause of the issue is that filename extracted from tag
src
attribute is a URI encoded string (e.g. 'index%40production.js'), so this PR aims to solve it by adding a decoding step when accessing theassets
object from webpack.How has this been tested?
@
in the filename is added. This is check and run to make sure the output files are properly inlined.Types of changes
feat
fix
refactor
test
Remarks
N/A