mirror of
https://github.com/tiennm99/hugoDocs.git
synced 2026-10-14 06:17:45 +00:00
Add note about caching for Hugo Pipes.
As per discussion in [Is the new js.Build functionality cached?](https://discourse.gohugo.io/t/is-the-new-js-build-functionality-cached/27276)
This commit is contained in:
1 parent
c91be3403e
commit
7297c11727
1 file changed
+12
@@ -50,3 +50,15 @@ The example above can therefore also be written as follows:
|
||||
{{ $style := resources.Get "sass/main.scss" | toCSS | minify | fingerprint }}
|
||||
<link rel="stylesheet" href="{{ $style.Permalink }}">
|
||||
```
|
||||
|
||||
### Caching
|
||||
|
||||
Hugo Pipes invocations are cached based on the entire _pipe chain_.
|
||||
|
||||
An example of a pipe chain is:
|
||||
|
||||
```go-html-template
|
||||
{{ $mainJs := resources.Get "js/main.js" | js.Build "main.js" | minify | fingerprint }}
|
||||
```
|
||||
|
||||
The pipe chain is only invoked the first time it is encountered in a site build, and results are otherwise loaded from cache. As such, Hugo Pipes can be used in templates which are executed thousands or millions of times without negatively impacting the build performance.
|
||||
Reference in new issue
Block a user