Age | Commit message (Collapse) | Author |
|
Fixes #9502
|
|
To get it in line with the others.
|
|
--printMemoryUsage
To get it in line with the others.
|
|
Fixes #9486
|
|
Closes #9454
|
|
Closes #8862
|
|
Updates #9363
|
|
Fixes #9357
Fixes #9359
|
|
* Deprecate .Page.Path when backed by a file
* site.Permalinks
* --ignoreVendor (use --ignoreVendorPaths)
Closes #9348
Closes #9349
|
|
Fixes #9165
|
|
Fixes #9162
|
|
Fixes #9051
|
|
Fixes #9048
|
|
The old implementation had some issues, mostly related to the context (e.g. name, file paths) passed to the template.
This new implementation is using the exact same code path for evaluating the pages as in a regular build.
This also makes it more robust and easier to reason about in a multilingual setup.
Now, if you are explicit about the target path, Hugo will now always pick the correct mount and language:
```bash
hugo new content/en/posts/my-first-post.md
```
Fixes #9032
Fixes #7589
Fixes #9043
Fixes #9046
Fixes #9047
|
|
So it at least is possible to do a `hugo mod clean --all` if the cache is in a funky state.
|
|
Fixes #8942
|
|
Fixes #8940
|
|
fail to start"
This reverts commit 3f38c785b7208440e2a9dd9a80cb39d4ae23e676.
|
|
|
|
Fixes #8904
|
|
Updates #8892
|
|
We have been using `go-toml` for language files only. This commit makes it the only TOML library.
It's spec compliant and very fast.
A benchark building a site with 200 pages with TOML front matter:
```bash
name old time/op new time/op delta
SiteNew/Regular_TOML_front_matter-16 48.5ms ± 1% 47.1ms ± 1% -2.85% (p=0.029 n=4+4)
name old alloc/op new alloc/op delta
SiteNew/Regular_TOML_front_matter-16 16.9MB ± 0% 16.7MB ± 0% -1.56% (p=0.029 n=4+4)
name old allocs/op new allocs/op delta
SiteNew/Regular_TOML_front_matter-16 302k ± 0% 296k ± 0% -2.20% (p=0.029 n=4+4)
```
Note that the front matter unmarshaling is only a small part of building a site, so the above is very good.
Fixes #8801
|
|
Fixes #8773
|
|
This commit started out investigating a `concurrent map read write` issue, ending by replacing the map with a struct.
This is easier to reason about, and it's more effective:
```
name old time/op new time/op delta
SiteNew/Regular_Deep_content_tree-16 71.5ms ± 3% 69.4ms ± 5% ~ (p=0.200 n=4+4)
name old alloc/op new alloc/op delta
SiteNew/Regular_Deep_content_tree-16 29.7MB ± 0% 27.9MB ± 0% -5.82% (p=0.029 n=4+4)
name old allocs/op new allocs/op delta
SiteNew/Regular_Deep_content_tree-16 313k ± 0% 303k ± 0% -3.35% (p=0.029 n=4+4)
```
See #8749
|
|
This allows error parsers (VSCode problemMatchers) to use the time notification as bounds for detecting errors.
Closes #8403
|
|
So you can do:
```
hugo server --poll 700ms
```
See #8720
|
|
Fixes #8720
Fixes #6849
Fixes #7930
|
|
Which is in line with how we do it elsewhere.
|
|
|
|
* Add owner path and version.
* Also add thme meta info and Hugo version when run with -v flag
|
|
So they can be used from the config package without cyclic troubles.
Updates #8654
|
|
Fixes #8655
|
|
The main motivation behind this is simplicity and correctnes, but the new small config library is also faster:
```
BenchmarkDefaultConfigProvider/Viper-16 252418 4546 ns/op 2720 B/op 30 allocs/op
BenchmarkDefaultConfigProvider/Custom-16 450756 2651 ns/op 1008 B/op 6 allocs/op
```
Fixes #8633
Fixes #8618
Fixes #8630
Updates #8591
Closes #6680
Closes #5192
|
|
Fixes #8613
|
|
Closes #8531
|
|
It creates lots of diffs even if there are no changes.
|
|
Fixes #8400
|
|
`hugo new theme foo` creates theme `foo` in `./themes` and not in current directory.
|
|
|
|
Revert "Refactor: Remove powershell support" with fixes
Thanks to Ben Mezger (@benmezger) for the original code.
See #8122
This reverts commit a7c515e1b56e8cab34ca2647b4116904df9c8250.
|
|
|
|
|
|
See issue #4296
|
|
But note that the Dart Sass Embedded Protocol is still in beta (beta 5), a main release scheduled for Q1 2021.
Fixes #7380
Fixes #8102
|
|
The substring match in TestExecute deploy test is adjusted accordingly.
|
|
See https://github.com/mvdan/gofumpt
|
|
Fixes #6595
|
|
This commit fixes some issues where modules in /assets share the same name as in node_modules.
This was not intended, and with this commit the node_modules-components should be isolated. If you want to redefine something inside node_modules, use the `defines` option.
Fixes #7948
|
|
Fixes #7816
Fixes #7777
Fixes #7916
|
|
Fixes #7826
|