Source maps use full path as filename about csso-cli HOT 7 CLOSED

@XhmikosR Yes, I'll try to figure it out now.

from csso-cli.

Fix shipped in 2.0.0 with other changes

from csso-cli.

We use server-side post-commit hooks to deploy changes to server. Thus we add map files to git.
Full path in "sources" makes work very annoying when your colleague change something in css and your working copy became partially invalid.

from csso-cli.

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

from csso-cli.

Here's a possible solution. Replace path.resolve with path.relative, just as is, having return relative paths with regards to the cwd to the input and/or output files.

Could be made an option, so one could optionally relativize paths and keep the absolute path alternative baked in as well.

from csso-cli.

@lahmatiy any chance you could get this fixed? I'm looking into switching to csso and it seems we are hitting this issue.

from csso-cli.

@lahmatiy: there's still an issue on Windows with v2.0.0:

dist\\css\\bootstrap-grid.css

I suggest that you either enable Windows testing on Travis or add AppVeyor :)

from csso-cli.