postcss-import and gulp-sourcemaps about postcss-import HOT 9 CLOSED

@vkrol works without {includeContent: false, sourceRoot: '/styles/'} option, because sourceRoot path points to a wrong place. Deleting the options works, it will include all the original sources into the source map, which is the recommended way.

If you really want to serve the sources from disk, then you have to pass the correct sourceRoot, that is ../styles/bundles/.

../a.css is relative to bundle.css in the sources, bundle.css is written to the build folder, so you need to go one level up, and then into the original path of bundle.css.

from postcss-import.

I don't use sourcemap, but I think postcss is pretty good at it.
We currently have some tests for it. Seems related to https://github.com/cssnext/gulp-cssnext/issues/6

@ai postcss-import is just moving some node, this should not affect source (so sourcemap) right ?

from postcss-import.

🔔 I got same issue probably.

from postcss-import.

same 😹

from postcss-import.

Does anyone still have this issue with the latest versions of everything?

from postcss-import.

I get the same results with the latest version.

@w0rm @ai Any ideas? I don't use gulp; is the gulpfile correct?

from postcss-import.

It is gulp-postcss issue, as I understand. postcss-import doesn’t do anything with source maps, as I understand. But gulp-postcss could miss src → dest changes.

from postcss-import.

@w0rm thanks!

from postcss-import.

@w0rm Thank You! Was having the same problem.

from postcss-import.