diff options
Diffstat (limited to 'docs/content/en/hugo-pipes/postcss.md')
| -rwxr-xr-x | docs/content/en/hugo-pipes/postcss.md | 11 |
1 files changed, 3 insertions, 8 deletions
diff --git a/docs/content/en/hugo-pipes/postcss.md b/docs/content/en/hugo-pipes/postcss.md index 46833e0a4..b87dc4595 100755 --- a/docs/content/en/hugo-pipes/postcss.md +++ b/docs/content/en/hugo-pipes/postcss.md @@ -3,7 +3,6 @@ title: PostCSS description: Hugo Pipes can process CSS files with PostCSS. date: 2018-07-14 publishdate: 2018-07-14 -lastmod: 2018-07-14 categories: [asset management] keywords: [] menu: @@ -12,10 +11,9 @@ menu: weight: 40 weight: 40 sections_weight: 40 -draft: false --- -Any asset file can be processed using `resources.PostCSS` which takes for argument the resource object and a slice of options listed below. +Any asset file can be processed using `resources.PostCSS` which takes for argument the resource object and a slice of options listed below. The resource will be processed using the project's or theme's own `postcss.config.js` or any file set with the `config` option. @@ -38,15 +36,14 @@ config [string] noMap [bool] : Default is `false`. Disable the default inline sourcemaps -inlineImports [bool] {{< new-in "0.66.0" >}} +inlineImports [bool] : Default is `false`. Enable inlining of @import statements. It does so recursively, but will only import a file once. URL imports (e.g. `@import url('https://fonts.googleapis.com/css?family=Open+Sans&display=swap');`) and imports with media queries will be ignored. Note that this import routine does not care about the CSS spec, so you can have @import anywhere in the file. Hugo will look for imports relative to the module mount and will respect theme overrides. skipInlineImportsNotFound [bool] {{< new-in "0.99.0" >}} - -Before Hugo 0.99.0 when `inlineImports` was enabled and we failed to resolve an import, we logged it as a warning. We now fail the build. If you have regular CSS imports in your CSS that you want to preserve, you can either use imports with URL or media queries (Hugo does not try to resolve those) or set `skipInlineImportsNotFound` to true. +: Default is `false`. Before Hugo 0.99.0 when `inlineImports` was enabled and we failed to resolve an import, we logged it as a warning. We now fail the build. If you have regular CSS imports in your CSS that you want to preserve, you can either use imports with URL or media queries (Hugo does not try to resolve those) or set `skipInlineImportsNotFound` to true. _If no configuration file is used:_ @@ -72,8 +69,6 @@ syntax [string] ## Check Hugo Environment from postcss.config.js -{{< new-in "0.66.0" >}} - The current Hugo environment name (set by `--environment` or in config or OS environment) is available in the Node context, which allows constructs like this: ```js |