-
Notifications
You must be signed in to change notification settings - Fork 116
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
using Less Autoprefix plugin breaks sourcemaps (sources property) #126
Comments
No idea - less should be dealing with the sourcemaps of plugins before it even hands data back to us. Will take some debugging. |
I understand now your are using inline sourcemap. So i tested |
Reopen on the relevant repo and link to this issue so people can track the progress |
When searching for a solution for gulp-community#126 i wondered why using Less with sourceMapFileInline (setting the SourceContent property of the source map with source files contents). Not using the sourceMapFileInline and using `result.map` directly gives me the same results after some testing.
When i using the following gulpfile.js:
The source map got a invalid second value for the sources property (
"../<input css 1>"
).The sourcemap code looks like that shown below:
When using
autoprefixer = require('gulp-autoprefixer');
with.pipe(autoprefixer())
instead of the plugin, the generated sourcemap is correct.To verify if the problem is not related to the Less Autoprefix plugin itself, i have compiled the Less code with the command line Less compiler and the autoprefix plugin by running:
lessc less/t.less css/t.css --autoprefix --source-map --source-map-less-inline
. Also the preceding command gives an sourcemap as expected ({"version":3,"sources":["../less/t.less","t.css"],"names":[]
)The text was updated successfully, but these errors were encountered: