-
When trying to go get `go-colorable` from `gopkg`, I'm currently getting this message (using Go 1.12):
```
go get -u gopkg.in/mattn/go-colorable.v0
go: gopkg.in/mattn/go-colorable.v0@v0.1.1: go.m…
-
### Go version
go version go1.23.2 darwin/arm64
### Output of `go env` in your module/workspace:
```shell
N/A
```
### What did you do?
I happened to know that `go mod tidy -diff` was [added in 1…
-
Go modules requires all v2 and later major versions to have import paths ending with `/v2` etc: https://blog.golang.org/v2-go-modules.
However, f2aed9ee205d62d45c55cfabbfd26342f8526862 added go.mod…
-
This is a fantastic library, thank you!
One suggestion: it would become more versatile if the code was updated to support Go modules.
gmosx updated
5 years ago
-
It might be time to start considering support for Go modules. Suggestions and support are welcome.
-
Add support for [Go Modules](https://github.com/golang/go/wiki/Modules).
-
### Prerequisites
- [x] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [x] I have already [searched in existing i…
-
In the transcript below, there is no go line in the go.mod.
Builds say I can't use post-Go 1.16 features, but then when I say
"go get go@1.21.0" (using a sufficiently old version so as not to break an…
-
Expecte when run `yaegi` in a folder that contains `go.mod`, one can use `import` to import the packages defined in the module in `go.mod`. Currently when I do that, it will report `unable to find sou…
-
Support go module versioning conventions and when used don't redirect to gopkg.in/mail.v2
https://github.com/golang/go/wiki/Modules#semantic-import-versioning