github/hugo
1
0
Fork 0
mirror of https://github.com/gohugoio/hugo.git synced 2024-11-21 20:46:30 -05:00
Code Issues Projects Releases Packages Wiki Activity
hugo/go.mod

65 lines
2.8 KiB
Modula-2
Raw Normal View History

Add go.mod See #5115
2018-08-25 11:51:57 -04:00
module github.com/gohugoio/hugo
require (
github.com/BurntSushi/locker v0.0.0-20171006230638-a6e239ea1c69
github.com/BurntSushi/toml v0.0.0-20170626110600-a368813c5e64
github.com/PuerkitoBio/purell v1.1.0
Use Go 1.11 modules with Mage See #5115
2018-08-25 11:58:04 -04:00
github.com/PuerkitoBio/urlesc v0.0.0-20170810143723-de5bf2ad4578 // indirect
Add go.mod See #5115
2018-08-25 11:51:57 -04:00
github.com/alecthomas/assert v0.0.0-20170929043011-405dbfeb8e38
Update Chroma Fixes #4993
2018-12-27 04:58:34 -05:00
github.com/alecthomas/chroma v0.6.2
github.com/alecthomas/repr v0.0.0-20181024024818-d37bc2a10ba1 // indirect
Add go.mod See #5115
2018-08-25 11:51:57 -04:00
github.com/bep/debounce v1.1.0
github.com/bep/gitmap v1.0.0
Update to LibSASS 3.5.5 Fixes #5432 See #5435
2018-11-14 04:35:42 -05:00
github.com/bep/go-tocss v0.6.0
Add go.mod See #5115
2018-08-25 11:51:57 -04:00
github.com/chaseadamsio/goorgeous v1.1.0
Update dependencies
2018-09-07 03:49:29 -04:00
github.com/cpuguy83/go-md2man v1.0.8 // indirect
github.com/disintegration/imaging v1.5.0
Add go.mod See #5115
2018-08-25 11:51:57 -04:00
github.com/eknkc/amber v0.0.0-20171010120322-cdade1c07385
github.com/fortytw2/leaktest v1.2.0
github.com/fsnotify/fsnotify v1.4.7
github.com/gobwas/glob v0.2.3
Update dependencies
2018-09-07 03:49:29 -04:00
github.com/gorilla/websocket v1.4.0
github.com/hashicorp/go-immutable-radix v1.0.0
Use Go 1.11 modules with Mage See #5115
2018-08-25 11:58:04 -04:00
github.com/inconshreveable/mousetrap v1.0.0 // indirect
Add go.mod See #5115
2018-08-25 11:51:57 -04:00
github.com/jdkato/prose v1.1.0
Update dependencies
2018-09-07 03:49:29 -04:00
github.com/kr/pretty v0.1.0 // indirect
Add go.mod See #5115
2018-08-25 11:51:57 -04:00
github.com/kyokomi/emoji v1.5.1
Update Mage
2018-09-11 11:54:30 -04:00
github.com/magefile/mage v1.4.0
Update dependencies
2018-09-07 03:49:29 -04:00
github.com/markbates/inflect v1.0.0
Add some color to the relevant filenames in terminal log Fixes #5344
2018-10-24 05:14:51 -04:00
github.com/mattn/go-isatty v0.0.4
Update dependencies
2018-09-07 03:49:29 -04:00
github.com/mattn/go-runewidth v0.0.3 // indirect
Add go.mod See #5115
2018-08-25 11:51:57 -04:00
github.com/miekg/mmark v1.3.6
Update dependencies
2018-09-07 03:49:29 -04:00
github.com/mitchellh/hashstructure v1.0.0
Add /config dir support This commit adds support for a configuration directory (default `config`). The different pieces in this puzzle are: * A new `--environment` (or `-e`) flag. This can also be set with the `HUGO_ENVIRONMENT` OS environment variable. The value for `environment` defaults to `production` when running `hugo` and `development` when running `hugo server`. You can set it to any value you want (e.g. `hugo server -e "Sensible Environment"`), but as it is used to load configuration from the file system, the letter case may be important. You can get this value in your templates with `{{ hugo.Environment }}`. * A new `--configDir` flag (defaults to `config` below your project). This can also be set with `HUGO_CONFIGDIR` OS environment variable. If the `configDir` exists, the configuration files will be read and merged on top of each other from left to right; the right-most value will win on duplicates. Given the example tree below: If `environment` is `production`, the left-most `config.toml` would be the one directly below the project (this can now be omitted if you want), and then `_default/config.toml` and finally `production/config.toml`. And since these will be merged, you can just provide the environment specific configuration setting in you production config, e.g. `enableGitInfo = true`. The order within the directories will be lexical (`config.toml` and then `params.toml`). ```bash config ├── _default │   ├── config.toml │   ├── languages.toml │   ├── menus │   │   ├── menus.en.toml │   │   └── menus.zh.toml │   └── params.toml ├── development │   └── params.toml └── production ├── config.toml └── params.toml ``` Some configuration maps support the language code in the filename (e.g. `menus.en.toml`): `menus` (`menu` also works) and `params`. Also note that the only folders with "a meaning" in the above listing is the top level directories below `config`. The `menus` sub folder is just added for better organization. We use `TOML` in the example above, but Hugo also supports `JSON` and `YAML` as configuration formats. These can be mixed. Fixes #5422
2018-11-15 03:28:02 -05:00
github.com/mitchellh/mapstructure v1.1.2
Add go.mod See #5115
2018-08-25 11:51:57 -04:00
github.com/muesli/smartcrop v0.0.0-20180228075044-f6ebaa786a12
Use Go 1.11 modules with Mage See #5115
2018-08-25 11:58:04 -04:00
github.com/nfnt/resize v0.0.0-20180221191011-83c6a9932646 // indirect
Add go.mod See #5115
2018-08-25 11:51:57 -04:00
github.com/nicksnyder/go-i18n v1.10.0
github.com/olekukonko/tablewriter v0.0.0-20180506121414-d4647c9c7a84
commands: Show server error info in browser The main item in this commit is showing of errors with a file context when running `hugo server`. This can be turned off: `hugo server --disableBrowserError` (can also be set in `config.toml`). But to get there, the error handling in Hugo needed a revision. There are some items left TODO for commits soon to follow, most notable errors in content and config files. Fixes #5284 Fixes #5290 See #5325 See #5324
2018-10-03 08:58:09 -04:00
github.com/pkg/errors v0.8.0
Add go.mod See #5115
2018-08-25 11:51:57 -04:00
github.com/russross/blackfriday v0.0.0-20180804101149-46c73eb196ba
github.com/sanity-io/litter v1.1.0
Use Go 1.11 modules with Mage See #5115
2018-08-25 11:58:04 -04:00
github.com/shurcooL/sanitized_anchor_name v0.0.0-20170918181015-86672fcb3f95 // indirect
Fix "failed to create file caches from configuration: file exists" on Windows Fixes #5497
2018-12-17 04:01:35 -05:00
github.com/spf13/afero v1.2.0
mod: Update cast Closes #5340
2018-10-26 11:13:22 -04:00
github.com/spf13/cast v1.3.0
Add go.mod See #5115
2018-08-25 11:51:57 -04:00
github.com/spf13/cobra v0.0.3
github.com/spf13/fsync v0.0.0-20170320142552-12a01e648f05
common/loggers: Make sure the global logger also gets colored labels See #4414
2018-10-28 11:06:50 -04:00
github.com/spf13/jwalterweatherman v1.0.1-0.20181028145347-94f6ae3ed3bc
Add go.mod See #5115
2018-08-25 11:51:57 -04:00
github.com/spf13/nitro v0.0.0-20131003134307-24d7ef30a12d
deps: Update minify No functional changes, just support for Go Modules.
2018-11-06 14:10:02 -05:00
github.com/spf13/pflag v1.0.3
Add /config dir support This commit adds support for a configuration directory (default `config`). The different pieces in this puzzle are: * A new `--environment` (or `-e`) flag. This can also be set with the `HUGO_ENVIRONMENT` OS environment variable. The value for `environment` defaults to `production` when running `hugo` and `development` when running `hugo server`. You can set it to any value you want (e.g. `hugo server -e "Sensible Environment"`), but as it is used to load configuration from the file system, the letter case may be important. You can get this value in your templates with `{{ hugo.Environment }}`. * A new `--configDir` flag (defaults to `config` below your project). This can also be set with `HUGO_CONFIGDIR` OS environment variable. If the `configDir` exists, the configuration files will be read and merged on top of each other from left to right; the right-most value will win on duplicates. Given the example tree below: If `environment` is `production`, the left-most `config.toml` would be the one directly below the project (this can now be omitted if you want), and then `_default/config.toml` and finally `production/config.toml`. And since these will be merged, you can just provide the environment specific configuration setting in you production config, e.g. `enableGitInfo = true`. The order within the directories will be lexical (`config.toml` and then `params.toml`). ```bash config ├── _default │   ├── config.toml │   ├── languages.toml │   ├── menus │   │   ├── menus.en.toml │   │   └── menus.zh.toml │   └── params.toml ├── development │   └── params.toml └── production ├── config.toml └── params.toml ``` Some configuration maps support the language code in the filename (e.g. `menus.en.toml`): `menus` (`menu` also works) and `params`. Also note that the only folders with "a meaning" in the above listing is the top level directories below `config`. The `menus` sub folder is just added for better organization. We use `TOML` in the example above, but Hugo also supports `JSON` and `YAML` as configuration formats. These can be mixed. Fixes #5422
2018-11-15 03:28:02 -05:00
github.com/spf13/viper v1.3.1
Add a consolidated file cache This commits reworks how file caching is performed in Hugo. Now there is only one way, and it can be configured. This is the default configuration: ```toml [caches] [caches.getjson] dir = ":cacheDir" maxAge = -1 [caches.getcsv] dir = ":cacheDir" maxAge = -1 [caches.images] dir = ":resourceDir/_gen" maxAge = -1 [caches.assets] dir = ":resourceDir/_gen" maxAge = -1 ``` You can override any of these cache setting in your own `config.toml`. The placeholders explained: `:cacheDir`: This is the value of the `cacheDir` config option if set (can also be set via OS env variable `HUGO_CACHEDIR`). It will fall back to `/opt/build/cache/hugo_cache/` on Netlify, or a `hugo_cache` directory below the OS temp dir for the others. `:resourceDir`: This is the value of the `resourceDir` config option. `maxAge` is the time in seconds before a cache entry will be evicted, -1 means forever and 0 effectively turns that particular cache off. This means that if you run your builds on Netlify, all caches configured with `:cacheDir` will be saved and restored on the next build. For other CI vendors, please read their documentation. For an CircleCI example, see https://github.com/bep/hugo-sass-test/blob/6c3960a8f4b90e8938228688bc49bdcdd6b2d99e/.circleci/config.yml Fixes #5404
2018-11-08 04:24:13 -05:00
github.com/stretchr/testify v1.2.3-0.20181014000028-04af85275a5c
deps: Update minify No functional changes, just support for Go Modules.
2018-11-06 14:10:02 -05:00
github.com/tdewolff/minify/v2 v2.3.7
Add go.mod See #5115
2018-08-25 11:51:57 -04:00
github.com/yosssi/ace v0.0.5
golang.org/x/image v0.0.0-20180708004352-c73c2afc3b81
Add GOPATH Hugo building tip
2018-10-09 05:09:00 -04:00
golang.org/x/net v0.0.0-20180906233101-161cd47e91fd // indirect
Add go.mod See #5115
2018-08-25 11:51:57 -04:00
golang.org/x/sync v0.0.0-20180314180146-1d60e4601c6f
Update Chroma Fixes #4993
2018-12-27 04:58:34 -05:00
golang.org/x/sys v0.0.0-20181221143128-b4a75ba826a6 // indirect
Update dependencies
2018-09-07 03:49:29 -04:00
golang.org/x/text v0.3.0
gopkg.in/check.v1 v1.0.0-20180628173108-788fd7840127 // indirect
Add /config dir support This commit adds support for a configuration directory (default `config`). The different pieces in this puzzle are: * A new `--environment` (or `-e`) flag. This can also be set with the `HUGO_ENVIRONMENT` OS environment variable. The value for `environment` defaults to `production` when running `hugo` and `development` when running `hugo server`. You can set it to any value you want (e.g. `hugo server -e "Sensible Environment"`), but as it is used to load configuration from the file system, the letter case may be important. You can get this value in your templates with `{{ hugo.Environment }}`. * A new `--configDir` flag (defaults to `config` below your project). This can also be set with `HUGO_CONFIGDIR` OS environment variable. If the `configDir` exists, the configuration files will be read and merged on top of each other from left to right; the right-most value will win on duplicates. Given the example tree below: If `environment` is `production`, the left-most `config.toml` would be the one directly below the project (this can now be omitted if you want), and then `_default/config.toml` and finally `production/config.toml`. And since these will be merged, you can just provide the environment specific configuration setting in you production config, e.g. `enableGitInfo = true`. The order within the directories will be lexical (`config.toml` and then `params.toml`). ```bash config ├── _default │   ├── config.toml │   ├── languages.toml │   ├── menus │   │   ├── menus.en.toml │   │   └── menus.zh.toml │   └── params.toml ├── development │   └── params.toml └── production ├── config.toml └── params.toml ``` Some configuration maps support the language code in the filename (e.g. `menus.en.toml`): `menus` (`menu` also works) and `params`. Also note that the only folders with "a meaning" in the above listing is the top level directories below `config`. The `menus` sub folder is just added for better organization. We use `TOML` in the example above, but Hugo also supports `JSON` and `YAML` as configuration formats. These can be mixed. Fixes #5422
2018-11-15 03:28:02 -05:00
gopkg.in/yaml.v2 v2.2.2
Add go.mod See #5115
2018-08-25 11:51:57 -04:00
)
Update dependencies
2018-09-07 03:49:29 -04:00
exclude github.com/chaseadamsio/goorgeous v2.0.0+incompatible
replace github.com/markbates/inflect => github.com/markbates/inflect v0.0.0-20171215194931-a12c3aec81a6
Reference in a new issue Copy permalink