use relative paths in sourcemap #149
Merged
Conversation
This file contains hidden or 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
Author
|
(bulk-closing PRs for libraries I'm no longer using) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Right now the source map generates filenames which are absolute paths on disk (
/home/shish/project/blah.css), which the browser interprets as absolute paths relative to the web root (https://www.shish.io/home/shish/project/blah.css), which means that they will never be found (unless your web server is configured to serve the root of your hard drive)Using relative paths seems like it should work in more cases, and also has the bonus of revealing a bit less about the internals of my server (
../blah.cssinstead of/home/shish/project/blah.css)