Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
// Copyright 2019 The Hugo Authors. All rights reserved.
|
|
|
|
//
|
|
|
|
// Licensed under the Apache License, Version 2.0 (the "License");
|
|
|
|
// you may not use this file except in compliance with the License.
|
|
|
|
// You may obtain a copy of the License at
|
|
|
|
// http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
//
|
|
|
|
// Unless required by applicable law or agreed to in writing, software
|
|
|
|
// distributed under the License is distributed on an "AS IS" BASIS,
|
|
|
|
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
|
|
// See the License for the specific language governing permissions and
|
|
|
|
// limitations under the License.
|
|
|
|
|
|
|
|
package modules
|
|
|
|
|
|
|
|
import (
|
|
|
|
"bufio"
|
|
|
|
"bytes"
|
|
|
|
"context"
|
|
|
|
"encoding/json"
|
|
|
|
"fmt"
|
|
|
|
"io"
|
|
|
|
"io/ioutil"
|
|
|
|
"os"
|
|
|
|
"os/exec"
|
|
|
|
"path/filepath"
|
2020-02-19 04:39:36 -05:00
|
|
|
"regexp"
|
2020-12-02 07:23:25 -05:00
|
|
|
"strings"
|
|
|
|
"time"
|
2020-02-19 04:39:36 -05:00
|
|
|
|
2021-12-12 06:11:11 -05:00
|
|
|
"github.com/gohugoio/hugo/common/collections"
|
2020-12-18 12:20:12 -05:00
|
|
|
"github.com/gohugoio/hugo/common/hexec"
|
|
|
|
|
2020-02-19 10:59:54 -05:00
|
|
|
hglob "github.com/gohugoio/hugo/hugofs/glob"
|
|
|
|
|
2020-09-09 15:10:28 -04:00
|
|
|
"github.com/gobwas/glob"
|
|
|
|
|
2020-02-19 04:39:36 -05:00
|
|
|
"github.com/gohugoio/hugo/hugofs"
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
|
|
|
|
"github.com/gohugoio/hugo/hugofs/files"
|
|
|
|
|
|
|
|
"github.com/gohugoio/hugo/common/loggers"
|
|
|
|
|
|
|
|
"github.com/gohugoio/hugo/config"
|
|
|
|
|
|
|
|
"github.com/rogpeppe/go-internal/module"
|
|
|
|
|
|
|
|
"github.com/gohugoio/hugo/common/hugio"
|
|
|
|
|
2022-05-02 10:07:52 -04:00
|
|
|
"errors"
|
|
|
|
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
"github.com/spf13/afero"
|
|
|
|
)
|
|
|
|
|
2020-12-02 07:23:25 -05:00
|
|
|
var fileSeparator = string(os.PathSeparator)
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
|
|
|
|
const (
|
|
|
|
goBinaryStatusOK goBinaryStatus = iota
|
|
|
|
goBinaryStatusNotFound
|
|
|
|
goBinaryStatusTooOld
|
|
|
|
)
|
|
|
|
|
|
|
|
// The "vendor" dir is reserved for Go Modules.
|
|
|
|
const vendord = "_vendor"
|
|
|
|
|
|
|
|
const (
|
|
|
|
goModFilename = "go.mod"
|
|
|
|
goSumFilename = "go.sum"
|
|
|
|
)
|
|
|
|
|
|
|
|
// NewClient creates a new Client that can be used to manage the Hugo Components
|
|
|
|
// in a given workingDir.
|
|
|
|
// The Client will resolve the dependencies recursively, but needs the top
|
|
|
|
// level imports to start out.
|
|
|
|
func NewClient(cfg ClientConfig) *Client {
|
|
|
|
fs := cfg.Fs
|
|
|
|
n := filepath.Join(cfg.WorkingDir, goModFilename)
|
|
|
|
goModEnabled, _ := afero.Exists(fs, n)
|
|
|
|
var goModFilename string
|
|
|
|
if goModEnabled {
|
|
|
|
goModFilename = n
|
|
|
|
}
|
|
|
|
|
2021-12-12 06:11:11 -05:00
|
|
|
var env []string
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
mcfg := cfg.ModuleConfig
|
|
|
|
|
|
|
|
config.SetEnvVars(&env,
|
|
|
|
"PWD", cfg.WorkingDir,
|
2019-07-26 04:55:50 -04:00
|
|
|
"GO111MODULE", "on",
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
"GOPROXY", mcfg.Proxy,
|
|
|
|
"GOPRIVATE", mcfg.Private,
|
2021-12-12 06:11:11 -05:00
|
|
|
"GONOPROXY", mcfg.NoProxy,
|
|
|
|
"GOPATH", cfg.CacheDir,
|
2022-02-18 06:43:59 -05:00
|
|
|
"GOWORK", mcfg.Workspace, // Requires Go 1.18, see https://tip.golang.org/doc/go1.18
|
2021-12-22 04:53:03 -05:00
|
|
|
// GOCACHE was introduced in Go 1.15. This matches the location derived from GOPATH above.
|
|
|
|
"GOCACHE", filepath.Join(cfg.CacheDir, "pkg", "mod"),
|
2021-12-12 06:11:11 -05:00
|
|
|
)
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
|
|
|
|
logger := cfg.Logger
|
|
|
|
if logger == nil {
|
|
|
|
logger = loggers.NewWarningLogger()
|
|
|
|
}
|
|
|
|
|
2020-09-09 15:10:28 -04:00
|
|
|
var noVendor glob.Glob
|
|
|
|
if cfg.ModuleConfig.NoVendor != "" {
|
|
|
|
noVendor, _ = hglob.GetGlob(hglob.NormalizePath(cfg.ModuleConfig.NoVendor))
|
|
|
|
}
|
|
|
|
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
return &Client{
|
|
|
|
fs: fs,
|
2019-07-31 02:21:17 -04:00
|
|
|
ccfg: cfg,
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
logger: logger,
|
2020-09-09 15:10:28 -04:00
|
|
|
noVendor: noVendor,
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
moduleConfig: mcfg,
|
|
|
|
environ: env,
|
2020-12-02 07:23:25 -05:00
|
|
|
GoModulesFilename: goModFilename,
|
|
|
|
}
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
}
|
|
|
|
|
|
|
|
// Client contains most of the API provided by this package.
|
|
|
|
type Client struct {
|
|
|
|
fs afero.Fs
|
2020-10-21 05:17:48 -04:00
|
|
|
logger loggers.Logger
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
|
2020-09-09 15:10:28 -04:00
|
|
|
noVendor glob.Glob
|
|
|
|
|
2019-07-31 02:21:17 -04:00
|
|
|
ccfg ClientConfig
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
|
|
|
|
// The top level module config
|
|
|
|
moduleConfig Config
|
|
|
|
|
|
|
|
// Environment variables used in "go get" etc.
|
|
|
|
environ []string
|
|
|
|
|
|
|
|
// Set when Go modules are initialized in the current repo, that is:
|
|
|
|
// a go.mod file exists.
|
|
|
|
GoModulesFilename string
|
|
|
|
|
|
|
|
// Set if we get a exec.ErrNotFound when running Go, which is most likely
|
|
|
|
// due to being run on a system without Go installed. We record it here
|
|
|
|
// so we can give an instructional error at the end if module/theme
|
|
|
|
// resolution fails.
|
|
|
|
goBinaryStatus goBinaryStatus
|
|
|
|
}
|
|
|
|
|
|
|
|
// Graph writes a module dependenchy graph to the given writer.
|
|
|
|
func (c *Client) Graph(w io.Writer) error {
|
|
|
|
mc, coll := c.collect(true)
|
|
|
|
if coll.err != nil {
|
|
|
|
return coll.err
|
|
|
|
}
|
|
|
|
for _, module := range mc.AllModules {
|
|
|
|
if module.Owner() == nil {
|
|
|
|
continue
|
|
|
|
}
|
|
|
|
|
|
|
|
prefix := ""
|
|
|
|
if module.Disabled() {
|
|
|
|
prefix = "DISABLED "
|
|
|
|
}
|
|
|
|
dep := pathVersion(module.Owner()) + " " + pathVersion(module)
|
|
|
|
if replace := module.Replace(); replace != nil {
|
|
|
|
if replace.Version() != "" {
|
|
|
|
dep += " => " + pathVersion(replace)
|
|
|
|
} else {
|
|
|
|
// Local dir.
|
|
|
|
dep += " => " + replace.Dir()
|
|
|
|
}
|
|
|
|
}
|
|
|
|
fmt.Fprintln(w, prefix+dep)
|
|
|
|
}
|
|
|
|
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// Tidy can be used to remove unused dependencies from go.mod and go.sum.
|
|
|
|
func (c *Client) Tidy() error {
|
|
|
|
tc, coll := c.collect(false)
|
|
|
|
if coll.err != nil {
|
|
|
|
return coll.err
|
|
|
|
}
|
|
|
|
|
|
|
|
if coll.skipTidy {
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
return c.tidy(tc.AllModules, false)
|
|
|
|
}
|
|
|
|
|
|
|
|
// Vendor writes all the module dependencies to a _vendor folder.
|
|
|
|
//
|
|
|
|
// Unlike Go, we support it for any level.
|
|
|
|
//
|
|
|
|
// We, by default, use the /_vendor folder first, if found. To disable,
|
|
|
|
// run with
|
2022-01-04 07:07:10 -05:00
|
|
|
// hugo --ignoreVendorPaths=".*"
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
//
|
|
|
|
// Given a module tree, Hugo will pick the first module for a given path,
|
|
|
|
// meaning that if the top-level module is vendored, that will be the full
|
|
|
|
// set of dependencies.
|
|
|
|
func (c *Client) Vendor() error {
|
2019-07-31 02:21:17 -04:00
|
|
|
vendorDir := filepath.Join(c.ccfg.WorkingDir, vendord)
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
if err := c.rmVendorDir(vendorDir); err != nil {
|
|
|
|
return err
|
|
|
|
}
|
2020-04-07 04:13:55 -04:00
|
|
|
if err := c.fs.MkdirAll(vendorDir, 0755); err != nil {
|
|
|
|
return err
|
|
|
|
}
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
|
|
|
|
// Write the modules list to modules.txt.
|
|
|
|
//
|
|
|
|
// On the form:
|
|
|
|
//
|
|
|
|
// # github.com/alecthomas/chroma v0.6.3
|
|
|
|
//
|
|
|
|
// This is how "go mod vendor" does it. Go also lists
|
|
|
|
// the packages below it, but that is currently not applicable to us.
|
|
|
|
//
|
|
|
|
var modulesContent bytes.Buffer
|
|
|
|
|
|
|
|
tc, coll := c.collect(true)
|
|
|
|
if coll.err != nil {
|
|
|
|
return coll.err
|
|
|
|
}
|
|
|
|
|
|
|
|
for _, t := range tc.AllModules {
|
|
|
|
if t.Owner() == nil {
|
|
|
|
// This is the project.
|
|
|
|
continue
|
|
|
|
}
|
2020-09-09 13:08:03 -04:00
|
|
|
|
2020-09-09 15:10:28 -04:00
|
|
|
if !c.shouldVendor(t.Path()) {
|
|
|
|
continue
|
|
|
|
}
|
|
|
|
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
if !t.IsGoMod() && !t.Vendor() {
|
|
|
|
// We currently do not vendor components living in the
|
|
|
|
// theme directory, see https://github.com/gohugoio/hugo/issues/5993
|
|
|
|
continue
|
|
|
|
}
|
|
|
|
|
2021-02-15 04:47:32 -05:00
|
|
|
// See https://github.com/gohugoio/hugo/issues/8239
|
|
|
|
// This is an error situation. We need something to vendor.
|
|
|
|
if t.Mounts() == nil {
|
2022-05-02 10:07:52 -04:00
|
|
|
return fmt.Errorf("cannot vendor module %q, need at least one mount", t.Path())
|
2021-02-15 04:47:32 -05:00
|
|
|
}
|
|
|
|
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
fmt.Fprintln(&modulesContent, "# "+t.Path()+" "+t.Version())
|
|
|
|
|
|
|
|
dir := t.Dir()
|
|
|
|
|
|
|
|
for _, mount := range t.Mounts() {
|
2020-04-07 04:13:55 -04:00
|
|
|
sourceFilename := filepath.Join(dir, mount.Source)
|
|
|
|
targetFilename := filepath.Join(vendorDir, t.Path(), mount.Source)
|
|
|
|
fi, err := c.fs.Stat(sourceFilename)
|
|
|
|
if err != nil {
|
2022-05-02 10:07:52 -04:00
|
|
|
return fmt.Errorf("failed to vendor module: %w", err)
|
2020-04-07 04:13:55 -04:00
|
|
|
}
|
|
|
|
|
|
|
|
if fi.IsDir() {
|
|
|
|
if err := hugio.CopyDir(c.fs, sourceFilename, targetFilename, nil); err != nil {
|
2022-05-02 10:07:52 -04:00
|
|
|
return fmt.Errorf("failed to copy module to vendor dir: %w", err)
|
2020-04-07 04:13:55 -04:00
|
|
|
}
|
|
|
|
} else {
|
|
|
|
targetDir := filepath.Dir(targetFilename)
|
|
|
|
|
|
|
|
if err := c.fs.MkdirAll(targetDir, 0755); err != nil {
|
2022-05-02 10:07:52 -04:00
|
|
|
return fmt.Errorf("failed to make target dir: %w", err)
|
2020-04-07 04:13:55 -04:00
|
|
|
}
|
|
|
|
|
|
|
|
if err := hugio.CopyFile(c.fs, sourceFilename, targetFilename); err != nil {
|
2022-05-02 10:07:52 -04:00
|
|
|
return fmt.Errorf("failed to copy module file to vendor: %w", err)
|
2020-04-07 04:13:55 -04:00
|
|
|
}
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// Include the resource cache if present.
|
|
|
|
resourcesDir := filepath.Join(dir, files.FolderResources)
|
|
|
|
_, err := c.fs.Stat(resourcesDir)
|
|
|
|
if err == nil {
|
|
|
|
if err := hugio.CopyDir(c.fs, resourcesDir, filepath.Join(vendorDir, t.Path(), files.FolderResources), nil); err != nil {
|
2022-05-02 10:07:52 -04:00
|
|
|
return fmt.Errorf("failed to copy resources to vendor dir: %w", err)
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2022-04-05 13:36:08 -04:00
|
|
|
// Include the config directory if present.
|
|
|
|
configDir := filepath.Join(dir, "config")
|
|
|
|
_, err = c.fs.Stat(configDir)
|
|
|
|
if err == nil {
|
|
|
|
if err := hugio.CopyDir(c.fs, configDir, filepath.Join(vendorDir, t.Path(), "config"), nil); err != nil {
|
2022-05-02 10:07:52 -04:00
|
|
|
return fmt.Errorf("failed to copy config dir to vendor dir: %w", err)
|
2022-04-05 13:36:08 -04:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
// Also include any theme.toml or config.* files in the root.
|
|
|
|
configFiles, _ := afero.Glob(c.fs, filepath.Join(dir, "config.*"))
|
|
|
|
configFiles = append(configFiles, filepath.Join(dir, "theme.toml"))
|
|
|
|
for _, configFile := range configFiles {
|
|
|
|
if err := hugio.CopyFile(c.fs, configFile, filepath.Join(vendorDir, t.Path(), filepath.Base(configFile))); err != nil {
|
|
|
|
if !os.IsNotExist(err) {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
if modulesContent.Len() > 0 {
|
|
|
|
if err := afero.WriteFile(c.fs, filepath.Join(vendorDir, vendorModulesFilename), modulesContent.Bytes(), 0666); err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// Get runs "go get" with the supplied arguments.
|
|
|
|
func (c *Client) Get(args ...string) error {
|
2022-03-20 11:24:37 -04:00
|
|
|
if len(args) == 0 || (len(args) == 1 && strings.Contains(args[0], "-u")) {
|
2020-01-30 03:08:49 -05:00
|
|
|
update := len(args) != 0
|
2022-03-20 11:24:37 -04:00
|
|
|
patch := update && (args[0] == "-u=patch") //
|
2020-01-30 03:08:49 -05:00
|
|
|
|
|
|
|
// We need to be explicit about the modules to get.
|
|
|
|
for _, m := range c.moduleConfig.Imports {
|
2020-02-18 07:35:29 -05:00
|
|
|
if !isProbablyModule(m.Path) {
|
|
|
|
// Skip themes/components stored below /themes etc.
|
|
|
|
// There may be false positives in the above, but those
|
|
|
|
// should be rare, and they will fail below with an
|
|
|
|
// "cannot find module providing ..." message.
|
|
|
|
continue
|
|
|
|
}
|
2020-01-30 03:08:49 -05:00
|
|
|
var args []string
|
2022-03-20 11:24:37 -04:00
|
|
|
|
|
|
|
if update && !patch {
|
2021-08-26 11:24:52 -04:00
|
|
|
args = append(args, "-u")
|
2022-03-20 11:24:37 -04:00
|
|
|
} else if update && patch {
|
|
|
|
args = append(args, "-u=patch")
|
2020-01-30 03:08:49 -05:00
|
|
|
}
|
|
|
|
args = append(args, m.Path)
|
2022-03-20 11:24:37 -04:00
|
|
|
|
2020-01-30 03:08:49 -05:00
|
|
|
if err := c.get(args...); err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
return c.get(args...)
|
|
|
|
}
|
|
|
|
|
|
|
|
func (c *Client) get(args ...string) error {
|
2021-08-26 11:24:52 -04:00
|
|
|
var hasD bool
|
|
|
|
for _, arg := range args {
|
|
|
|
if arg == "-d" {
|
|
|
|
hasD = true
|
|
|
|
break
|
|
|
|
}
|
|
|
|
}
|
|
|
|
if !hasD {
|
|
|
|
// go get without the -d flag does not make sense to us, as
|
|
|
|
// it will try to build and install go packages.
|
|
|
|
args = append([]string{"-d"}, args...)
|
|
|
|
}
|
2020-10-21 05:17:48 -04:00
|
|
|
if err := c.runGo(context.Background(), c.logger.Out(), append([]string{"get"}, args...)...); err != nil {
|
2022-05-02 10:07:52 -04:00
|
|
|
return fmt.Errorf("failed to get %q: %w", args, err)
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
}
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// Init initializes this as a Go Module with the given path.
|
|
|
|
// If path is empty, Go will try to guess.
|
|
|
|
// If this succeeds, this project will be marked as Go Module.
|
|
|
|
func (c *Client) Init(path string) error {
|
2020-10-21 05:17:48 -04:00
|
|
|
err := c.runGo(context.Background(), c.logger.Out(), "mod", "init", path)
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
if err != nil {
|
2022-05-02 10:07:52 -04:00
|
|
|
return fmt.Errorf("failed to init modules: %w", err)
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
}
|
|
|
|
|
2019-07-31 02:21:17 -04:00
|
|
|
c.GoModulesFilename = filepath.Join(c.ccfg.WorkingDir, goModFilename)
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
2020-02-19 04:39:36 -05:00
|
|
|
var verifyErrorDirRe = regexp.MustCompile(`dir has been modified \((.*?)\)`)
|
|
|
|
|
|
|
|
// Verify checks that the dependencies of the current module,
|
|
|
|
// which are stored in a local downloaded source cache, have not been
|
|
|
|
// modified since being downloaded.
|
|
|
|
func (c *Client) Verify(clean bool) error {
|
2020-12-23 03:26:23 -05:00
|
|
|
// TODO(bep) add path to mod clean
|
2020-02-19 04:39:36 -05:00
|
|
|
err := c.runVerify()
|
|
|
|
if err != nil {
|
|
|
|
if clean {
|
|
|
|
m := verifyErrorDirRe.FindAllStringSubmatch(err.Error(), -1)
|
|
|
|
if m != nil {
|
|
|
|
for i := 0; i < len(m); i++ {
|
|
|
|
c, err := hugofs.MakeReadableAndRemoveAllModulePkgDir(c.fs, m[i][1])
|
|
|
|
if err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
fmt.Println("Cleaned", c)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
// Try to verify it again.
|
|
|
|
err = c.runVerify()
|
|
|
|
}
|
|
|
|
}
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
|
2020-02-19 10:59:54 -05:00
|
|
|
func (c *Client) Clean(pattern string) error {
|
|
|
|
mods, err := c.listGoMods()
|
|
|
|
if err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
|
|
|
|
var g glob.Glob
|
|
|
|
|
|
|
|
if pattern != "" {
|
|
|
|
var err error
|
|
|
|
g, err = hglob.GetGlob(pattern)
|
|
|
|
if err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
for _, m := range mods {
|
|
|
|
if m.Replace != nil || m.Main {
|
|
|
|
continue
|
|
|
|
}
|
|
|
|
|
|
|
|
if g != nil && !g.Match(m.Path) {
|
|
|
|
continue
|
|
|
|
}
|
|
|
|
_, err = hugofs.MakeReadableAndRemoveAllModulePkgDir(c.fs, m.Dir)
|
|
|
|
if err == nil {
|
2020-10-21 05:17:48 -04:00
|
|
|
c.logger.Printf("hugo: cleaned module cache for %q", m.Path)
|
2020-02-19 10:59:54 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
|
2020-02-19 04:39:36 -05:00
|
|
|
func (c *Client) runVerify() error {
|
|
|
|
return c.runGo(context.Background(), ioutil.Discard, "mod", "verify")
|
|
|
|
}
|
|
|
|
|
2019-09-03 06:58:02 -04:00
|
|
|
func isProbablyModule(path string) bool {
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
return module.CheckPath(path) == nil
|
|
|
|
}
|
|
|
|
|
|
|
|
func (c *Client) listGoMods() (goModules, error) {
|
2019-09-03 06:58:02 -04:00
|
|
|
if c.GoModulesFilename == "" || !c.moduleConfig.hasModuleImport() {
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
return nil, nil
|
|
|
|
}
|
|
|
|
|
2021-08-26 11:24:52 -04:00
|
|
|
downloadModules := func(modules ...string) error {
|
|
|
|
args := []string{"mod", "download"}
|
|
|
|
args = append(args, modules...)
|
|
|
|
out := ioutil.Discard
|
|
|
|
err := c.runGo(context.Background(), out, args...)
|
|
|
|
if err != nil {
|
2022-05-02 10:07:52 -04:00
|
|
|
return fmt.Errorf("failed to download modules: %w", err)
|
2021-08-26 11:24:52 -04:00
|
|
|
}
|
|
|
|
return nil
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
}
|
|
|
|
|
2021-08-26 11:24:52 -04:00
|
|
|
if err := downloadModules(); err != nil {
|
|
|
|
return nil, err
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
}
|
|
|
|
|
2021-08-26 11:24:52 -04:00
|
|
|
listAndDecodeModules := func(handle func(m *goModule) error, modules ...string) error {
|
|
|
|
b := &bytes.Buffer{}
|
|
|
|
args := []string{"list", "-m", "-json"}
|
|
|
|
if len(modules) > 0 {
|
|
|
|
args = append(args, modules...)
|
|
|
|
} else {
|
|
|
|
args = append(args, "all")
|
|
|
|
}
|
|
|
|
err := c.runGo(context.Background(), b, args...)
|
|
|
|
if err != nil {
|
2022-05-02 10:07:52 -04:00
|
|
|
return fmt.Errorf("failed to list modules: %w", err)
|
2021-08-26 11:24:52 -04:00
|
|
|
}
|
|
|
|
|
|
|
|
dec := json.NewDecoder(b)
|
|
|
|
for {
|
|
|
|
m := &goModule{}
|
|
|
|
if err := dec.Decode(m); err != nil {
|
|
|
|
if err == io.EOF {
|
|
|
|
break
|
|
|
|
}
|
2022-05-02 10:07:52 -04:00
|
|
|
return fmt.Errorf("failed to decode modules list: %w", err)
|
2021-08-26 11:24:52 -04:00
|
|
|
}
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
|
2021-08-26 11:24:52 -04:00
|
|
|
if err := handle(m); err != nil {
|
|
|
|
return err
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
}
|
|
|
|
}
|
2021-08-26 11:24:52 -04:00
|
|
|
return nil
|
|
|
|
}
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
|
2021-08-26 11:24:52 -04:00
|
|
|
var modules goModules
|
|
|
|
err := listAndDecodeModules(func(m *goModule) error {
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
modules = append(modules, m)
|
2021-08-26 11:24:52 -04:00
|
|
|
return nil
|
|
|
|
})
|
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
|
|
|
|
// From Go 1.17, go lazy loads transitive dependencies.
|
|
|
|
// That does not work for us.
|
|
|
|
// So, download these modules and update the Dir in the modules list.
|
|
|
|
var modulesToDownload []string
|
|
|
|
for _, m := range modules {
|
|
|
|
if m.Dir == "" {
|
|
|
|
modulesToDownload = append(modulesToDownload, fmt.Sprintf("%s@%s", m.Path, m.Version))
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
if len(modulesToDownload) > 0 {
|
|
|
|
if err := downloadModules(modulesToDownload...); err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
err := listAndDecodeModules(func(m *goModule) error {
|
|
|
|
if mm := modules.GetByPath(m.Path); mm != nil {
|
|
|
|
mm.Dir = m.Dir
|
|
|
|
}
|
|
|
|
return nil
|
|
|
|
}, modulesToDownload...)
|
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
}
|
|
|
|
|
|
|
|
return modules, err
|
|
|
|
}
|
|
|
|
|
|
|
|
func (c *Client) rewriteGoMod(name string, isGoMod map[string]bool) error {
|
|
|
|
data, err := c.rewriteGoModRewrite(name, isGoMod)
|
|
|
|
if err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
if data != nil {
|
2019-07-31 02:21:17 -04:00
|
|
|
if err := afero.WriteFile(c.fs, filepath.Join(c.ccfg.WorkingDir, name), data, 0666); err != nil {
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
return err
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
func (c *Client) rewriteGoModRewrite(name string, isGoMod map[string]bool) ([]byte, error) {
|
|
|
|
if name == goModFilename && c.GoModulesFilename == "" {
|
|
|
|
// Already checked.
|
|
|
|
return nil, nil
|
|
|
|
}
|
|
|
|
|
|
|
|
modlineSplitter := getModlineSplitter(name == goModFilename)
|
|
|
|
|
|
|
|
b := &bytes.Buffer{}
|
2019-07-31 02:21:17 -04:00
|
|
|
f, err := c.fs.Open(filepath.Join(c.ccfg.WorkingDir, name))
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
if err != nil {
|
|
|
|
if os.IsNotExist(err) {
|
|
|
|
// It's been deleted.
|
|
|
|
return nil, nil
|
|
|
|
}
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
defer f.Close()
|
|
|
|
|
|
|
|
scanner := bufio.NewScanner(f)
|
|
|
|
var dirty bool
|
|
|
|
|
|
|
|
for scanner.Scan() {
|
|
|
|
line := scanner.Text()
|
|
|
|
var doWrite bool
|
|
|
|
|
|
|
|
if parts := modlineSplitter(line); parts != nil {
|
|
|
|
modname, modver := parts[0], parts[1]
|
|
|
|
modver = strings.TrimSuffix(modver, "/"+goModFilename)
|
|
|
|
modnameVer := modname + " " + modver
|
|
|
|
doWrite = isGoMod[modnameVer]
|
|
|
|
} else {
|
|
|
|
doWrite = true
|
|
|
|
}
|
|
|
|
|
|
|
|
if doWrite {
|
|
|
|
fmt.Fprintln(b, line)
|
|
|
|
} else {
|
|
|
|
dirty = true
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
if !dirty {
|
|
|
|
// Nothing changed
|
|
|
|
return nil, nil
|
|
|
|
}
|
|
|
|
|
|
|
|
return b.Bytes(), nil
|
|
|
|
}
|
|
|
|
|
|
|
|
func (c *Client) rmVendorDir(vendorDir string) error {
|
|
|
|
modulestxt := filepath.Join(vendorDir, vendorModulesFilename)
|
|
|
|
|
|
|
|
if _, err := c.fs.Stat(vendorDir); err != nil {
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
_, err := c.fs.Stat(modulestxt)
|
|
|
|
if err != nil {
|
|
|
|
// If we have a _vendor dir without modules.txt it sounds like
|
|
|
|
// a _vendor dir created by others.
|
|
|
|
return errors.New("found _vendor dir without modules.txt, skip delete")
|
|
|
|
}
|
|
|
|
|
|
|
|
return c.fs.RemoveAll(vendorDir)
|
|
|
|
}
|
|
|
|
|
|
|
|
func (c *Client) runGo(
|
|
|
|
ctx context.Context,
|
|
|
|
stdout io.Writer,
|
|
|
|
args ...string) error {
|
|
|
|
if c.goBinaryStatus != 0 {
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
stderr := new(bytes.Buffer)
|
2021-12-12 06:11:11 -05:00
|
|
|
|
|
|
|
argsv := collections.StringSliceToInterfaceSlice(args)
|
|
|
|
argsv = append(argsv, hexec.WithEnviron(c.environ))
|
|
|
|
argsv = append(argsv, hexec.WithStderr(io.MultiWriter(stderr, os.Stderr)))
|
|
|
|
argsv = append(argsv, hexec.WithStdout(stdout))
|
|
|
|
argsv = append(argsv, hexec.WithDir(c.ccfg.WorkingDir))
|
|
|
|
argsv = append(argsv, hexec.WithContext(ctx))
|
|
|
|
|
|
|
|
cmd, err := c.ccfg.Exec.New("go", argsv...)
|
2020-12-18 12:20:12 -05:00
|
|
|
if err != nil {
|
|
|
|
return err
|
|
|
|
}
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
|
|
|
|
if err := cmd.Run(); err != nil {
|
|
|
|
if ee, ok := err.(*exec.Error); ok && ee.Err == exec.ErrNotFound {
|
|
|
|
c.goBinaryStatus = goBinaryStatusNotFound
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
2020-01-30 03:08:49 -05:00
|
|
|
if strings.Contains(stderr.String(), "invalid version: unknown revision") {
|
|
|
|
// See https://github.com/gohugoio/hugo/issues/6825
|
2021-11-10 03:32:17 -05:00
|
|
|
c.logger.Println(`An unknown revision most likely means that someone has deleted the remote ref (e.g. with a force push to GitHub).
|
2021-09-17 03:34:35 -04:00
|
|
|
To resolve this, you need to manually edit your go.mod file and replace the version for the module in question with a valid ref.
|
|
|
|
|
2021-11-10 03:32:17 -05:00
|
|
|
The easiest is to just enter a valid branch name there, e.g. master, which would be what you put in place of 'v0.5.1' in the example below.
|
2021-09-17 03:34:35 -04:00
|
|
|
|
|
|
|
require github.com/gohugoio/hugo-mod-jslibs/instantpage v0.5.1
|
|
|
|
|
2021-11-10 03:32:17 -05:00
|
|
|
If you then run 'hugo mod graph' it should resolve itself to the most recent version (or commit if no semver versions are available).`)
|
2020-01-30 03:08:49 -05:00
|
|
|
}
|
|
|
|
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
_, ok := err.(*exec.ExitError)
|
|
|
|
if !ok {
|
2022-05-02 10:07:52 -04:00
|
|
|
return fmt.Errorf("failed to execute 'go %v': %s %T", args, err, err)
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
}
|
|
|
|
|
|
|
|
// Too old Go version
|
|
|
|
if strings.Contains(stderr.String(), "flag provided but not defined") {
|
|
|
|
c.goBinaryStatus = goBinaryStatusTooOld
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
2022-05-02 10:07:52 -04:00
|
|
|
return fmt.Errorf("go command failed: %s", stderr)
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
func (c *Client) tidy(mods Modules, goModOnly bool) error {
|
|
|
|
isGoMod := make(map[string]bool)
|
|
|
|
for _, m := range mods {
|
|
|
|
if m.Owner() == nil {
|
|
|
|
continue
|
|
|
|
}
|
|
|
|
if m.IsGoMod() {
|
|
|
|
// Matching the format in go.mod
|
|
|
|
pathVer := m.Path() + " " + m.Version()
|
|
|
|
isGoMod[pathVer] = true
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
if err := c.rewriteGoMod(goModFilename, isGoMod); err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
|
|
|
|
if goModOnly {
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
if err := c.rewriteGoMod(goSumFilename, isGoMod); err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
2020-09-09 15:10:28 -04:00
|
|
|
func (c *Client) shouldVendor(path string) bool {
|
|
|
|
return c.noVendor == nil || !c.noVendor.Match(path)
|
|
|
|
}
|
|
|
|
|
2020-10-29 12:14:04 -04:00
|
|
|
func (c *Client) createThemeDirname(modulePath string, isProjectMod bool) (string, error) {
|
2022-05-02 10:07:52 -04:00
|
|
|
invalid := fmt.Errorf("invalid module path %q; must be relative to themesDir when defined outside of the project", modulePath)
|
2020-10-30 05:14:08 -04:00
|
|
|
|
2020-10-29 12:14:04 -04:00
|
|
|
modulePath = filepath.Clean(modulePath)
|
2020-10-30 05:14:08 -04:00
|
|
|
if filepath.IsAbs(modulePath) {
|
|
|
|
if isProjectMod {
|
|
|
|
return modulePath, nil
|
|
|
|
}
|
|
|
|
return "", invalid
|
|
|
|
}
|
|
|
|
|
2020-10-29 12:14:04 -04:00
|
|
|
moduleDir := filepath.Join(c.ccfg.ThemesDir, modulePath)
|
|
|
|
if !isProjectMod && !strings.HasPrefix(moduleDir, c.ccfg.ThemesDir) {
|
2020-10-30 05:14:08 -04:00
|
|
|
return "", invalid
|
2020-10-29 12:14:04 -04:00
|
|
|
}
|
|
|
|
return moduleDir, nil
|
|
|
|
}
|
|
|
|
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
// ClientConfig configures the module Client.
|
|
|
|
type ClientConfig struct {
|
2019-07-31 02:21:17 -04:00
|
|
|
Fs afero.Fs
|
2020-10-21 05:17:48 -04:00
|
|
|
Logger loggers.Logger
|
2019-07-31 02:21:17 -04:00
|
|
|
|
|
|
|
// If set, it will be run before we do any duplicate checks for modules
|
|
|
|
// etc.
|
|
|
|
HookBeforeFinalize func(m *ModulesConfig) error
|
|
|
|
|
2020-09-09 10:51:13 -04:00
|
|
|
// Ignore any _vendor directory for module paths matching the given pattern.
|
|
|
|
// This can be nil.
|
|
|
|
IgnoreVendor glob.Glob
|
2019-07-31 02:21:17 -04:00
|
|
|
|
|
|
|
// Absolute path to the project dir.
|
|
|
|
WorkingDir string
|
|
|
|
|
|
|
|
// Absolute path to the project's themes dir.
|
|
|
|
ThemesDir string
|
|
|
|
|
2021-06-16 13:11:01 -04:00
|
|
|
// Eg. "production"
|
|
|
|
Environment string
|
|
|
|
|
2021-12-12 06:11:11 -05:00
|
|
|
Exec *hexec.Exec
|
|
|
|
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
CacheDir string // Module cache
|
|
|
|
ModuleConfig Config
|
|
|
|
}
|
|
|
|
|
2020-09-09 10:51:13 -04:00
|
|
|
func (c ClientConfig) shouldIgnoreVendor(path string) bool {
|
|
|
|
return c.IgnoreVendor != nil && c.IgnoreVendor.Match(path)
|
|
|
|
}
|
|
|
|
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 03:16:58 -04:00
|
|
|
type goBinaryStatus int
|
|
|
|
|
|
|
|
type goModule struct {
|
|
|
|
Path string // module path
|
|
|
|
Version string // module version
|
|
|
|
Versions []string // available module versions (with -versions)
|
|
|
|
Replace *goModule // replaced by this module
|
|
|
|
Time *time.Time // time version was created
|
|
|
|
Update *goModule // available update, if any (with -u)
|
|
|
|
Main bool // is this the main module?
|
|
|
|
Indirect bool // is this module only an indirect dependency of main module?
|
|
|
|
Dir string // directory holding files for this module, if any
|
|
|
|
GoMod string // path to go.mod file for this module, if any
|
|
|
|
Error *goModuleError // error loading module
|
|
|
|
}
|
|
|
|
|
|
|
|
type goModuleError struct {
|
|
|
|
Err string // the error itself
|
|
|
|
}
|
|
|
|
|
|
|
|
type goModules []*goModule
|
|
|
|
|
|
|
|
func (modules goModules) GetByPath(p string) *goModule {
|
|
|
|
if modules == nil {
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
for _, m := range modules {
|
|
|
|
if strings.EqualFold(p, m.Path) {
|
|
|
|
return m
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
func (modules goModules) GetMain() *goModule {
|
|
|
|
for _, m := range modules {
|
|
|
|
if m.Main {
|
|
|
|
return m
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
func getModlineSplitter(isGoMod bool) func(line string) []string {
|
|
|
|
if isGoMod {
|
|
|
|
return func(line string) []string {
|
|
|
|
if strings.HasPrefix(line, "require (") {
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
if !strings.HasPrefix(line, "require") && !strings.HasPrefix(line, "\t") {
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
line = strings.TrimPrefix(line, "require")
|
|
|
|
line = strings.TrimSpace(line)
|
|
|
|
line = strings.TrimSuffix(line, "// indirect")
|
|
|
|
|
|
|
|
return strings.Fields(line)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return func(line string) []string {
|
|
|
|
return strings.Fields(line)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
func pathVersion(m Module) string {
|
|
|
|
versionStr := m.Version()
|
|
|
|
if m.Vendor() {
|
|
|
|
versionStr += "+vendor"
|
|
|
|
}
|
|
|
|
if versionStr == "" {
|
|
|
|
return m.Path()
|
|
|
|
}
|
|
|
|
return fmt.Sprintf("%s@%s", m.Path(), versionStr)
|
|
|
|
}
|