first

course/12-local_development/exercises/4b-modules/multiple_choice.json

@@ -0,0 +1,8 @@
+{
+  "question": "What is an import path?",
+  "answers": [
+    "A module path + package subdirectory",
+    "An HTTP connection",
+    "A RESTful server"
+  ]
+}

course/12-local_development/exercises/4b-modules/readme.md

@@ -0,0 +1,33 @@
+# Modules
+
+Go programs are organized into *packages*. A package is a directory of Go code that's all compiled together. Functions, types, variables, and constants defined in one source file are visible to **all other source files within the same package (directory)**.
+
+A *repository* contains one or more *modules*. A module is a collection of Go packages that are released together.
+
+## A Go repository typically contains only one module, located at the root of the repository.
+
+A file named `go.mod` at the root of a project declares the module. It contains:
+
+* The module path
+* The version of the Go language your project requires
+* Optionally, any external package dependencies your project has
+
+The module path is just the import path prefix for all packages within the module. Here's an example of a `go.mod` file:
+
+```
+module github.com/bootdotdev/exampleproject
+
+go 1.20
+
+require github.com/google/examplepackage v1.3.0
+```
+
+Each module's path not only serves as an import path prefix for the packages within but *also indicates where the go command should look to download it*. For example, to download the module `golang.org/x/tools`, the go command would consult the repository located at [https://golang.org/x/tools](https://golang.org/x/tools).
+
+> An "import path" is a string used to import a package. A package's import path is its module path joined with its subdirectory within the module. For example, the module `github.com/google/go-cmp` contains a package in the directory `cmp/`. That package's import path is `github.com/google/go-cmp/cmp`. Packages in the standard library do not have a module path prefix.
+
+- Paraphrased from Golang.org's [code organization](https://golang.org/doc/code#Organization)
+
+## Do I need to put my package on GitHub?
+
+You don't *need* to publish your code to a remote repository before you can build it. A module can be defined locally without belonging to a repository. However, it's a good habit to keep a copy of all your projects on a remote server, like GitHub.