Public Wrapper Around Non-Public Runtime
Some packages are intentionally public as installers or access layers while the full runtime remains outside the visible package surface.
Package
Vite Plugin OAC
The public Vite-facing wrapper around the OAC pipeline, important because it turns ontology compilation into a normal dev-server/build step.
- Runs Maker, IR-to-metadata conversion, and OSDK generation as part of Vite dev/build.
- Shows the public OAC workflow being shaped around ordinary frontend tooling rather than a separate compiler UX.
- Recent stable patches are mostly compatibility alignment; the meaningful feature is the three-stage build pipeline itself.
- Public Vite entry point into the OAC pipeline; compatibility bumps here often mirror deeper compiler-layer changes.
Relevant code
Most revealing source snippet
published: build/esm/generateOntologyAssets.js
packages/vite-plugin-oac/src/generateOntologyAssets.ts
open source file ->await ontologyJsToIr(opts);
await ontologyIrToFullMetadata(opts);
await fullMetadataToOsdk(opts);
const { stdout } = await execa("pnpm", [
"exec", "osdk", "unstable", "typescript", "generate", ...
]);Notes
Why it matters
@osdk/vite-plugin-oac matters because it does more than expose config. It explicitly orchestrates three steps: ontology source to IR, IR to full metadata, and full metadata to generated OSDK output.
That means Palantir is turning ontology-as-code into something a frontend developer can run inside a normal Vite loop, instead of treating compilation as a totally separate internal pipeline.
The recent 0.5.6 stable patch is not the interesting part. The interesting part is that this package exists at all, and that its internals openly call Maker, metadata conversion, and osdk unstable typescript generate in sequence.
Seams