-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't install Excelize #2006
Comments
Thanks for your issue. Please read the README or documentation. Install lasted version by the following command: go get github.com/xuri/excelize/v2 |
I closed this, if you have any questions, please let me know, and you can reopen this anytime. |
go get github.com/xuri/excelize/v2 doesn't work on VS Code : That is why I used : go install github.com/xuri/excelize/v2 So I tried : go install github.com/xuri/excelize/v2@latest Thanks ! |
Please reference the documentation, there is a video tutorial in the documentation for setting up Excelize project in the Visual Studio Code. |
Ok Thank you very much ! |
Description
I'm working in the VS Code Terminal on Windows and I'm trying to install excelize
go get github.com/xuri/excelize
doesn't work ('go get' is no longer supported outside a module.) and I need to do :
go install github.com/xuri/excelize@latest
instead
go install github.com/xuri/excelize@latest
I have the issue :
version constraints conflict:
github.com/360EntSecGroup-Skylar/excelize/v2@v2.8.1: parsing go.mod:
module declares its path as: github.com/xuri/excelize/v2
but was required as: github.com/360EntSecGroup-Skylar/excelize/v2
Thanks for your help!
Describe the results you received:
Error
Describe the results you expected:
Install ok
Output of
go version
:go: github.com/xuri/excelize@latest: version constraints conflict:
github.com/xuri/excelize@v1.4.1: parsing go.mod:
module declares its path as: github.com/360EntSecGroup-Skylar/excelize
but was required as: github.com/xuri/excelize
Excelize version or commit ID:
Environment details (OS, Microsoft Excel™ version, physical, etc.):
The text was updated successfully, but these errors were encountered: