@diagrammo/dgmo 0.50.2 → 0.51.0

package/docs/language-reference.md

@@ -10,6 +10,7 @@
 1. [Universal Constructs](#1-universal-constructs)
 2. [Universal Name Handling](#2-universal-name-handling)
    2A. [Universal Aliases (`as` keyword)](#2a-universal-aliases-as-keyword)
+   2B. [Universal Date Handling](#2b-universal-date-handling)
 3. [Sequence Diagrams](#3-sequence-diagrams)
 4. [Infrastructure Diagrams](#4-infrastructure-diagrams)
 5. [Flowchart Diagrams](#5-flowchart-diagrams)
@@ -509,6 +510,51 @@ rarely benefit. Aliases should aid comprehension, not obscure it.
 
 ---
 
+## 2B. Universal Date Handling
+
+<a id="2b-universal-date-handling"></a>
+
+Every date-bearing chart — **gantt (§13), pert (§13A), timeline (§15),
+event-line (§28), countdown (§36)** — accepts one liberal date grammar. Write
+dates however is natural; they store internally as ISO. (Family uses year-grain
+only; clock has no date input.)
+
+**Accepted forms** (all equivalent to `2026-07-04`):
+
+- `2026-07-04` — ISO, canonical, always unambiguous
+- `2026-07-04 14:30` — datetime (where the type supports a time)
+- `2026-07` / `2026` — month- / year-grain
+- `07-04` / `7/4` — numeric, **US month-first by default**
+- `Jul 4` / `July 4` / `July 4, 2026` / `4 Jul 2026` — month-name
+- `753 BCE` / `14 CE` — era-signed year (timeline)
+
+**Rarely type a year.** A bare month-day resolves via: (1) an explicit year on
+the date → (2) a `year 20XX` directive → (3) a sibling dated row (timeline/
+event-line carry forward + roll across New Year; gantt/pert anchor to the first
+full date, usually `start`) → (4) the current render year (only if the chart has
+no full date at all; emits a soft `year 20XX` hint).
+
+**Directives** (any date-bearing chart; position-independent):
+
+| Directive | Effect |
+| --------- | ------ |
+| `year 2026` | base year for bare month-days |
+| `date-order dmy` | numeric slash/dash dates read day-first (default `mdy`) |
+| `no-current-year` | a fully-bare chart errors instead of assuming this year |
+
+**TIPS (AI authoring):**
+
+- Prefer `Jul 4` or `07-04` + one `year 2026` line over repeating the ISO year
+  on every row — shorter and reproducible.
+- `7/4` is **Jul 4** (US month-first). For day-first documents add `date-order
+  dmy` once at the top; then `7/4` is **Apr 7**.
+- Month-name forms (`Jul 4`) are never ambiguous and ignore `date-order` — use
+  them when a mixed audience will read the source.
+- Existing ISO dates keep working unchanged; this is a superset, not a
+  migration.
+
+---
+
 ## 3. Sequence Diagrams
 
 <!-- TYPE:sequence -->
@@ -3782,7 +3828,7 @@ Percent is `now / target`. Over-target clamps the fill at 100% while the `%` lab
 <!-- TYPE:countdown -->
 
 <!-- TIPS start -->
-**Styling tips:** The only dynamic chart — it ticks every second and is accurate on every load, so use it for a live "N days until X" widget, not a static report. Keep the title to the event (`Trip to Japan`); the target date renders as a caption automatically. `target` is a space-separated `key value` directive (no colon): a bare date (`2026-08-21`) counts to the viewer's local midnight, a datetime or offset is honored. Default `units days` reads best for weeks/months out; use `units full` for a launch-day `Nd HH:MM:SS` clock. Set `expired` to the celebration text (`🚀 Shipped!`); after the target passes every live surface shows it and the tick stops. On images (PNG export, `.svg` via `<img>`, GitHub camo) it can't tick and shows the whole-day count baked at export time — the correct fallback.
+**Styling tips:** The only dynamic chart — it ticks every second and is accurate on every load, so use it for a live "N days until X" widget, not a static report. Keep the title to the event (`Trip to Japan`); the target date renders as a caption automatically. `target` is a space-separated `key value` directive (no colon): a bare date (`2026-08-21`) counts to midnight, a datetime or offset is honored. By default those times are **viewer-local** — each person sees their own; add `tz America/New_York` (any IANA zone, no colon) to **pin** the count so a shared launch/livestream page shows everyone the same remaining time and it doesn't shift when you carry the laptop to another zone. Default `units days` reads best for weeks/months out; use `units full` for a launch-day `Nd HH:MM:SS` clock. Set `expired` to the celebration text (`🚀 Shipped!`); after the target passes every live surface shows it and the tick stops. On images (PNG export, `.svg` via `<img>`, GitHub camo) it can't tick and shows the whole-day count baked at export time — the correct fallback.
 <!-- TIPS end -->
 
 The only *dynamic* dgmo chart: a single "N days until X" recomputed against the viewer's clock on every load and ticking every second on any live surface. Distinct from `goal` (static) — a countdown has no `now`/`target` pair, just one future instant. The renderer bakes a whole-day fallback number (the no-JS floor); a tiny page-level ticker overwrites it live and, in `units full`, upgrades it to `Nd HH:MM:SS`.
@@ -3810,12 +3856,13 @@ target 2026-08-21
 | Directive               | Effect                                                                 |
 | ----------------------- | ---------------------------------------------------------------------- |
 | `target <iso>`          | The future instant (required). `2026-08-21`, `2026-08-21T18:00`, or with a tz offset. The literal `now` resolves at render (→ immediately expired; for testing). |
+| `tz <IANA>`             | Pin authored times to a zone (`America/New_York`, `Asia/Kolkata`, `UTC`) so the count is the **same for every viewer** and doesn't drift when the host moves zones. Default viewer-local. Footer then shows the in-zone time + a `UTC±` tag. |
 | `units <days\|full>`    | `days` (default) shows whole days (ceil); `full` ticks `Nd HH:MM:SS` on live surfaces. |
 | `expired <text>`        | Shown once the target passes; the tick stops. Default `"Now!"`.        |
 
 ### Values & color
 
-A bare `YYYY-MM-DD` counts to the viewer's **local midnight**; a datetime with no offset is viewer-local; an explicit offset is honored. The trailing-token color rule (§1.5) applies to the title line (`countdown Trip to Japan blue`) and tints the figure.
+A bare `YYYY-MM-DD` counts to **midnight** and a datetime with no offset to that wall-clock time — both in the `tz` zone if one is set (`tz America/New_York`), otherwise **viewer-local**; an explicit ISO offset is always an absolute instant. Pin a `tz` when a shared page must show everyone the same countdown (a launch, a livestream); leave it off for a personal "my local deadline" widget. The trailing-token color rule (§1.5) applies to the title line (`countdown Trip to Japan blue`) and tints the figure.
 
 ### Semantics
 
@@ -3828,7 +3875,7 @@ Days mode uses `ceil` — a target later *today* reads "1 day", not "0". Full mo
 <!-- TYPE:clock -->
 
 <!-- TIPS start -->
-**Styling tips:** A live world clock — one panel per person or place, each showing the CURRENT time in its zone and ticking every second, accurate the instant the page loads. Reach for it to answer "what time is it for the crew right now": a distributed team's local times, a single collaborator's clock, or the overlap window for scheduling a call. The first line declares the type and a title (`Crew standups`). Each entry is one line, `<place> <IANA/Zone> [as <label>]`: a human-readable place, then a real IANA zone (`Europe/London`, `America/New_York`, `America/Los_Angeles`, `Asia/Tokyo`) — never a bare offset like `GMT+1`, which doesn't track daylight saving. Use `as <label>` to name the person or role behind a zone (`New York America/New_York as Dani (NY)`); the label becomes the caption. The single-clock case is common and encouraged — one title, one entry (`clock Dani` / `New York America/New_York`). Global directives are flat, no colon: `analog` for analog dials (digital is the default face), `time-24` for a 24-hour readout (12h am/pm is the default), and optional context bands `hours 9-17` + `days mon-fri` (the window accepts `HH:MM` and am/pm, e.g. `hours 8:30-17:15`) to shade each zone's working window so out-of-hours people read at a glance. `no-sun` hides the sunrise/sundown indicator (on by default). Add `hours`/`days` only when the point is scheduling overlap; drop them for a plain "current time" widget. Zones are **colorized by default** (`color-by`, default `place` — a distinct palette accent per place); reach for a semantic mode when color should *mean* something: `color-by time` or `color-by daylight` make an at-a-glance world board read as day-vs-night (order the zones west→east so the daylight sweeps across), and `color-by work` turns a standup/team board green/amber/grey by availability — it needs `hours` set. A hand-set per-zone color (`London Europe/London as UK team purple`) is a **defined** shade that always wins over the dimension, so you can pin one zone and let the rest follow. `color-by none` goes neutral. On image surfaces (PNG, `.svg` via `<img>`, GitHub camo) it can't tick and bakes the time at export — the correct graceful fallback.
+**Styling tips:** A live world clock — one panel per person or place, each showing the CURRENT time in its zone and ticking every second, accurate the instant the page loads. Reach for it to answer "what time is it for the crew right now": a distributed team's local times, a single collaborator's clock, or the overlap window for scheduling a call. The first line declares the type and a title (`Crew standups`). Each entry is one line, `<anchor> [as <label>] [color]`: name the zone once as the anchor — a plain **city name** (`London`, `NYC`, `Bombay`, `Los Angeles` — easiest, resolved through the bundled gazetteer to its canonical zone and displayed as the canonical city), a full **IANA id** (the token containing `/`, like `Europe/London` or `America/New_York`), or a **UTC/GMT offset** (`UTC`, `UTC+1`, `UTC+5:30`, `GMT+2`) which pins a **fixed** offset with no daylight-saving shift (bare `UTC`/`GMT` = +00:00, and no sun line). Use `as <label>` to name the person or role behind a zone (`New York as Dani (NY)`); the label becomes the caption and defaults to the resolved city (or the offset label for a fixed row). The single-clock case is common and encouraged — one title, one entry (`clock Dani` / `New York`). Global directives are flat, no colon: `analog` for analog dials (digital is the default face), `time-24` for a 24-hour readout (12h am/pm is the default), and optional context bands `hours 9-17` + `days mon-fri` (the window accepts `HH:MM` and am/pm, e.g. `hours 8:30-17:15`) to shade each zone's working window so out-of-hours people read at a glance. `no-sun` hides the sunrise/sundown indicator (on by default). Add `hours`/`days` only when the point is scheduling overlap; drop them for a plain "current time" widget. Zones are **colorized by default** (`color-by`, default `place` — a distinct palette accent per place); reach for a semantic mode when color should *mean* something: `color-by time` or `color-by daylight` make an at-a-glance world board read as day-vs-night (order the zones west→east so the daylight sweeps across), and `color-by work` turns a standup/team board green/amber/grey by availability — it needs `hours` set. A hand-set per-zone color (`London as UK team purple`, or just `London purple`) is a **defined** shade that always wins over the dimension, so you can pin one zone and let the rest follow. `color-by none` goes neutral. On image surfaces (PNG, `.svg` via `<img>`, GitHub camo) it can't tick and bakes the time at export — the correct graceful fallback.
 <!-- TIPS end -->
 
 The second *dynamic* dgmo chart (with `countdown`): a live board of world clocks recomputed against the viewer's clock every second. Flat syntax — the first line is `clock <Title>`; every other non-blank line is either a board-level directive (its first token is an option keyword) or a place row. Order-independent; no colons anywhere.
@@ -3847,7 +3894,7 @@ no-title                    // suppress the board title
 direction lr                // lay the panels out in a row
 color-by <place|work|daylight|time|none> // zone coloring; default place
 
-<place tokens…> <IANA/Zone> [as <label…>]
+<anchor> [as <label…>] [color]
 ```
 
 ### Example
@@ -3857,9 +3904,20 @@ clock Crew standups
 hours 9-17
 days mon-fri
 
-London        Europe/London        as UK team
-New York      America/New_York     as Dani (NY)
-Los Angeles   America/Los_Angeles  as West coast
+London        as UK team
+New York      as Dani (NY)
+Los Angeles   as West coast
+```
+
+A UTC-offset board (offsets are fixed — no DST, no sun line):
+
+```
+clock Bridge watch
+time-24
+
+London        as UK team
+UTC+5:30      as Bangalore ops
+UTC           as Servers
 ```
 
 ### Directives
@@ -3877,7 +3935,13 @@ Los Angeles   America/Los_Angeles  as West coast
 
 ### Entry grammar
 
-Each place row is `<place tokens…> <IANA/Zone> [as <label…>]`. The zone is the token containing `/` (a full IANA name like `America/New_York`); text before it is the place, and `as <label>` sets the display alias (default = place). A row that is just a zone (`Asia/Tokyo`) uses the zone's city as the place.
+Each place row is `<anchor> [as <label…>] [color]`. The **anchor** names the zone exactly once and is resolved in this order:
+
+1. **UTC/GMT offset** — `UTC`, `UTC+1`, `UTC-7`, `UTC+5:30`, `GMT+2`. A **fixed** offset with no DST (bare `UTC`/`GMT` = +00:00); renders a "no DST" marker and no sun line.
+2. **IANA id** — the token containing `/` (`Europe/London`, `America/New_York`). DST-correct.
+3. **City name** — via the bundled gazetteer (`London`, `NYC`, `Bombay`, `Los Angeles`). Resolves to the canonical IANA zone and displays the canonical city. An ambiguous name (`San Jose`) errors and lists the candidates; an unknown name is skipped with a warning and a did-you-mean.
+
+`as <label>` sets the display alias (default = the resolved city, or the offset label for a fixed row). A trailing palette color token pins the row's shade (`London as UK team purple`, or `London purple`).
 
 ### Semantics
 
@@ -4038,7 +4102,7 @@ Markers in cells are always **rendered in canonical alphabet order** (`R A C I`,
 <!-- TYPE:map -->
 
 <!-- TIPS start -->
-**Styling tips:** the zero-config map already looks good — name places and stop. When POIs fall into categories, tag them so each category gets its own color; keep place labels to the place name; leave region colorize and coastlines on unless the user asks to hide them. **For flights and airport routes, use IATA codes, not city names** — `LHR ~> JFK`, `LHR ~> DXB`, `LHR ~> SIN`, `LHR ~> HND` — the bundled airport set (large international hubs + all US commercial airports) resolves them to the right coordinates and labels them with the code. **For cities, use the exact canonical name**: "New York City" (NOT "New York"), "Washington, D.C.", etc. — a name the gazetteer doesn't have **silently drops that point** and the map just reframes around the rest, so it looks fine but is wrong. When unsure of the exact token, look it up: `dgmo map-search "<place>"` (or the `lookup_map_location` MCP tool) returns the city name or airport code to paste; fall back to coordinates (`poi Name as 40.71,-74.0`) for anything not found. **For routes/flows from a hub** (an airport's daily flights, a distribution center's shipments), write ONE edge per line and repeat the origin — never indented edges (those error). Use **arcs** (`~>`) for flights and long-haul links so the spokes separate; the connector label carries the relationship (`~daily~>`, `~2x daily~>`). Endpoints auto-create POIs, so don't add separate `poi` lines for places already in an edge. Reach for a `route` block only when the trip is an **ordered voyage** that continues stop→stop (a cruise itinerary), not a set of independent routes from one origin.
+**Styling tips:** the zero-config map already looks good — name places and stop. When POIs fall into categories, tag them so each category gets its own color; keep place labels to the place name; leave region colorize and coastlines on unless the user asks to hide them. **For flights and airport routes, use IATA codes, not city names** — `LHR ~> JFK`, `LHR ~> DXB`, `LHR ~> SIN`, `LHR ~> HND` — the bundled airport set (large international hubs + all US commercial airports) resolves them to the right coordinates and labels them with the code. **For cities, use the exact canonical name**: "New York City" (NOT "New York"), "Washington, D.C.", etc. — a name the gazetteer doesn't have **silently drops that point** and the map just reframes around the rest, so it looks fine but is wrong. When unsure of the exact token, look it up: `dgmo map-search "<place>"` (or the `lookup_map_location` MCP tool) returns the city name or airport code to paste; fall back to coordinates (`poi Name as 40.71,-74.0`) for anything not found. **For routes/flows from a hub** (an airport's daily flights, a distribution center's shipments), write ONE edge per line and repeat the origin — never indented edges (those error). Use **arcs** (`~>`) for flights and long-haul links so the spokes separate; the connector label carries the relationship (`~daily~>`, `~2x daily~>`). Endpoints auto-create POIs, so don't add separate `poi` lines for places already in an edge. Reach for a `route` block only when the trip is an **ordered voyage** that continues stop→stop (a cruise itinerary), not a set of independent routes from one origin. **For a "what time is it at each office" map**, flag each POI with `clock` — the zone comes from the place automatically, so just `poi Denver clock`; add `hours 9-17` + `days mon-fri` for open/closed dots, and `clock: <IANA>` only on bare-coordinate pins. Use `label:` (not `as`) for a multi-word office name.
 <!-- TIPS end -->
 
 Geographic concept maps: highlight/shade political subdivisions, drop points of interest (POIs), and connect them with routes or edges. For "share a concept" business maps, not cartography. Renders at a fixed, auto-fit position — no pan/zoom. Basemap and viewport are **inferred from the content you reference** — most maps need no directives. v1 boundaries: world countries + US states.
@@ -4109,9 +4173,28 @@ poi Austin red                      # direct marker color (trailing token, §1.5
 ```
 
 - **Coordinates are positional** — two leading signed numbers (lat then lon); cities never start with a number.
-- `size:` scales marker area (use `poi-size <label>` for the legend key). A trailing color (`poi Austin red`) sets the marker fill directly — winning over a tag color and the default orange. POI properties: `label`, `size`, `style`, applied tag alias, `as`. No `icon` in v1.
+- `size:` scales marker area (use `poi-size <label>` for the legend key). A trailing color (`poi Austin red`) sets the marker fill directly — winning over a tag color and the default orange. POI properties: `label`, `size`, `style`, applied tag alias, `as`, `clock`. No `icon` in v1.
 - Coord-positioned or relabeled POIs take `as <alias>` for route/edge references; named POIs are referenced by name.
 
+### Local-time cards (`clock`)
+
+Flag a POI with `clock` and it grows a **live local-time card** above the marker — for a team/office map that shows what time it is at each site.
+
+```
+map Team offices
+hours 9-17                          # per-pin availability window (open/closed dot)
+days mon-fri
+poi San Francisco clock             # zone auto-derived from the place
+poi London clock
+poi Bengaluru clock
+poi 1.29 103.85 as SG clock: Asia/Singapore   # bare-coord pin names its zone
+```
+
+- **The place picks the zone — don't type it.** A named city derives its IANA zone from the gazetteer (correct by construction, e.g. Austin → Central). Only a **bare-coordinate** pin needs the valued form `clock: <zone>` — an IANA id (`Asia/Tokyo`) or a fixed offset (`clock: UTC+9`, no DST). The valued form also *overrides* a city, but a mismatch warns (you almost never want it).
+- `hours 9-17` + `days mon-fri` (map-level) give a status dot per pin — green open / amber opening soon / hollow closed·weekend — evaluated in **each pin's own zone**.
+- Use `label:` for a multi-word office name (`poi Los Angeles clock, label: El Segundo`); the `as` alias is a single word and doesn't render.
+- The card ticks every second on live surfaces and bakes a snapshot for PNG/SVG. It shows the weekday only when the pin's day differs from the viewer's.
+
 ### Routes & connectors
 
 `route <origin>` — an ordered, auto-numbered voyage; the origin gets a distinct marker, and the header takes **no shape option**. Each indented line is a `<arrow> destination` leg that continues from the previous stop, using the same indented arrow idiom as a sitemap — a leg is an edge (in-arrow label, `width:` thickness, and the **arrow glyph alone sets shape**: `-…->` straight, `~…~>` arc, mixable per leg). The **arrow is required and must be directional** — a bare destination errors, and so does an undirected `--`/`~~` glyph (a voyage always flows forward; use `->`/`~>`). A **tag on a leg colours the LINE** (categorical leg-type colouring — flights vs cruises vs trains); `label:`/`as` still name the destination stop. Repeat the origin as a leg's destination to close a loop (no second marker):

package/gallery/fixtures/clock.dgmo

@@ -3,6 +3,6 @@ hours 9-17
 days mon-fri
 color-by work
 
-London        Europe/London        as UK team
-New York      America/New_York     as Dani (NY)
-Los Angeles   America/Los_Angeles  as West coast
+London as UK team
+New York as Dani (NY)
+Los Angeles as West coast

package/gallery/fixtures/countdown-tz.dgmo

@@ -0,0 +1,5 @@
+countdown The Black Pearl sets sail
+target 2026-09-01T18:00
+tz America/New_York
+units full
+expired 🏴‍☠️ Anchors aweigh!

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@diagrammo/dgmo",
-  "version": "0.50.2",
+  "version": "0.51.0",
   "description": "DGMO diagram markup language — parser, renderer, and color system",
   "license": "MIT",
   "repository": {

package/dist/dgmo-router-CE2G67FV.js

@@ -1,84 +0,0 @@
-import {
-  CHART_TYPE_DESCRIPTIONS,
-  chartTypeParsers,
-  getAllChartTypes,
-  getRenderCategory,
-  isExtendedChartType,
-  knownChartTypeIds,
-  looksLikeC4,
-  looksLikeGantt,
-  parseDgmo,
-  parseDgmoChartType
-} from "./chunk-KQ57MHRO.js";
-import "./chunk-Q4V4XQWV.js";
-import "./chunk-BTUTZMPT.js";
-import "./chunk-YNRDWYZP.js";
-import "./chunk-3XPUDB7B.js";
-import "./chunk-QXKWYZNR.js";
-import "./chunk-PGEGPSCZ.js";
-import "./chunk-3UIKSPFB.js";
-import "./chunk-BDXC7MDK.js";
-import "./chunk-XEGTMVYY.js";
-import "./chunk-I2WKW7C7.js";
-import "./chunk-TSA237IM.js";
-import "./chunk-6IAA2QQ2.js";
-import "./chunk-6HJBFVLO.js";
-import "./chunk-3P2DKJCG.js";
-import "./chunk-3LKM6FMW.js";
-import "./chunk-XJLKLU4D.js";
-import "./chunk-7L3R6I3U.js";
-import "./chunk-NNAAJVBU.js";
-import "./chunk-VUJGMJE6.js";
-import "./chunk-C2CVAM3U.js";
-import "./chunk-GKC3HILQ.js";
-import "./chunk-U2HGPLZS.js";
-import "./chunk-DSWVNQVS.js";
-import "./chunk-DZXYF2F5.js";
-import "./chunk-XHVV4NVW.js";
-import "./chunk-OMNGQPEZ.js";
-import "./chunk-VBYSIOOY.js";
-import "./chunk-QQJUTGQH.js";
-import "./chunk-SXRTRMEE.js";
-import "./chunk-NU3XLTGP.js";
-import "./chunk-OTQKUHRS.js";
-import "./chunk-SQLNBA64.js";
-import "./chunk-EAMEADTV.js";
-import "./chunk-L3UHP6TD.js";
-import "./chunk-USZW2HHU.js";
-import "./chunk-HTMN2Z6U.js";
-import "./chunk-I7F2A35O.js";
-import "./chunk-6BFZKBGD.js";
-import "./chunk-3Y2DRD7S.js";
-import "./chunk-QROYX7TT.js";
-import "./chunk-IYULMRBE.js";
-import "./chunk-R3XI2VC7.js";
-import "./chunk-P6T66CCZ.js";
-import "./chunk-BH3UYK36.js";
-import "./chunk-C3Z4DX3V.js";
-import "./chunk-FJUNPCYI.js";
-import "./chunk-GBE54KY6.js";
-import "./chunk-I46X5VUA.js";
-import "./chunk-2C56LEML.js";
-import "./chunk-NXMESY4J.js";
-import "./chunk-GL5UZ6NY.js";
-import "./chunk-SCHXJTZL.js";
-import "./chunk-FMDSF3OV.js";
-import "./chunk-FFUN5D66.js";
-import "./chunk-NOTA6TEI.js";
-import "./chunk-OTAL43EH.js";
-import "./chunk-TLVIHFRO.js";
-import "./chunk-CXK4DZH3.js";
-import "./chunk-5WRI5ZAA.js";
-export {
-  CHART_TYPE_DESCRIPTIONS,
-  chartTypeParsers,
-  getAllChartTypes,
-  getRenderCategory,
-  isExtendedChartType,
-  knownChartTypeIds,
-  looksLikeC4,
-  looksLikeGantt,
-  parseDgmo,
-  parseDgmoChartType
-};
-//# sourceMappingURL=dgmo-router-CE2G67FV.js.map

package/dist/dimensions-OTBKC5M6.js

@@ -1,22 +0,0 @@
-import {
-  mapContentAspect,
-  mapExportDimensions
-} from "./chunk-TN35C5KM.js";
-import "./chunk-LE4MYMLI.js";
-import "./chunk-I5IGB56C.js";
-import "./chunk-HGN652MU.js";
-import "./chunk-7UEMZREK.js";
-import "./chunk-A4GOY3PE.js";
-import "./chunk-HQCHYB5F.js";
-import "./chunk-5LWQH6QV.js";
-import "./chunk-P6T66CCZ.js";
-import "./chunk-FJUNPCYI.js";
-import "./chunk-OTAL43EH.js";
-import "./chunk-TLVIHFRO.js";
-import "./chunk-CXK4DZH3.js";
-import "./chunk-5WRI5ZAA.js";
-export {
-  mapContentAspect,
-  mapExportDimensions
-};
-//# sourceMappingURL=dimensions-OTBKC5M6.js.map

package/dist/layout-6RDJHS6E.js

@@ -1,9 +0,0 @@
-import {
-  layoutWireframe
-} from "./chunk-6IUAK7RZ.js";
-import "./chunk-5LWQH6QV.js";
-import "./chunk-5WRI5ZAA.js";
-export {
-  layoutWireframe
-};
-//# sourceMappingURL=layout-6RDJHS6E.js.map

package/dist/layout-J36454XU.js

@@ -1,14 +0,0 @@
-import {
-  layoutOrg
-} from "./chunk-IUMPEA64.js";
-import "./chunk-HQCHYB5F.js";
-import "./chunk-5LWQH6QV.js";
-import "./chunk-FJUNPCYI.js";
-import "./chunk-OTAL43EH.js";
-import "./chunk-TLVIHFRO.js";
-import "./chunk-CXK4DZH3.js";
-import "./chunk-5WRI5ZAA.js";
-export {
-  layoutOrg
-};
-//# sourceMappingURL=layout-J36454XU.js.map

package/dist/layout-LD6XTLD6.js

@@ -1,14 +0,0 @@
-import {
-  layoutSitemap
-} from "./chunk-VDOOQZUD.js";
-import "./chunk-HQCHYB5F.js";
-import "./chunk-5LWQH6QV.js";
-import "./chunk-FJUNPCYI.js";
-import "./chunk-OTAL43EH.js";
-import "./chunk-TLVIHFRO.js";
-import "./chunk-CXK4DZH3.js";
-import "./chunk-5WRI5ZAA.js";
-export {
-  layoutSitemap
-};
-//# sourceMappingURL=layout-LD6XTLD6.js.map

package/dist/parser-4WQQQXCG.js

@@ -1,13 +0,0 @@
-import {
-  parseEventLine
-} from "./chunk-HTMN2Z6U.js";
-import "./chunk-I7F2A35O.js";
-import "./chunk-FJUNPCYI.js";
-import "./chunk-OTAL43EH.js";
-import "./chunk-TLVIHFRO.js";
-import "./chunk-CXK4DZH3.js";
-import "./chunk-5WRI5ZAA.js";
-export {
-  parseEventLine
-};
-//# sourceMappingURL=parser-4WQQQXCG.js.map

package/dist/renderer-UYMQQCJK.js

@@ -1,24 +0,0 @@
-import {
-  renderMap,
-  renderMapForExport
-} from "./chunk-3LH5CLP4.js";
-import "./chunk-LE4MYMLI.js";
-import "./chunk-I5IGB56C.js";
-import "./chunk-HEVYAHLW.js";
-import "./chunk-HGN652MU.js";
-import "./chunk-7UEMZREK.js";
-import "./chunk-A4GOY3PE.js";
-import "./chunk-6KFWC4CO.js";
-import "./chunk-HQCHYB5F.js";
-import "./chunk-5LWQH6QV.js";
-import "./chunk-P6T66CCZ.js";
-import "./chunk-FJUNPCYI.js";
-import "./chunk-OTAL43EH.js";
-import "./chunk-TLVIHFRO.js";
-import "./chunk-CXK4DZH3.js";
-import "./chunk-5WRI5ZAA.js";
-export {
-  renderMap,
-  renderMapForExport
-};
-//# sourceMappingURL=renderer-UYMQQCJK.js.map

package/dist/renderer-radial-F7X5F2VU.js

@@ -1,21 +0,0 @@
-import {
-  renderTreemapRadial,
-  renderTreemapRadialForExport
-} from "./chunk-MCZ5LBZD.js";
-import "./chunk-PFHVU7UA.js";
-import "./chunk-HEVYAHLW.js";
-import "./chunk-7UEMZREK.js";
-import "./chunk-6KFWC4CO.js";
-import "./chunk-HQCHYB5F.js";
-import "./chunk-5LWQH6QV.js";
-import "./chunk-P6T66CCZ.js";
-import "./chunk-FJUNPCYI.js";
-import "./chunk-OTAL43EH.js";
-import "./chunk-TLVIHFRO.js";
-import "./chunk-CXK4DZH3.js";
-import "./chunk-5WRI5ZAA.js";
-export {
-  renderTreemapRadial,
-  renderTreemapRadialForExport
-};
-//# sourceMappingURL=renderer-radial-F7X5F2VU.js.map