Go modules overview - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to initialize a new Go module.

Go

go [1] init example.com/mymodule

Drag options to blanks, or click blank then click option'

Amod

Binitmod

Cmodule

Dstart

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'go module init' instead of 'go mod init'.

Using 'go init' without 'mod'.

The correct command to initialize a new Go module is go mod init.

2fill in blank

medium

Complete the code to add a dependency to your Go module.

Go

go [1] get github.com/gin-gonic/gin@v1.7.7

Drag options to blanks, or click blank then click option'

Amod

Bget

Cinstall

Dadd

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'go mod install' which is not a valid command.

Using 'go add' which does not exist in Go tooling.

The command go get is used to add or update dependencies in a Go module.

3fill in blank

hard

Fix the error in the command to tidy the module dependencies.

Go

go mod [1]

Drag options to blanks, or click blank then click option'

Atidy

Bclean

Cfix

Dupdate

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'go mod clean' which is not a valid command.

Using 'go mod update' which does not exist.

The go mod tidy command cleans up unused dependencies and adds missing ones.

4fill in blank

hard

Fill both blanks to print the current module's path and version.

Go

go [1] [2]

Drag options to blanks, or click blank then click option'

Alist

Bmod

C-m

Dinfo

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'go mod -m' which is not a valid command.

Using 'go mod info' which is not a valid flag.

The command go list -m lists the main module's path and version.

5fill in blank

hard

Fill both blanks to upgrade a dependency to the latest version.

Go

go [1] github.com/pkg/errors@[2]

Drag options to blanks, or click blank then click option'

Aget

Bmod

Clatest

Dupgrade

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'go mod get' which is not a valid command.

Using 'latest' without '@' symbol.

The command go get github.com/pkg/errors@latest upgrades the dependency to the latest version.

Practice

1. What is the main purpose of Go modules in a Go project?

easy

A. To compile Go code faster

B. To manage project dependencies and versions easily

C. To replace the Go compiler

D. To write Go code without packages

Solution

1. Step 1: Understand what Go modules do and compare options

   Go modules help manage dependencies and versions in a Go project. Only "To manage project dependencies and versions easily" correctly describes this purpose; others are unrelated.

2. Final Answer:

   To manage project dependencies and versions easily -> Option B

3. Quick Check:

   Go modules = dependency management [OK]

Hint: Remember: modules manage dependencies and versions [OK]

Common Mistakes:

• Thinking modules speed up compilation
• Confusing modules with compiler tools
• Believing modules remove packages

2. Which command initializes a new Go module in your project directory?

easy

A. go mod init

B. go build

C. go run

D. go get

Solution

1. Step 1: Identify the command to start a module and check others

   The command go mod init creates a new module in the current directory. go build compiles code, go run runs code, and go get fetches packages, so they don't initialize modules.

2. Final Answer:

   go mod init -> Option A

3. Quick Check:

   Initialize module = go mod init [OK]

Hint: Init module with 'go mod init' command [OK]

Common Mistakes:

• Using 'go build' to start a module
• Confusing 'go get' with module initialization
• Trying 'go run' to create modules

3. What does the command go mod tidy do when run in a Go module project?

medium

A. It compiles the project

B. It deletes the go.mod file

C. It runs all tests

D. It removes unused dependencies and adds missing ones

Solution

1. Step 1: Understand the purpose of 'go mod tidy' and compare options

   This command cleans the module dependencies by removing unused ones and adding any missing required dependencies. Options A, C, and D describe unrelated actions like compiling, testing, or deleting files.

2. Final Answer:

   It removes unused dependencies and adds missing ones -> Option D

3. Quick Check:

   go mod tidy = clean dependencies [OK]

Hint: Use 'go mod tidy' to clean dependencies [OK]

Common Mistakes:

• Thinking it compiles code
• Assuming it runs tests
• Believing it deletes module files

4. You ran go mod init myproject but got an error saying "go.mod file already exists". What is the likely cause?

medium

A. The Go compiler is not installed

B. You need to run 'go mod tidy' first

C. You already have a go.mod file in the directory

D. You must delete the main.go file first

Solution

1. Step 1: Understand the error and check other options

   The error "go.mod file already exists" means the module file is already present in the directory. Running 'go mod tidy' or deleting main.go won't fix this. The compiler installation is unrelated.

2. Final Answer:

   You already have a go.mod file in the directory -> Option C

3. Quick Check:

   Existing go.mod file causes this error [OK]

Hint: Check if go.mod already exists before init [OK]

Common Mistakes:

• Trying to tidy before init
• Assuming compiler missing causes error
• Deleting unrelated files to fix error

5. You want to share your Go project with others and ensure they get the exact dependencies you used. Which two commands should you run to prepare your project? (Choose the best pair)

hard

A. go mod vendor and go mod tidy

B. go build and go run

C. go get and go test

D. go mod init and go mod tidy

Solution

1. Step 1: Identify commands to prepare modules for sharing and evaluate options

   go mod vendor copies dependencies into the vendor directory, ensuring exact versions are included, and go mod tidy cleans dependencies to ensure correctness. go mod init creates the module file but is usually done once at project start. Other options do not prepare dependencies for sharing.

2. Final Answer:

   go mod vendor and go mod tidy -> Option A

3. Quick Check:

   Vendor + tidy prepare exact dependencies for sharing [OK]

Hint: Use 'go mod vendor' and 'go mod tidy' before sharing [OK]

Common Mistakes:

• Using build or run commands for module setup
• Confusing get or test with module preparation
• Relying only on init and tidy without vendoring