Workaround for Go Monorepos embedding NextJS?

[abraithwaite]

When embedding a NextJS into a Go monorepo, it breaks a lot of workflows using ./... syntax:

17:55:27 $ go build ./...
pattern ./...: directory app/node_modules/@vercel/fun/dist/src/runtimes/go1.x is contained in a module that is not one of the workspace modules listed in go.work. You can add the module to the workspace using:
        go work use .

Do you know of any good workarounds for this? Would love to not have to delete node_modules just to work on the Go side of the project.