Essential Go Packages  Edit on GitHub      File Issue

Package naming best practices

It’s best if package name is the same as the name of last path element of import path.

If your GitHub account is and you’re writing package markdown, it’s import path should be

A common mistake is to include go as part of import path e.g. naming the package markdown and giving it import path

  ↑ ↓ to navigate     ↵ to select     Esc to close