Great question—moving a legacy project with vendorized code to Go Modules doesn't have to be manual and error-prone. Here's a step-by-step guide to automate the process and get your project portable with Go Modules:

Step 1: Initialize Go Modules in Your Project Root #

First, navigate to the root directory of your project (where gowebapp.go lives) and initialize a new module. Use a meaningful module name—usually the URL of your GitHub repository (even if it's not pushed yet):

go mod init github.com/your-username/your-webapp-name

This creates a go.mod file that will track all your project's dependencies.

Step 2: Relocate Your Own Code (Critical!) #

Your business code lives in vendor/app, but in Go Modules, your own code shouldn't be in the vendor directory—that folder is meant for third-party dependencies. Move the entire app directory to your project root:

mv vendor/app ./

You can delete the now-empty vendor folder (or keep it temporarily if it has third-party packages; we'll handle those next).

Step 3: Fix Import Paths (If Needed) #

Your current imports like "app/route" are referencing the old vendorized path. With Go Modules, imports should point to your module's full path. Update all import statements to use your new module name as a prefix. For example:
Instead of:

import "app/route"

Use:

import "github.com/your-username/your-webapp-name/app/route"

To do this quickly across all files, use a bulk replace tool like sed:

sed -i 's/"app\//"github.com\/your-username\/your-webapp-name\/app\//g' gowebapp.go app/**/*.go

Step 4: Auto-Sync All Dependencies with go mod tidy #

This is the magic command you're looking for! Run:

go mod tidy

What it does automatically:

• Scans every .go file in your project to find all imported packages (both your own app/... code and the dozens of third-party packages)
• Adds all required third-party dependencies to go.mod with the correct version tags
• Generates a go.sum file to verify dependency integrity
• Removes any dependencies that are no longer used by your code

Step 5: Verify and Test #

Run your application to make sure everything works as expected:

go run gowebapp.go

If you hit any import errors, double-check that your module name and import paths match correctly.

Bonus: Use Vendor Directory (Optional) #

If you want to keep a local copy of all dependencies (like your old vendor setup), run:

go mod vendor

This will populate the vendor directory with all required dependencies, and you can run your app with:

go run -mod=vendor gowebapp.go

Alternative: Keep Old Import Paths (Local Dev Only) #

If you don't want to update import paths right now, add a replace directive to your go.mod to map the old "app/" imports to your local ./app directory:

replace app => ./app

This works for local development, but you'll want to switch to full module path imports if you plan to share or publish your code.

内容的提问来源于stack exchange，提问作者Babr