server VS lo

You still end up with the same problem, though, just in a container instead of directly on your computer's filesystem. The root issue is that if you are working on two modules where one depends on the other, say github.com/yourname/server and github.com/yourname/client, the compiler (and gopls) is checking your function calls, etc. against the version in the repository, not the version you have on your computer that you just modified. This means that you would have to make a change, commit it to the repo, then do go mod download to get the changes, and then check to see if they work.

There is, in fact a Lodash-like package for Go: https://github.com/samber/lo

What's really maps and filters? All I see is loops hidden in JavaScript runtime with different names but yes, it doesn't hurt to write few readable Go code for every project, when I started Go I used something like Samber/lo this is a worthy competitor you can install in every project and make use of it😜, another thing is: you have pure go code (no type definitions) so you can easily jump right into the code to see how it's done and learn

This library is useful even in testing https://github.com/samber/lo

If you are curious, try looking at github.com/samber/lo and github.com/samber/mo packages if you get a chance.

mostly this https://github.com/samber/lo

Any different then what is provided by https://github.com/samber/lo?

otherwise this library has some success for some operations: https://github.com/samber/lo - it's a bit of tooling around searching/filtering and such, you'll need to dig a bit more if you need vecdeque, heaptree and such.

case in point, lo