unable to replace assetspath in js, but success in html, using webpack4 about string-replace-loader HOT 4 CLOSED

sorry for such a delay. it may be caused by how webpack injects paths. i would advice you to debug by checking the contents of the subject files in the moment of replacement – it's possible that they're not there at that moment. otherwise, if it is not an issue anymore (after almost 2 years lol), close it. thanks

from string-replace-loader.

I know this is an old one now, but I'm hitting the same issue and think I know what is causing it, but not how to resolve it. The loader is operating on the entry point only - but I need the string replacement to happen on the files that get resolved as a result of the entry point. I'd guess the original issue was because of the same thing.

from string-replace-loader.

Looks like the answer is in #54. Use a plug-in.

from string-replace-loader.

thanks for your answer @AllanJard . the tricky part with projects like this is in that Webpack setups are very different in different projects and it is therefore usually quite hard to debug and find a solution. what i'm trying to provide with the loader is that it works in the expected & consistent way when it's used in a clean & simple, isolated Webpack setup, as automated tests verify. even though i'm happy to have a look into the issue and answer questions, everything beyond is up to a user.

i believe, this one can be now closed as well, then.

from string-replace-loader.