Source maps

Enable maps in the production API

Supply a real entry filename. outputFilename controls the map's generated-file identity.

const result = await compileWithToolchain(inputCss, candidates, {
  filename: "/project/src/coordiation.css",
  outputFilename: "/project/dist/coordiation.css",
  sourceMap: true,
  toolchain: { minify: true },
});

await writeFile("dist/coordiation.css", result.css);
await writeFile("dist/coordiation.css.map", result.map);

result.map is a JSON string. result.toolchain.sourceMap is a compact machine-readable manifest of enabled state, source identities, and embedded-content policy.

Control embedded source text

Original CSS is embedded by default so DevTools can display sources without separately fetching project files.

sourceMap: {
  sourcesContent: false,
}

Disable sourcesContent when source identities and line mappings are useful but original CSS must not be embedded in the artifact.

Choose external or inline CLI output

External maps are suitable for deployed debugging. Inline maps keep local or portable output self-contained.

coordiation-css \
  -i src/coordiation.css \
  -o dist/coordiation.css \
  -c src \
  --sourcemap

coordiation-css \
  -i src/coordiation.css \
  -o dist/coordiation.css \
  -c src \
  --sourcemap-inline \
  --no-sources-content

External mode writes coordiation.css.map and adds a relative annotation to the CSS. Watch mode refreshes the map before replacing the CSS output.

Return native Vite module maps

Enable sourceMap on the official adapter. The virtual CSS loader returns Vite's conventional { code, map } result.

coordiation({
  content: ["src"],
  cssFile: "src/coordiation.css",
  sourceMap: true,
})

Compose with a PostCSS runner

When the runner requests a map, the adapter enables Coordiation mapping automatically and attaches it as the previous map for generated nodes.

const result = await postcss([coordiation({ content: ["src"] })]).process(css, {
  from: "src/app.css",
  to: "dist/app.css",
  map: { inline: false },
});

The adapter also publishes a coordiation-source-map result message for build diagnostics and agent inspection.

Inspect before describing coverage

{
  enabled: true,
  sourcesContent: true,
  sources: [
    "project/src/coordiation.css",
    "project/src/theme.css",
    "project/src/components.css"
  ]
}

The source list describes CSS origins. Scanned HTML, JSX, Vue, or .coord templates are candidate-discovery inputs and are not presented as CSS source locations.