Go plugin vs Module plugin

[jacobhokanson]

Just curious, which of these options is recommended? It seems like the go plugins method is architecture specific- is the module method not?

I want to pick whichever option will be easier to setup in ci / for others to setup on their dev environments

P.S. I was a bit confused by the documentation for these (didn't realize they were different options until I saw linters.settings.custom type reference said it could be "module" or "goplugin"). Maybe it could use a bit more detail

[ldez]

Hello,

goplugin is more complex to use because:

• You need to compile the linter as a Go plugin (require CGO)
• You need to use the exact same version of the dependencies as golangci-lint.
• You need to compile the plugin and golangci-lint with the exact same toolchain.
• It doesn't work on Windows.

module is easier to use:

• There is a dedicated command custom and a build configuration.
• The dependencies are handled like a classic Go module.

goplugin was the first plugin system inside golangci-lint, but the constraints to use it drove us to create the module plugin system.

I recommend using module.

References:

• https://pkg.go.dev/plugin
• https://golangci-lint.run/plugins/module-plugins/
• https://golangci-lint.run/plugins/go-plugins/

[jacobhokanson]

Thanks for your answer. It took me a while to understand the .golangci.yml custom linter name comes from the init() func. Is this somewhere in the docs or could it be added?

[ldez]

https://github.com/golangci/example-plugin-module-linter