mypkg

Indeed every Linux user does a code review before pressing return on curl xpto | sh, or mypkg install.

> Trouble starts the minute you start relying on commands like this: sudo apt-get install mypkg So what's wrong with `sudo apt-get install mypkg=<version>`?

The middleware/lib does most of the work once you call `mypkg.

Is and compare to the returned err to mypkg.

If my package is at example.org/pkg/mypkg and I stop paying for my domain name for any number of reasons then that package is essentially lost.

You can also do this: import ( mypkg "github.com/user/core/adapters" ) and use mypkg.

So, you can not say "var x mypkg.unexportedType", even if you can "x:= mypkg.

Finally, I find it annoying that you can do Pkg.update("Mypkg") and Pkg.build("Mypkg") but not Pkg.test("Mypkg") (or is it the other way around, I always forget).

Return "error" and not a custom type "mypkg.

Like I’m writing a Vite plugin and it has code like this: const moduleId = "virtual:mypkg"; const resolvedModuleId = "\0" + moduleId; Unless you’ve written Vite/rollup plugins, which many folks haven’t, you’re going to appreciate a comment that at least points to some docs.

You can also do this: import ( mypkg "github.com/user/core/adapters" ) and use mypkg.

So, you can not say "var x mypkg.unexportedType", even if you can "x:= mypkg.

Finally, I find it annoying that you can do Pkg.update("Mypkg") and Pkg.build("Mypkg") but not Pkg.test("Mypkg") (or is it the other way around, I always forget).

Return "error" and not a custom type "mypkg.