@samva/markup 0.15.1 → 0.17.0

package/dist/whatsapp.js

@@ -1,4 +1,4 @@
-import { a as jsx, n as Fragment } from "./jsx-runtime-CBlexoeR.js";
+import { a as jsx, n as Fragment } from "./jsx-runtime-qL19u3Fy.js";
 //#region src/whatsapp.ts
 const fragment = (children) => jsx(Fragment, { children });
 /**

package/generated/contract.json

@@ -1,6 +1,6 @@
 {
   "contract": 1,
-  "irVersion": 1,
+  "compiledTemplateVersion": 1,
   "template": {
     "extension": ".tsx",
     "directories": ["templates", "emails"],
@@ -14,7 +14,7 @@
     "emailBody": "{ subject, preheader?, body }, each a function of the validated input",
     "schema": "Any Standard JSON Schema converter, or a literal jsonSchema<Input>({ ... }); portable JSON Schema 2020-12. It validates every send and drives the binding checker. No coercion and no inserted defaults.",
     "fixtures": "Named payloads that must validate. At least one. Each is a preview and a publish check.",
-    "execution": "Nothing runs at send time. A template compiles to IR and the send path renders the IR against the input. Locale and time zone are send options."
+    "execution": "Nothing runs at send time. A template compiles to a compiled template and the send path renders it against the input. Locale and time zone are send options."
   },
   "profile": {
     "forms": [
@@ -1556,6 +1556,11 @@
       "fix": "Pair background and text tokens (bg-primary with text-primary-foreground), give the theme's dark-mode @theme a value for the token, or choose colors that reach the required ratio.",
       "upgrade": "Move the project's theme onto the theme vocabulary with one dark-mode block. In starter.css and theme.css, rename each color token to the vocabulary name for its role (reference.md, Theme): a page color to --color-background, the main text to --color-foreground, a surface to --color-card with --color-card-foreground, the brand or action color to --color-primary with --color-primary-foreground, subdued text to --color-muted-foreground, a highlight to --color-accent with --color-accent-foreground, rules to --color-border, body and heading fonts to --font-sans and --font-heading, and a corner radius to --radius. Keep every value.\n\nMove each --color-<name>-dark value into @media (prefers-color-scheme: dark) { @theme { --color-<name>: <value>; } } under the renamed token, and delete the -dark tokens. In every template and partial, rename the utilities to match (bg-surface to bg-card, text-muted to text-muted-foreground, and so on) and delete each dark:…-dark class whose token now has a dark value; keep a dark: class only where it picks a different token in dark mode.\n\nThen fix what email-contrast still reports at its location: pair each fill with its -foreground token, or give the dark block a value that reaches the ratio. Do not weaken the design to pass: keep the brand's colors and adjust the paired token.\n\nCompile every entry and render every fixture in light and dark mode; confirm the light render is unchanged apart from fixes. Resolve errors before requesting one saved version for the whole project, approved by the user; do not publish."
     },
+    {
+      "code": "email-external-asset",
+      "summary": "An image points at another site's URL; a hotlinked image can disappear, be blocked, track recipients or slow the message.",
+      "fix": "Add the image to the project's files and import it (import logo from './logo.png'), then use the import as the src."
+    },
     {
       "code": "email-font-fallback",
       "summary": "A font stack names a project font without a generic fallback.",

package/generated/reference.md

@@ -3,8 +3,8 @@
 A template is one TSX file that default-exports `defineTemplate({ id, schema, fixtures, email })`
 from `@samva/markup`, in `templates/` (`emails/` is also recognized). Set
 `jsxImportSource: "@samva/markup/email"`. `email` is `{ subject, preheader?, body }`; each is a
-function of the validated input that the compiler reads without running. The IR it produces is what
-every preview and send renders (IR version 1).
+function of the validated input that the compiler reads without running. The compiled template it
+produces is what every preview and send renders (compiled template version 1).
 
 ## Static profile
 
@@ -305,6 +305,7 @@ Global attributes: `id`, `title`, `lang`, `dir`, `role`.
 | `dynamic-expression`         | An expression outside the static profile: a call other than fmt.* and .map, a computed value, or a spread.                                                                                  | Compute the value where the message is sent and bind it from the payload.                                                                                                           |
 | `dynamic-numeric-prop`       | A prop that sizes layout at compile time is not a number literal.                                                                                                                           | Write the number literally, for example height={44}.                                                                                                                                |
 | `email-contrast`             | Text, or a filled button against its surroundings, falls below the contrast ratio in light or dark mode (below 1.5:1 a button is indistinguishable from its surface; WCAG 1.4.11 asks 3:1). | Pair background and text tokens (bg-primary with text-primary-foreground), give the theme's dark-mode @theme a value for the token, or choose colors that reach the required ratio. |
+| `email-external-asset`       | An image points at another site's URL; a hotlinked image can disappear, be blocked, track recipients or slow the message.                                                                   | Add the image to the project's files and import it (import logo from './logo.png'), then use the import as the src.                                                                 |
 | `email-font-fallback`        | A font stack names a project font without a generic fallback.                                                                                                                               | End the stack with sans-serif, serif or monospace.                                                                                                                                  |
 | `email-font-family`          | @font-face declares no font-family.                                                                                                                                                         | Add font-family.                                                                                                                                                                    |
 | `email-font-format`          | @font-face uses a format other than WOFF2.                                                                                                                                                  | Convert the file to .woff2.                                                                                                                                                         |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@samva/markup",
-  "version": "0.15.1",
+  "version": "0.17.0",
   "description": "Type-safe authoring and compilation primitives for Samva templates",
   "keywords": [
     "email",
@@ -73,6 +73,10 @@
       "types": "./dist/compiler.d.ts",
       "import": "./dist/compiler.js"
     },
+    "./compatibility": {
+      "types": "./dist/compatibility.d.ts",
+      "import": "./dist/compatibility.js"
+    },
     "./diagnostics": {
       "types": "./dist/diagnostics.d.ts",
       "import": "./dist/diagnostics.js"

package/skills/sml/SKILL.md

@@ -7,7 +7,7 @@ description: Author, check, render and repair Samva email templates written as s
 
 A template is one `.tsx` file that default-exports `defineTemplate` from `@samva/markup`. It is
 ordinary JSX, HTML and Tailwind written in a static profile: the compiler reads it without running
-it and produces a JSON IR. Every preview and every send renders that IR against the input, so
+it and produces a compiled template: JSON. Every preview and every send renders that template against the input, so
 nothing you write executes at send time.
 
 ## The loop
@@ -23,7 +23,7 @@ samva templates dev                         # local editor with every fixture re
 
 Add `--json` for diagnostics as data: each has a `code`, a location, a severity and a `fix`. Apply
 the fix the diagnostic names rather than rewriting around it. Without the CLI, call
-`compileTemplate` from `@samva/markup/compiler` and `renderIr` from `@samva/markup/render`.
+`compileTemplate` from `@samva/markup/compiler` and `render` from `@samva/markup/render`.
 
 ## Upgrades