@nxgt/mail-i18n 0.3.0 → 0.3.1

package/README.md

@@ -407,7 +407,9 @@ the build.
 **List the plugin that brings a template's components.** A tag that
 resolves to no component renders nothing, and the build fails with
 `i18n: fr/welcome.html is empty — a tag of its template resolved to no
-component; list the plugin that brings it, as ui()`.
+component; list the plugin that brings it, as ui()`. With `ui()` listed, a
+tag that resolves to no component fails the build first, nested or not:
+`ui: <NxButon> in emails/welcome.vue is no component — …`.
 
 **Leave the output paths to the plugin.** An `output.path` set in a
 template, or a `plaintext.destination`, moves a file out of the plugin's

package/docs/guide/manifest.md

@@ -229,7 +229,7 @@ catalogues, not a condition to catch:
 | `i18n: en: welcome.subject uses {count} as a number — a subject's arguments are placeholders, filled at send time as strings` | A subject with a `number`, `plural` or `date` argument |
 | `i18n: en: welcome.subject chooses on {kind} with a select — a subject's arguments are placeholders, which always choose other` | A subject with a `select` argument |
 | `i18n: welcome was not built in fr` | No HTML file (with `output.extension`) was written for that e-mail in that locale |
-| `i18n: fr/welcome.html is empty — a tag of its template resolved to no component; list the plugin that brings it, as ui()` | The file holds nothing but its doctype: a tag of the template matched no component, which Vue renders as nothing. See [Templates from a package](templates.md#templates-from-a-package) |
+| `i18n: fr/welcome.html is empty — a tag of its template resolved to no component; list the plugin that brings it, as ui()` | The file holds nothing but its doctype: a tag of the template matched no component, which Vue renders as nothing. With `ui()` listed, the build fails earlier on `ui: <Tag> in <file> is no component`. See [Templates from a package](templates.md#templates-from-a-package) |
 | `i18n: ../text/welcome.en.txt was written outside the output folder — the i18n plugin lays out every e-mail; set no plaintext.destination and no output path in a template` | A `plaintext.destination`, or an output path set in a template, put a file outside `output.path` |
 | `i18n: custom/welcome.html is not where the i18n plugin puts an e-mail — set no output path in a template` | A file in the output folder that is not `<locale>/<email>` (or `<email>.<locale>` with the flat layout), usually from an output path set in a template |
 

package/docs/guide/templates.md

@@ -266,7 +266,9 @@ which skips that folder. The plugin that ships the components resolves them —
 `@nxgt/mail-ui`'s `ui()` does, for its `Nx*` components and Maizzle's
 built-ins, so list it in `plugins`. A tag left unresolved renders nothing,
 and the build fails on the empty e-mail (see
-[What fails the build](#what-fails-the-build)).
+[What fails the build](#what-fails-the-build)); with `ui()` listed, one
+nested anywhere fails it too, naming the tag and the file:
+`ui: <NxButon> in emails/welcome.vue is no component — …`.
 
 ### Its errors
 
@@ -302,7 +304,7 @@ the template or the catalogues, to fix, not a condition to catch.
 | `i18n: templates[0] has no template sign-in.vue — name one of its e-mails` | A [package's source](#templates-from-a-package) lists, in `emails`, a template its folder does not have; checked when the config loads |
 | `i18n: templates[0] holds no template — is /…/emails the folder of a package's e-mails?` | A package's source whose `dir` is missing or has no template; checked when the config loads |
 | `i18n: templates[0] and templates[1] both have welcome.vue — keep one with emails: [...], or write the project's own in its folder` | Two package sources ship the same e-mail; checked when the config loads |
-| `i18n: fr/welcome.html is empty — a tag of its template resolved to no component; list the plugin that brings it, as ui()` | The e-mail rendered nothing but the doctype: a tag of its template, usually the layout, matched no component, and Vue renders an unknown component as nothing. Typically `ui()` is missing from `plugins`, or a package's template uses a component no plugin brings. Reported when the manifest is written |
+| `i18n: fr/welcome.html is empty — a tag of its template resolved to no component; list the plugin that brings it, as ui()` | The e-mail rendered nothing but the doctype: a tag of its template, usually the layout, matched no component, and Vue renders an unknown component as nothing. Typically `ui()` is missing from `plugins`, or a package's template uses a component no plugin brings. Reported when the manifest is written; with `ui()` listed, the build fails earlier on `ui: <Tag> in <file> is no component` |
 | `i18n: emails/Welcome.vue is not a kebab-case name — name a template as verify-email.vue` | A template whose path is not kebab-case, checked when the config loads. Under `maizzle serve`, one added while the server runs is printed with `console.error`, and the server keeps running |
 | `i18n: welcome has no subject — add welcome.subject to the catalogues` | The e-mail has no subject message; reported when the manifest is written, at the end of the build. The other manifest failures, including an output path set in a template, are in [The manifest](manifest.md#where-it-is-written) |
 | `i18n: emails/verify-email.vue is not built through the i18n plugin — leave content to it, and put templates in emails/` | Maizzle rendered a template directly: the project set its own `content` |

package/docs/roadmap.md

@@ -5,10 +5,7 @@ no dates here, and the version something shipped in is the only number.
 
 ## Now
 
-- **The manifest's format, versioned** — `mail-manifest.json` starts with
-  `formatVersion`, `MANIFEST_FORMAT` is exported, and the format changes only
-  with the manifest's shape: any later `@nxgt/mail` 0.x reads the build.
-  Built, not yet published.
+Nothing between releases.
 
 ## Next
 
@@ -41,6 +38,10 @@ Nothing yet. A request is welcome as an
 The last ten, newest first, each with the version it came in. Everything
 before is in the [CHANGELOG](../CHANGELOG.md).
 
+- **The manifest's format, versioned, v0.3.0** — `mail-manifest.json` starts
+  with `formatVersion`, `MANIFEST_FORMAT` is exported, and the format changes
+  only with the manifest's shape: any later `@nxgt/mail` 0.x reads the build.
+  The `@nxgt/mail-config` peer moves to `^0.2.0`.
 - **The wrappers under `.maizzle/emails/`, v0.2.0** — the files generated per
   template and locale move from `.maizzle/i18n/` to `.maizzle/emails/`, so
   `maizzle serve` lists the e-mails under `.maizzle/emails/en` rather than a
@@ -85,10 +86,3 @@ before is in the [CHANGELOG](../CHANGELOG.md).
   catalogues each time the config loads, so an editor completes `t('…')` and
   flags an unknown key or a wrong argument, and `vue-tsc` checks templates in
   CI.
-- **The renderer typed by the build, v0.1.0** — after each `maizzle build`, the
-  plugin writes `generated/mail.ts`: `MailEmails`, each e-mail with the
-  variables it takes, a URL variable as a `string`. With it,
-  `createMailRenderer<MailEmails>` from `@nxgt/mail/renderer` refuses an
-  unknown e-mail, a missing or unknown variable, or a number for a URL at
-  compile time. Rewritten only when it changes;
-  `rendererTypes` moves it, or `false` turns it off.

package/docs/troubleshooting.md

@@ -828,9 +828,12 @@ such warning for each tag that did not resolve.
 
 **When:** `maizzle build`, after the templates, when a template's outermost
 tag is a component that nothing resolves. Most often `ui()` is missing from
-the plugins while a template uses `<NxLayout>`. It also happens when a
-package's template, under `node_modules`, uses a component that no plugin in
-the list resolves for it.
+the plugins while a template uses `<NxLayout>`, or a package's template,
+under `node_modules`, uses a component that no plugin in the list resolves
+for it. With `@nxgt/mail-ui`'s `ui()` listed, the build stops earlier, on
+`ui: <NxLayout> in emails/welcome.vue is no component — check its name, or add
+the plugin or the components folder that brings it`, for any tag nested or
+not.
 **Why:** Vue renders a component it cannot resolve as nothing, and Maizzle
 still writes the file, with its doctype alone. The e-mail would go out
 blank, so the build stops.

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@nxgt/mail-i18n",
-	"version": "0.3.0",
+	"version": "0.3.1",
 	"description": "An i18n plugin for a Maizzle project: ICU catalogues checked at build time, t() in templates, one output per locale, and the manifest the renderer reads. createTranslator for use outside templates.",
 	"license": "MIT",
 	"type": "module",
@@ -52,14 +52,14 @@
 	"devDependencies": {
 		"@maizzle/framework": "6.1.7",
 		"@maizzle/tailwindcss": "1.5.6",
-		"@nxgt/mail-config": "0.2.0",
+		"@nxgt/mail-config": "0.2.1",
 		"@types/bun": "^1.4.2",
 		"vue": "3.5.43",
 		"vue-tsc": "^3.3.11"
 	},
 	"peerDependencies": {
 		"@maizzle/framework": "^6.1.7",
-		"@nxgt/mail-config": "^0.2.0",
+		"@nxgt/mail-config": "^0.2.1",
 		"typescript": "^6.0.3",
 		"vue": "^3.5.0"
 	},