Maker TypeScript Discovery Boundary
In the public materials reviewed for this repo, Maker exposes a function-discovery path whose standalone install workflow is not clearly documented.
Package
The public ontology-as-code DSL; important because it kept expanding from object definitions into actions, imports, discovery, and compiler-facing workflows.
Relevant code
published: build/esm/api/defineFunction.js
packages/maker/src/api/defineFunction.ts
open source file ->// generalized snippet; identifiers intentionally redacted
let cachedDiscoverer = null;
async function loadDiscoverer() {
try {
const module = await import("discovery-runtime");
cachedDiscoverer = module.FunctionDiscoverer;
return cachedDiscoverer;
} catch {
return null;
}
} Notes
Maker is the package to watch if you want the public face of Palantir’s ontology-as-code strategy.
What makes it significant is how quickly it expanded. The changelog shows a steady move from object definitions into actions-as-code, links-as-code, imports, interface actions, direct datasources, PSG handling, custom decimal/value formatting, and query function discovery.
That means Maker is no longer just a declarative DSL for ontology shape. It is increasingly the public authoring front-end for a broader compiler pipeline.
The important caveat is that its TypeScript function-discovery path is still not fully packaged as a self-contained public workflow, so one of the most interesting new flows still crosses a boundary outside the main public package surface.
Maker is both a substantial public DSL and the clearest example of a public/private seam in this package set.
Seams
In the public materials reviewed for this repo, Maker exposes a function-discovery path whose standalone install workflow is not clearly documented.