Currently it's not possible.

My first impression is that it would require two changes:

1. a syntax to specify both the package and its version - for example something like import "some/package@v1.2" except that @ should be replaced with a character that cannot be part of a package name - anyone knows any such character?
2. a mechanism to forward the package version to go build - it should be enough to put it in the file go.mod of the plugin created on-the-fly and compiled to load the package.

this would be a very appreciated addition. A space character would not work?

Directory names can contain spaces.
Actually, at least on Linux, directory names can contain any character except ASCII 47 (i.e. forward slash '/') and ASCII 0.

Thus import "some/package\000v1.2" could technically work on Linux, and probably also on most Unix-like systems.
It's also really ugly.

I prefer that gophernotes recognize go.mod file placed in same location of notebook file.