hof/create: support @org/project

[verdverm]

What feature would you like?

hof create @hof/{cli,rest,app}

would be equivalent to

hof create github.com/hofstadter-io/{cli,rest,app}

basically a namespace shorthand

• probably want to avoid having them defined in hof, besides for hof
• want users to be able to config at system level, like module remotes & mirrors

hof/config command incoming?

[verdverm]

there is some concept of "vanity" url in CUE's module proposal (upcoming), though what that is, is still unclear

In JS ecosystem, there are a bunch of @<name>/<thing>'s around, and it is not always clear what this is referring to, especially with dependencies an imports.

One thing that is nice, in NextJS, is being able to set multiple @/<path>: <path-to> setting to simplify internal package references.

What we are talking about here is a similar, configurable shorthand like NextJS, but for create args only, flow and gen already have something like this naturally, but create starts from nothing (for now) so we wouldn't have project level configuration available. This would have to be configured at the system or user level. The main idea is to make it easier for groups who share app-kits (new name for creator content or generators+flows), to have an easy to read, remember, and type name. The driver here is internal company devx... "you just need to hof create @my-co/<foo> bar baz to do that thing"

I don't think we want external imports or dependencies to start showing up everywhere like the JS ecosystem. At the same time, it could be interesting to ponder what import modules and types separately, like the JS ecosystem, might mean for the CUE module proposal.