npm - @telepath-computer/television - Versions diffs - 0.1.98 → 0.1.100 - Mend

@telepath-computer/television 0.1.98 → 0.1.100

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (17) hide show

package/dist/cli.cjs +444 -434
package/dist/skills/television/SKILL.md +215 -198
package/dist/skills/television-calendar/SKILL.md +99 -0
package/dist/skills/television-table/SKILL.md +89 -0
package/dist/views/markdown/manifest.json +1 -1
package/dist/web/assets/index-BteBsj8I.js +513 -0
package/dist/web/index.html +1 -1
package/package.json +1 -1
package/dist/skills/artifact-calendar/SKILL.md +0 -151
package/dist/skills/artifact-calendar/house-style.md +0 -67
package/dist/skills/artifact-table/SKILL.md +0 -217
package/dist/skills/artifact-table/house-style.md +0 -67
package/dist/views/text/index.html +0 -38
package/dist/views/text/manifest.json +0 -5
package/dist/web/assets/index-Cf-KqGge.js +0 -513
/package/dist/skills/{artifact-calendar → television-calendar}/calendar.css +0 -0
/package/dist/skills/{artifact-calendar → television-calendar}/calendar.js +0 -0

package/dist/web/index.html CHANGED Viewed

@@ -4,7 +4,7 @@
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no" />
     <title>Television</title>
-    <script type="module" crossorigin src="./assets/index-Cf-KqGge.js"></script>
+    <script type="module" crossorigin src="./assets/index-BteBsj8I.js"></script>
     <link rel="stylesheet" crossorigin href="./assets/index-DXZ2UyQf.css">
   </head>
   <body></body>

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "@telepath-computer/television",
-  "version": "0.1.98",
+  "version": "0.1.100",
   "type": "module",
   "main": "dist/cli.cjs",
   "bin": {

package/dist/skills/artifact-calendar/SKILL.md DELETED Viewed

@@ -1,151 +0,0 @@
----
-name: artifact-calendar
-description: Author self-contained HTML calendar artifacts using the bundled calendar-week elements and copied calendar assets.
----
-# Authoring a calendar week
-Before authoring the artifact, read `house-style.md` in this skill folder.
-A working-week calendar with a generated header strip, all-day band, time axis,
-and timed event grid. The agent only authors a single `<calendar-week>` plus
-flat sibling `<calendar-event>` children. The component renders the rest.
-## Required assets
-Every calendar artifact must be self-contained. Read `calendar.css` and
-`calendar.js` from this skill folder and carry them into the artifact output
-instead of referencing `/skills/artifact-calendar/...` URLs.
-For a Television internal artifact bundle, copy both files into the artifact's
-`public/` directory and reference them relatively:
-```html
-<link rel="stylesheet" href="/canonical/v1/styles.css" />
-<link rel="stylesheet" href="./calendar.css" />
-<script type="module" src="./calendar.js"></script>
-```
-For a standalone single-file HTML artifact, inline the contents of
-`calendar.css` and `calendar.js` directly into `<style>` and
-`<script type="module">` tags so the output stays self-contained.
-`calendar.js` registers the custom elements. `calendar.css` provides the
-calendar-specific chrome styling. Do not reimplement those elements yourself.
-## Markup contract
-Author exactly this surface:
-```html
-<calendar-week start-date="YYYY-MM-DD" days="N" start-hour="8">
-  <calendar-event title="..." start="..." end="..." color="blue"></calendar-event>
-  <calendar-event title="..." start="..." end="..." all-day color="purple"></calendar-event>
-</calendar-week>
-```
-`<calendar-week>` attributes:
-- `start-date` is required and must be a real `YYYY-MM-DD` date.
-- `days` is required and should usually be `5` or `7`.
-- `start-hour` is optional. Omit it unless you need a fixed initial scroll
-  position.
-`<calendar-event>` attributes:
-- `title` is required.
-- `start` is required.
-- `end` is required.
-- `all-day` is optional and presence-only. Use it only for all-day events.
-- `color` is optional. Allowed values: `red`, `orange`, `yellow`, `green`,
-  `blue`, `purple`. Omitted or unknown values fall back to the neutral default.
-## Timed vs. all-day events
-Timed events:
-- Omit `all-day`.
-- Use `YYYY-MM-DDTHH:MM` wall-clock datetimes for both `start` and `end`.
-- Keep each event within a single day.
-All-day events:
-- Include `all-day`.
-- Use date-only `YYYY-MM-DD` values for both `start` and `end`.
-- `end` is non-inclusive, following RFC 5545.
-Examples:
-- Single-day all-day holiday on Monday:
-  `start="2026-05-04" end="2026-05-05" all-day`
-- Tue–Thu offsite:
-  `start="2026-05-05" end="2026-05-08" all-day`
-- Timed design review from 11:00 to 12:30:
-  `start="2026-05-06T11:00" end="2026-05-06T12:30"`
-Repeat the non-inclusive rule when you think about date spans. A Mon–Fri trip
-is `start="2026-05-04" end="2026-05-09"`, not `end="2026-05-08"`.
-## What the component auto-renders
-Do not author any of these directly:
-- `<calendar-headers>`
-- `<calendar-day>`
-- `<calendar-allday>`
-- `<calendar-grid>`
-- `<calendar-time-axis>`
-- `<calendar-column>`
-- `<calendar-cell>`
-Those are internal chrome and CSS targets created by `<calendar-week>`.
-## Behavior to rely on
-- All-day events clip silently to the visible range.
-- All-day events stack into lanes automatically when their visible spans
-  overlap.
-- Timed events on the same day cascade to the right when their time ranges
-  overlap.
-- Malformed events are silently dropped. There is no error pill or fallback UI.
-## Content guidance
-- Make the schedule feel real. Use plausible meeting names, owners, and time
-  blocks.
-- Vary the event titles and use sensible durations.
-- Use the color palette intentionally; don't paint everything the same color.
-- Avoid placeholder text like "Lorem ipsum", "Event 1", or "Meeting".
-## Minimal complete example
-```html
-<!doctype html>
-<html lang="en">
-  <head>
-    <meta charset="UTF-8" />
-    <meta name="viewport" content="width=device-width, initial-scale=1" />
-    <title>Team Week</title>
-    <link rel="stylesheet" href="/canonical/v1/styles.css" />
-    <link rel="stylesheet" href="./calendar.css" />
-    <script type="module" src="./calendar.js"></script>
-    <style>
-      html, body { margin: 0; min-height: 100vh; }
-      calendar-week { height: 100vh; }
-    </style>
-  </head>
-  <body>
-    <calendar-week start-date="2026-05-04" days="5">
-      <calendar-event title="Holiday" start="2026-05-04" end="2026-05-05" all-day color="red"></calendar-event>
-      <calendar-event title="Standup" start="2026-05-05T09:00" end="2026-05-05T09:30" color="blue"></calendar-event>
-      <calendar-event title="Design review" start="2026-05-06T11:00" end="2026-05-06T12:30" color="purple"></calendar-event>
-    </calendar-week>
-  </body>
-</html>
-```
-## Non-goals
-- Do not author internal chrome or custom day headers.
-- Do not use timezones, UTC conversion, or seconds.
-- Do not invent interaction, editing UI, filters, or legends unless asked.

package/dist/skills/artifact-calendar/house-style.md DELETED Viewed

@@ -1,67 +0,0 @@
-# Authoring artifacts
-You're writing a single self-contained HTML artifact that will be rendered
-inside a Television viewer (or downloaded for offline viewing later). This
-skill documents the conventions you must follow.
-## House style
-Artifacts inherit a versioned, canonical stylesheet served by the
-Television runtime. Include it in `<head>`:
-```html
-<link rel="stylesheet" href="/canonical/v1/styles.css">
-```
-That stylesheet provides:
-- A CSS reset and font-face declarations (Hind variable font, loaded
-  automatically — no extra link tags needed).
-- The full design-system token catalog as CSS custom properties:
-  typography (`--text-*`, `--font-*`, `--leading-*`), spacing
-  (`--space-*`), color (`--color-*`, `--neutral-*`), radii
-  (`--radius-*`), and surfaces. The runtime source of truth is
-  `packages/ui/styles/tokens.css`; the bundle inlines it.
-- Bare-tag styling. `body`, `a`, `h1`–`h6`, `code`, `pre`, and similar
-  semantic elements have built-in styling — you do not need to add
-  classes to make them look right.
-**Lean on semantic HTML and the bare-tag styling.** Reach for `<h1>`,
-`<p>`, `<ul>`, `<code>`, etc. before inventing custom classes. Use tokens
-(`var(--space-8)`, `var(--color-text-muted)`, etc.) for any custom CSS
-you do write — never hardcoded pixel values or hex colors.
-## Document shape
-Emit a complete HTML document, not a fragment:
-```html
-<!doctype html>
-<html lang="en">
-  <head>
-    <meta charset="utf-8">
-    <title>{{title}}</title>
-    <link rel="stylesheet" href="/canonical/v1/styles.css">
-  </head>
-  <body>
-    <!-- artifact content -->
-  </body>
-</html>
-```
-## Conventions
-- **Self-contained.** By default, emit one HTML file. If the active
-  kind skill ships local CSS or JS assets, copy or inline them from the
-  skill folder so the final artifact remains self-contained without any
-  `/skills/...` runtime dependency.
-- **No arbitrary `<script>` tags.** Static HTML is the default. Only
-  include local, bundled scripts when the active kind skill explicitly
-  requires them.
-- **No external network fetches.** No CDN links, no remote images, no
-  font URLs other than what `/canonical/v1/styles.css` already includes.
-- **No inline `<style>` overrides for chrome-level concerns.** Small
-  layout-specific styles for the artifact's content are fine; redefining
-  brand colors or typography is not.
-- **Use tokens, not hardcoded values.** `padding: var(--space-12)`, not
-  `padding: 12px`. `color: var(--color-text-muted)`, not `color: #999`.

package/dist/skills/artifact-table/SKILL.md DELETED Viewed

@@ -1,217 +0,0 @@
----
-name: artifact-table
-description: Author dense Airtable-style HTML record tables using the shared Television house style.
----
-# Authoring a record table
-Before authoring the artifact, read `house-style.md` in this skill folder.
-A dense, Airtable-style table of records. Lots of cells, mixed cell types,
-structured rows. Should look crisp at a glance and read like real software,
-not a styled spreadsheet.
-## Required content
-- `<h1>` heading with a short title naming the table (e.g. "Tasks",
-  "Releases", "Customers").
-- One paragraph (1–2 sentences) describing what the table contains and
-  how many rows it has.
-- A `<table>` with:
-  - A `<thead>` row of column labels.
-  - 8–15 `<tbody>` rows of data.
-  - 4–6 columns covering a mix of cell types — at minimum:
-    - one **text** column (title / name)
-    - one **status** column (rendered as a small pill: a `<span>` with a
-      background color and rounded corners — done / open / blocked /
-      shipped etc.)
-    - one **date** column
-    - one **person** column (a name)
-    - one **numeric** or **tag** column (priority, count, label)
-  - Realistic-looking values, not "Lorem ipsum" or "Item 1, Item 2".
-## Page layout
-The artifact is a *full-width* table view, not a centered prose document.
-Do NOT wrap the content in `<main>` or any other container that
-constrains width — the table runs edge-to-edge.
-**The default is a single ungrouped table.** Only consider sections
-(see below) when the data has a categorical column that genuinely
-chunks the records into meaningful groups — most tables do not.
-Use this page structure:
-```html
-<body>
-  <header class="lead">
-    <h1>...</h1>
-    <p class="lede">...</p>
-  </header>
-  <table class="records">
-    ...
-  </table>
-</body>
-```
-The page is white throughout — no page wash, no contrasting bands. The
-hairline borders around the thead and between rows do all the visual
-work.
-- `header.lead` padding: `var(--space-32) var(--space-32) var(--space-16)`.
-- `table.records`: `width: 100%; border-collapse: collapse;`. Add
-  `font-variant-numeric: tabular-nums;` so numeric columns align.
-## Edge gutters
-The table runs full-width, but its content needs to line up with the
-title section's gutter. Achieve this by padding the *first* and *last*
-cells of every row (both `thead th` and `tbody td`):
-```css
-table.records thead th:first-child,
-table.records tbody td:first-child { padding-left: var(--space-32); }
-table.records thead th:last-child,
-table.records tbody td:last-child  { padding-right: var(--space-32); }
-```
-## Borders
-The table has hairline borders on the **top of the thead** and the
-**bottom of the last `tbody` row**, plus muted hairlines between rows.
-No vertical column rules — the table feels like a list, not a grid.
-```css
-table.records thead th {
-  border-top: 0.5px solid var(--color-border);
-  border-bottom: 0.5px solid var(--color-border);
-}
-table.records tbody td {
-  border-bottom: 0.5px solid var(--color-border-muted);
-}
-table.records tbody tr:last-child td {
-  border-bottom: 0.5px solid var(--color-border);
-}
-```
-## Cell styling
-- Use semantic `<table>` / `<thead>` / `<tbody>` / `<tr>` / `<th>` /
-  `<td>`.
-- Header row: small, muted, uppercase. `font-size: var(--text-sm);
-  text-transform: uppercase; letter-spacing: 0.04em; color:
-  var(--color-text-muted); font-weight: var(--font-weight-body);`.
-  Don't bold-bomb it.
-- Cells: `padding: var(--space-8) var(--space-12);` (tight vertical,
-  generous horizontal). `vertical-align: baseline;`.
-- Numeric and date columns: right-align via a `.num` / `.date` class
-  with `text-align: right; white-space: nowrap;`.
-- Title cell: `font-weight: 500;` so it reads as the row's primary
-  label.
-## Status pills
-Inline, rounded, with subtle backgrounds — use `color-mix()` accents at
-~14–16% opacity so they sit calmly in the row. Each status gets its own
-class (e.g. `pill-done`, `pill-in-progress`, `pill-blocked`,
-`pill-shipped`). Example:
-```css
-.pill {
-  display: inline-block;
-  padding: 1px var(--space-8);
-  border-radius: var(--radius-full);
-  font-size: var(--text-sm);
-}
-.pill-done {
-  background: color-mix(in srgb, var(--color-text-muted) 14%, transparent);
-  color: var(--color-text-muted);
-}
-.pill-in-progress {
-  background: color-mix(in srgb, royalblue 16%, transparent);
-  color: color-mix(in srgb, royalblue 80%, var(--color-text));
-}
-```
-## Sections (optional)
-**A single ungrouped table is the default. Most tables should not
-use sections.** Only break into sections when *all* of the following
-hold:
-- The data has a categorical column (status, quarter, tier, severity)
-  whose values are stable, meaningful, and the primary thing the
-  reader scans for.
-- That column has a small, fixed set of values — not many sparse ones.
-- Each section will have at least ~3 rows on average. A section of one
-  row is noise.
-- The grouping reflects how the user thinks about the data, not just
-  a sort order. If the answer is "you could just sort by it", don't
-  group.
-Examples that justify sections: tasks grouped by status when status
-*is* the lens (active vs done vs blocked); incidents by severity for
-an on-call view; releases by quarter on a roadmap.
-Examples that don't: a customer list grouped by signup month; a
-products table grouped by alphabet; a uniform list of items where
-every row is the same kind of thing. Default to one table.
-When grouping is justified, render each group as its own `<table>`
-inside a `<section class="group">`, with an `<h2>` heading above it.
-Each table repeats the column headers — grouping doesn't change the
-per-table contract, it just multiplies it.
-```html
-<header class="lead">…</header>
-<section class="group">
-  <h2>In progress</h2>
-  <table class="records">
-    <colgroup>
-      <col /><col style="width: 9rem" /><col style="width: 9rem" />
-      <col style="width: 7rem" /><col style="width: 5rem" />
-    </colgroup>
-    <thead>
-      <tr><th>Title</th><th>Status</th><th>Owner</th><th>Area</th><th class="date">Due</th></tr>
-    </thead>
-    <tbody>…</tbody>
-  </table>
-</section>
-<section class="group">
-  <h2>Done</h2>
-  <table class="records">…same colgroup, same thead…</table>
-</section>
-```
-Group heading — substantial enough to do the visual chunking on its
-own (no background separation between sections):
-```css
-section.group h2 {
-  margin: 0;
-  padding: var(--space-16) var(--space-32) var(--space-8);
-  font-size: var(--text-lg);
-  font-weight: 600;
-  color: var(--color-text);
-}
-```
-Repeat the same `<colgroup>` definition in every grouped table so
-columns line up across sections. Pick widths once based on the longest
-content across all groups. Without `<colgroup>` each table sizes its
-own columns independently and they will drift.
-Order groups so active states come before terminal states — e.g.
-"In progress" before "Done", "Open" before "Closed". The most
-actionable section reads first.
-## Non-goals
-- No filtering, sorting, search, or row selection — purely rendered.
-- No icons unless they add real meaning (an empty/filled circle for
-  status is fine; decorative emoji is not).
-- No nested tables, no expand/collapse, no sticky headers.
-- No collapse/expand on section headers — sections are visual
-  grouping only.

package/dist/skills/artifact-table/house-style.md DELETED Viewed

@@ -1,67 +0,0 @@
-# Authoring artifacts
-You're writing a single self-contained HTML artifact that will be rendered
-inside a Television viewer (or downloaded for offline viewing later). This
-skill documents the conventions you must follow.
-## House style
-Artifacts inherit a versioned, canonical stylesheet served by the
-Television runtime. Include it in `<head>`:
-```html
-<link rel="stylesheet" href="/canonical/v1/styles.css">
-```
-That stylesheet provides:
-- A CSS reset and font-face declarations (Hind variable font, loaded
-  automatically — no extra link tags needed).
-- The full design-system token catalog as CSS custom properties:
-  typography (`--text-*`, `--font-*`, `--leading-*`), spacing
-  (`--space-*`), color (`--color-*`, `--neutral-*`), radii
-  (`--radius-*`), and surfaces. The runtime source of truth is
-  `packages/ui/styles/tokens.css`; the bundle inlines it.
-- Bare-tag styling. `body`, `a`, `h1`–`h6`, `code`, `pre`, and similar
-  semantic elements have built-in styling — you do not need to add
-  classes to make them look right.
-**Lean on semantic HTML and the bare-tag styling.** Reach for `<h1>`,
-`<p>`, `<ul>`, `<code>`, etc. before inventing custom classes. Use tokens
-(`var(--space-8)`, `var(--color-text-muted)`, etc.) for any custom CSS
-you do write — never hardcoded pixel values or hex colors.
-## Document shape
-Emit a complete HTML document, not a fragment:
-```html
-<!doctype html>
-<html lang="en">
-  <head>
-    <meta charset="utf-8">
-    <title>{{title}}</title>
-    <link rel="stylesheet" href="/canonical/v1/styles.css">
-  </head>
-  <body>
-    <!-- artifact content -->
-  </body>
-</html>
-```
-## Conventions
-- **Self-contained.** By default, emit one HTML file. If the active
-  kind skill ships local CSS or JS assets, copy or inline them from the
-  skill folder so the final artifact remains self-contained without any
-  `/skills/...` runtime dependency.
-- **No arbitrary `<script>` tags.** Static HTML is the default. Only
-  include local, bundled scripts when the active kind skill explicitly
-  requires them.
-- **No external network fetches.** No CDN links, no remote images, no
-  font URLs other than what `/canonical/v1/styles.css` already includes.
-- **No inline `<style>` overrides for chrome-level concerns.** Small
-  layout-specific styles for the artifact's content are fine; redefining
-  brand colors or typography is not.
-- **Use tokens, not hardcoded values.** `padding: var(--space-12)`, not
-  `padding: 12px`. `color: var(--color-text-muted)`, not `color: #999`.

package/dist/views/text/index.html DELETED Viewed

@@ -1,38 +0,0 @@
-<!DOCTYPE html>
-<html>
-  <head>
-    <meta charset="utf-8" />
-    <title>Text view</title>
-    <style>
-      html,
-      body {
-        margin: 0;
-        padding: 0;
-        height: 100%;
-        background: #fff;
-        color: #000;
-      }
-      pre#content {
-        box-sizing: border-box;
-        margin: 0;
-        padding: 12px 16px;
-        min-height: 100%;
-        font-family: ui-monospace, SFMono-Regular, Menlo, Consolas, monospace;
-        font-size: 13px;
-        line-height: 1.5;
-        white-space: pre-wrap;
-        word-break: break-word;
-        outline: none;
-      }
-    </style>
-    <script type="module">var I=e=>{throw TypeError(e)};var _=(e,n,t)=>n.has(e)||I("Cannot "+t);var c=(e,n,t)=>(_(e,n,"read from private field"),t?t.call(e):n.get(e)),u=(e,n,t)=>n.has(e)?I("Cannot add the same private member more than once"):n instanceof WeakSet?n.add(e):n.set(e,t),y=(e,n,t,r)=>(_(e,n,"write to private field"),r?r.call(e,t):n.set(e,t),t),p=(e,n,t)=>(_(e,n,"access private method"),t);(function(){const n=document.createElement("link").relList;if(n&&n.supports&&n.supports("modulepreload"))return;for(const s of document.querySelectorAll('link[rel="modulepreload"]'))r(s);new MutationObserver(s=>{for(const o of s)if(o.type==="childList")for(const i of o.addedNodes)i.tagName==="LINK"&&i.rel==="modulepreload"&&r(i)}).observe(document,{childList:!0,subtree:!0});function t(s){const o={};return s.integrity&&(o.integrity=s.integrity),s.referrerPolicy&&(o.referrerPolicy=s.referrerPolicy),s.crossOrigin==="use-credentials"?o.credentials="include":s.crossOrigin==="anonymous"?o.credentials="omit":o.credentials="same-origin",o}function r(s){if(s.ep)return;s.ep=!0;const o=t(s);fetch(s.href,o)}})();const S=new Set(["target","currentTarget","eventPhase","defaultPrevented","isTrusted","timeStamp","srcElement","returnValue","cancelBubble","NONE","CAPTURING_PHASE","AT_TARGET","BUBBLING_PHASE","composedPath","stopPropagation","stopImmediatePropagation","preventDefault","initEvent"]);function O(e){for(const n of Object.keys(e))if(S.has(n))throw new Error(`Event payload key "${n}" is reserved; choose a different property name`)}function G(e,n){O(n);for(const t of Object.keys(n))Object.defineProperty(e,t,{value:n[t],writable:!0,enumerable:!0,configurable:!0})}function V(){class e extends Event{constructor(t,r){const{type:s,bubbles:o,cancelable:i,composed:v,...w}=r??{};if(s!==void 0)throw new Error('Do not pass "type" in init; use the constructor argument instead');super(t,{bubbles:o,cancelable:i,composed:v}),G(this,w)}}return e}class U extends globalThis.EventTarget{}function B(e,n,t){const r=e.dispose.bind(e);e.dispose=()=>{if(!n())return t(),r()}}function F(e){var t;class n extends e{constructor(...o){super(...o);u(this,t,!1);B(this,()=>c(this,t),()=>{y(this,t,!0)})}[Symbol.dispose](){this.dispose()}get disposed(){return c(this,t)}}return t=new WeakMap,n}const R="0123456789ABCDEFGHJKMNPQRSTVWXYZ",b=32,W=16,A=10,P=0xffffffffffff;var f;(function(e){e.Base32IncorrectEncoding="B32_ENC_INVALID",e.DecodeTimeInvalidCharacter="DEC_TIME_CHAR",e.DecodeTimeValueMalformed="DEC_TIME_MALFORMED",e.EncodeTimeNegative="ENC_TIME_NEG",e.EncodeTimeSizeExceeded="ENC_TIME_SIZE_EXCEED",e.EncodeTimeValueMalformed="ENC_TIME_MALFORMED",e.PRNGDetectFailure="PRNG_DETECT",e.ULIDInvalid="ULID_INVALID",e.Unexpected="UNEXPECTED",e.UUIDInvalid="UUID_INVALID"})(f||(f={}));class T extends Error{constructor(n,t){super(`${t} (${n})`),this.name="ULIDError",this.code=n}}function $(e){const n=Math.floor(e()*b)%b;return R.charAt(n)}function j(e){const n=H(),t=n&&(n.crypto||n.msCrypto)||null;if(typeof(t==null?void 0:t.getRandomValues)=="function")return()=>{const r=new Uint8Array(1);return t.getRandomValues(r),r[0]/256};if(typeof(t==null?void 0:t.randomBytes)=="function")return()=>t.randomBytes(1).readUInt8()/256;throw new T(f.PRNGDetectFailure,"Failed to find a reliable PRNG")}function H(){return X()?self:typeof window<"u"?window:typeof global<"u"?global:typeof globalThis<"u"?globalThis:null}function K(e,n){let t="";for(;e>0;e--)t=$(n)+t;return t}function k(e,n=A){if(isNaN(e))throw new T(f.EncodeTimeValueMalformed,`Time must be a number: ${e}`);if(e>P)throw new T(f.EncodeTimeSizeExceeded,`Cannot encode a time larger than ${P}: ${e}`);if(e<0)throw new T(f.EncodeTimeNegative,`Time must be positive: ${e}`);if(Number.isInteger(e)===!1)throw new T(f.EncodeTimeValueMalformed,`Time must be an integer: ${e}`);let t,r="";for(let s=n;s>0;s--)t=e%b,r=R.charAt(t)+r,e=(e-t)/b;return r}function X(){return typeof WorkerGlobalScope<"u"&&self instanceof WorkerGlobalScope}function z(e,n){const t=j(),r=Date.now();return k(r,A)+K(W,t)}function N(e){return typeof e=="object"&&e!==null}function Y(e){return!N(e)||e.type!=="content-updated"||typeof e.content!="string"?!1:!("id"in e)}function Z(e){if(!N(e)||e.type!=="response"||typeof e.id!="string")return!1;const n="result"in e&&e.result!==void 0,t="error"in e&&e.error!==void 0;return!(n===t||n&&(!N(e.result)||Object.keys(e.result).length!==0)||t&&(!N(e.error)||typeof e.error.message!="string"))}const q=V(),J=F(U);var m,E,h,d,a,L,C,D,x;class Q extends J{constructor(t=globalThis){super();u(this,a);u(this,m);u(this,E);u(this,h);u(this,d,new Map);y(this,m,t);const r=t.parent;if(!r||r===t)throw new Error("ArtifactContext: window has no parent");y(this,E,r),y(this,h,s=>p(this,a,L).call(this,s)),c(this,m).addEventListener("message",c(this,h)),p(this,a,D).call(this,{type:"ready"})}updateContent(t){p(this,a,x).call(this);const r=z(),s={type:"update-content",id:r,content:t};return new Promise((o,i)=>{c(this,d).set(r,{resolve:o,reject:i}),p(this,a,D).call(this,s)})}dispose(){c(this,m).removeEventListener("message",c(this,h));const t=[...c(this,d).values()];c(this,d).clear();for(const{reject:r}of t)r(new Error("ArtifactContext disposed"))}}m=new WeakMap,E=new WeakMap,h=new WeakMap,d=new WeakMap,a=new WeakSet,L=function(t){if(this.disposed||t.source!==c(this,E))return;const r=t.data;if(Y(r)){this.dispatchEvent(new q("content-updated",{content:r.content}));return}if(Z(r)){p(this,a,C).call(this,r);return}},C=function(t){const r=c(this,d).get(t.id);if(r){if(c(this,d).delete(t.id),t.error!==void 0){r.reject(new Error(t.error.message));return}r.resolve()}},D=function(t){c(this,E).postMessage(t,"*")},x=function(){if(this.disposed)throw new Error("ArtifactContext is disposed")};const ee=500;function te(e){const{pre:n,ctx:t}=e,r=e.debounceMs??ee;let s=null,o=null,i=null;const v=async()=>{i=null;const g=n.textContent??"";s=g;try{await t.updateContent(g),o=g}catch{const l=o??"";n.textContent=l,s=l}},w=()=>{i!==null&&clearTimeout(i),i=setTimeout(()=>{v()},r)},M=g=>{const l=g.content;s!==null&&l===s||(n.textContent=l,o=l)};return t.addEventListener("content-updated",M),n.addEventListener("input",w),{dispose(){i!==null&&(clearTimeout(i),i=null),t.removeEventListener("content-updated",M),n.removeEventListener("input",w)}}}const ne=document.getElementById("content"),re=new URLSearchParams(window.location.search).get("debugWire")==="1";re&&window.addEventListener("message",e=>{e.source===window.parent&&window.parent.postMessage({type:"__wire-observed",direction:"host-to-view",message:e.data},"*")});const se=new Q;te({pre:ne,ctx:se});
-</script>
-  </head>
-  <body>
-    <pre
-      id="content"
-      contenteditable="plaintext-only"
-      spellcheck="false"
-    ></pre>
-  </body>
-</html>

package/dist/views/text/manifest.json DELETED Viewed

@@ -1,5 +0,0 @@
-{
-  "name": "Text",
-  "description": "Renders text content as preformatted text.",
-  "accepts": ["text/plain"]
-}