# \[SOLVED\] No sourcemap with PostCSS (0.46)

**URL:** https://discourse.gohugo.io/t/solved-no-sourcemap-with-postcss-0-46/13649
**Category:** support
**Created:** [August 17, 2018, 9:47am UTC](https://discourse.gohugo.io/t/solved-no-sourcemap-with-postcss-0-46/13649 "2018-08-17T09:47:38Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![holehan](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/holehan/32/5121_2.png) [@holehan](https://discourse.gohugo.io/u/holehan)
#### Post date: [September 3, 2018, 3:54pm UTC](https://discourse.gohugo.io/t/solved-no-sourcemap-with-postcss-0-46/13649/6 "2018-09-03T15:54:33Z")

</div>

PostCSS sourcemaps are indeed possible with Hugo Pipes. From my experience it’s best to ignore the PostCSS options Hugo Pipes offers and just use a `postcss.config.js` file. Setting `map: { inline: true }` there should embed the sourcemap into your style file:

```auto
module.exports = {
  map: { inline: true },
  plugins: {
    ...
  }
};

```

If you want to configure PostCSS the Hugo Pipes way with `postCSS (dict "noMap" false)` you’d have to use a separate config file anyway [according to the postcss-cli maintainers](https://github.com/postcss/postcss-cli): “If you want to set options via CLI, it’s mandatory to reference ctx.options in postcss.config.js”.

```auto
module.exports = ctx => ({
  map: ctx.options.map,
  plugins: {
    ...
  }
});

```

---

_[View the full topic](https://discourse.gohugo.io/t/solved-no-sourcemap-with-postcss-0-46/13649)._