Notice the backtick to start the prepended string is at the end and not at the start of the fingerprint. This causes the JS to blow up when loaded in a browser.
Ah it appears this is due to broccoli-asset-rewrite and there is already an opened issue and potential PR fix over there. Should I leave this open here for visibility?
Take the example code below:
The particular line of interest is where we have a template literal.
When we try to fingerprint this template literal string with some
prepend
URL it causes invalid JavaScript to be generated in the output.Expected
Actual
Notice the backtick to start the prepended string is at the end and not at the start of the fingerprint. This causes the JS to blow up when loaded in a browser.
Reproduction:
PR with failing test