Fix sourcemapping url replacement #484
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Includes a work-around for bug where if the sourcemap is nested two levels deep, it'll resolve as the source file that's being mapped, rather than the map itself by Sprockets. So
context.resolve("a/b/c.js.map")will returnc.jsinstead ofc.js.map. This doesn't happen when the nesting is only one level deep, likea/b.js/mapor if there's no nesting at all. This is a long-standing Sprockets bug we need to find and fix, but it predates this processor, though the processor tickles it.Also, this makes sure that nested files that do no tickle the double+ nesting bug will be correctly mapped.