How to Resolve Dependency Conflicts When Using `GO111MODULE=on` and `github.com/junegunn/fzf`?

Trouble Loading Module Requirements with GO111MODULE=on

The issue encountered while trying to get the development branch of github.com/junegunn/fzf with GO111MODULE=on is related to a dependency conflict.

The dependency graph looks as follows:

github.com/junegunn/fzf -> github.com/gdamore/tcell -> gopkg.in/DATA-DOG/go-sqlmock.v1

GOPKG.IN/DATA-DOG/go-sqlmock version 1.3.3 introduced go modules without version suffixes, causing issues with explicit version number specification.

When attempting to get fzf@devel explicitly using -u, the dependencies get updated to their latest versions. However, go-sqlmock v1.3.3 is incompatible with this setup due to its lack of a version suffix.

The solution is to use go get github.com/junegunn/fzf without the -u flag if the intention is to work with the development branch without updating dependencies. Alternatively, use an older version of go-sqlmock with a version suffix.

The issue involving go-sqlmock 1.3.3 has been reported and a pull request exists to address it: https://github.com/gdamore/tcell/pull/267.

The above is the detailed content of How to Resolve Dependency Conflicts When Using `GO111MODULE=on` and `github.com/junegunn/fzf`?. For more information, please follow other related articles on the PHP Chinese website!