-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Source maps use full path as filename #7
Comments
We use server-side post-commit hooks to deploy changes to server. Thus we add map files to git. |
I'm amazed that, about a year later, this hasn't had much attention. It's a rather important feature for users who have workflows similar to the one mentioned above, where map files are committed into VCS. This can be rather bothering since absolute paths -- meaning personal OS file tree structure is also committed into VCS -- might contain sensitive information.. Might, may not, but it is a possibility |
Here's a possible solution. Replace Lines 207 to 215 in f79854f
Could be made an option, so one could optionally relativize paths and keep the absolute path alternative baked in as well. |
@XhmikosR Yes, I'll try to figure it out now. |
Fix shipped in 2.0.0 with other changes |
@lahmatiy: there's still an issue on Windows with v2.0.0:
I suggest that you either enable Windows testing on Travis or add AppVeyor :) |
It's seems source map is including full paths rather than relative files
{"version":3,"sources":["W:\test\css\index.css"],"names":[],"mappings":....
i'd expect to see
{"version":3,"sources":["index.css"],"names":[],"mappings":...
running win10
css/csso#348
The text was updated successfully, but these errors were encountered: