I recently coded up a skeleton app to use as a starting point for projects that include a server component and a wasm (WebAssembly) client that does local work in a user's browser while communicating with the server.
The skeleton is hosted on Github (in a private repo until I think it's ready to publish). Today I decided to clone it and start an actual project. I've run into a problem with internal package imports. Briefly, the skeleton has multiple source files that import from internal packages, e.g. import "github.com/Michael-F-Ellis/skeleton/internal/common" The purpose of the internal/common package is to define structs that need to be known by both the server and the wasm component. As such, the package will be different in each application built from the skeleton and, hence, the import statements all need to be modified to reference the new project's module name, e.g., import "gitlab.com/SomeOneElse/someproject/internal/common" Is there now no way to simply refer to "internal/common" in the import statement and have the toolchain treat it as a local import. I've tried using the various argument to a replace directive in go.mod with no luck so far. What's the right way to handle this use case? -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/669b426e-5d0a-43a4-b086-e9e0c7213a9en%40googlegroups.com.
