Add pathPrefix option #2
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
|
Thanks! Also do you (or your team) use any CLI tools like (The reason I'm asking this is because I'm trying hard to push this plugin to those CLI tools, for better sourcemap support, example facebook/create-react-app#3202 with support for others coming soon) |
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.
This option allows appending a prefix to the paths generated by css-visor for the assets its creates.
In our build configuration, the paths used at runtime to load assets may be different from the root paths within the source tree. For example, styles are always loaded from within a
/styles/route, which won't work by default with css-visor which always emits routes relative to the site source root folder name. This change allows aligning the output from css-visor to an arbitrary route at runtime.