Nate Finch

Hmm that version should be fine. Can you run `mage -debug -l` in the directory with the magefile and output the results here? That may tell us more. The magefile...

That second compiled way faster, in only 184ms, compared to the first one's 914ms. That's the built-in go build cache doing the right thing, and not actually rebuilding. So, i...

Ahh yeah, how it works needs some updating. Thanks for pointing that out... I hate having out-of-date docs. As for giving you an option... that's certainly possible. WIth an environment...

You can set an environment variable MAGEFILE_VERBOSE=true to have verbose always on. Most anything I thought someone might want always on, I made available from an environment variable. See https://magefile.org/environment/...

Mage doesn't suppress all output by default, btw. There's effectively two ways to output - if you use the stdlib `log` package, that is only displayed if you use the...

It doesn't suppress stderr. It sets the `log` package to use io.Discard by default, and sets it to use stderr when you run with -v. In hindsight, that may have...

So, I believe this is fixed using the MAGEFILE_HASHFAST environment variable, which will only rebuild if one of the magefiles changes. This should make running mage much faster on windows....

Give that a try and see if it does what you need it to do. (and I'll make a separate issue for the import naming, because that's 100% valid).

What linter is complaining about no main function, do you know? Honestly, that seems like a pretty unhelpful linter, since the compiler will tell you that you have no main...

Ahh, I figured it out. VSCode defaults to "build on save". Which I personally don't like, so I always turn it off. `"go.buildOnSave": "off"`