When GoLand is upgraded from one version to the next, the deployment process adds a new set of configuration, cache, and log directories. But it does not remove the versions associated to the previous versions of the IDE, to ease rolling back to the previous version if an upgrade happens to cause an issue.
So after some time, removing these now-unused folders will regain some disk space, possibly more than 1 GB. Here are their respective locations and content on macOS:
The problemIn a GoLand 2018.3 EAP run configuration, a Makefile run configuration finds the
gobinary on macOS, but not on Ubuntu, causing make targets like this one to fail:
# Building WASM
GOARCH=wasm GOOS=js go build -o client/test.wasm client/main.go
/usr/bin/make -f (some edited path)/Makefile client/test.wasm
/bin/sh: 1: go: not found
make: *** [client/test.wasm] Error 127
Simple enough to fix...