jschoubben
71a35a6376
The delivery repository's contracts and SDK live under modules/ as mesh-delivery-contracts and mesh-delivery-sdk, their Go module paths renamed to match the folders (the TypeScript names already did), and every importer in mesh-delivery, mesh-catalog, mesh-host, mesh-tools and mesh-sdk follows in the same group: a design as it should be, one path per module, checked by the group's check building every importer. Builds: design 47 G §427, §88 Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
15 lines
765 B
Go
15 lines
765 B
Go
package buildstep
|
|
|
|
import "git.novox.be/novox/mesh-sdk/go/catalogue"
|
|
|
|
// LauncherSuffix is what a TypeScript entrypoint's launcher is called beside it: index.js is started as
|
|
// index.serve.mjs (novox/hq ADR 0193), an ES module by its own extension whatever the bundle's package.json says.
|
|
const LauncherSuffix = catalogue.LauncherSuffix
|
|
|
|
// Launchers are the launchers a bundle's build writes, by entrypoint, relative to the bundle's root
|
|
// (catalogue.Launchers): the one rule mesh-build-node, build-agent, the controller and a node taking in a build share
|
|
// (R4e, issue 1126), so the name a build writes is the name a reader expects.
|
|
func Launchers(language string, entrypoints []string) map[string]string {
|
|
return catalogue.Launchers(language, entrypoints)
|
|
}
|