Fix: use stringifyRequest instead of absolute paths in loader output #167
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Per Webpack's documentation on building loaders, the loader-utils package's
stringifyRequest
method should be used by loaders to avoid hash-breaking absolute paths. (See this article for more details on the broken hash problem.)This PR applies Webpack's recommendation to handlebars-loader.
All tests pass. Since the stringifyRequest method is a part of the Webpack loader-utils package and acts as a drop-in replacement for JSON.stringify I didn't think additional tests seemed necessary, but please let me know if you'd like to see something added.