ngwr 14.5.0 → 14.6.0

package/fesm2022/ngwr-version.mjs

@@ -16,7 +16,7 @@ import { InjectionToken } from '@angular/core';
  * Distinct from `Version` exported by `@angular/core`, which reports the
  * loaded Angular runtime version (e.g. `'22.0.0'`), not ngwr's.
  */
-const NGWR_VERSION = '14.5.0';
+const NGWR_VERSION = '14.6.0';
 
 /**
  * @license

package/fesm2022/ngwr-version.mjs.map

@@ -1 +1 @@
-{"version":3,"file":"ngwr-version.mjs","sources":["../../../projects/lib/version/version.ts","../../../projects/lib/version/version.token.ts","../../../projects/lib/version/ngwr-version.ts"],"sourcesContent":["/**\n * @license\n *\n * Use of this source code is governed by an MIT-style license that can be\n * found in the LICENSE file at https://github.com/thekhegay/ngwr/blob/main/LICENSE\n */\n\n/**\n * The ngwr library version string, kept in sync with\n * `projects/lib/package.json` by `scripts/release-prepare.ts`.\n *\n * Prefer this over reading `package.json` at runtime — that requires a JSON\n * import or `require`, neither of which tree-shakes well in Angular builds.\n *\n * Distinct from `Version` exported by `@angular/core`, which reports the\n * loaded Angular runtime version (e.g. `'22.0.0'`), not ngwr's.\n */\nexport const NGWR_VERSION = '14.5.0';\n","/**\n * @license\n *\n * Use of this source code is governed by an MIT-style license that can be\n * found in the LICENSE file at https://github.com/thekhegay/ngwr/blob/main/LICENSE\n */\n\nimport { InjectionToken } from '@angular/core';\n\nimport { NGWR_VERSION } from './version';\n\n/**\n * Injection token holding the ngwr library version string.\n *\n * Default factory returns {@link NGWR_VERSION}. Override it in tests or in\n * apps that want to surface a custom build identifier.\n *\n * @example\n * ```ts\n * @Component({...})\n * export class FooterComponent {\n *   readonly version = inject(NGWR_VERSION_TOKEN);\n * }\n * ```\n */\nexport const NGWR_VERSION_TOKEN = new InjectionToken<string>('NGWR_VERSION_TOKEN', {\n  providedIn: 'root',\n  factory: () => NGWR_VERSION,\n});\n","/**\n * Generated bundle index. Do not edit.\n */\n\nexport * from './public-api';\n"],"names":[],"mappings":";;AAAA;;;;;AAKG;AAEH;;;;;;;;;AASG;AACI,MAAM,YAAY,GAAG;;ACjB5B;;;;;AAKG;AAMH;;;;;;;;;;;;;AAaG;MACU,kBAAkB,GAAG,IAAI,cAAc,CAAS,oBAAoB,EAAE;AACjF,IAAA,UAAU,EAAE,MAAM;AAClB,IAAA,OAAO,EAAE,MAAM,YAAY;AAC5B,CAAA;;AC5BD;;AAEG;;;;"}
+{"version":3,"file":"ngwr-version.mjs","sources":["../../../projects/lib/version/version.ts","../../../projects/lib/version/version.token.ts","../../../projects/lib/version/ngwr-version.ts"],"sourcesContent":["/**\n * @license\n *\n * Use of this source code is governed by an MIT-style license that can be\n * found in the LICENSE file at https://github.com/thekhegay/ngwr/blob/main/LICENSE\n */\n\n/**\n * The ngwr library version string, kept in sync with\n * `projects/lib/package.json` by `scripts/release-prepare.ts`.\n *\n * Prefer this over reading `package.json` at runtime — that requires a JSON\n * import or `require`, neither of which tree-shakes well in Angular builds.\n *\n * Distinct from `Version` exported by `@angular/core`, which reports the\n * loaded Angular runtime version (e.g. `'22.0.0'`), not ngwr's.\n */\nexport const NGWR_VERSION = '14.6.0';\n","/**\n * @license\n *\n * Use of this source code is governed by an MIT-style license that can be\n * found in the LICENSE file at https://github.com/thekhegay/ngwr/blob/main/LICENSE\n */\n\nimport { InjectionToken } from '@angular/core';\n\nimport { NGWR_VERSION } from './version';\n\n/**\n * Injection token holding the ngwr library version string.\n *\n * Default factory returns {@link NGWR_VERSION}. Override it in tests or in\n * apps that want to surface a custom build identifier.\n *\n * @example\n * ```ts\n * @Component({...})\n * export class FooterComponent {\n *   readonly version = inject(NGWR_VERSION_TOKEN);\n * }\n * ```\n */\nexport const NGWR_VERSION_TOKEN = new InjectionToken<string>('NGWR_VERSION_TOKEN', {\n  providedIn: 'root',\n  factory: () => NGWR_VERSION,\n});\n","/**\n * Generated bundle index. Do not edit.\n */\n\nexport * from './public-api';\n"],"names":[],"mappings":";;AAAA;;;;;AAKG;AAEH;;;;;;;;;AASG;AACI,MAAM,YAAY,GAAG;;ACjB5B;;;;;AAKG;AAMH;;;;;;;;;;;;;AAaG;MACU,kBAAkB,GAAG,IAAI,cAAc,CAAS,oBAAoB,EAAE;AACjF,IAAA,UAAU,EAAE,MAAM;AAClB,IAAA,OAAO,EAAE,MAAM,YAAY;AAC5B,CAAA;;AC5BD;;AAEG;;;;"}

package/image-cropper/styles/_index.scss

@@ -23,6 +23,13 @@
     user-select: none;
   }
 
+  // A source the browser could not decode. The `<img>` stays in the DOM, since the
+  // next `src` goes through the same element, but some engines draw a broken-image
+  // glyph for it — and the failure is the host's to explain, not a stray icon's.
+  &--failed &__image {
+    display: none;
+  }
+
   &__backdrop {
     position: absolute;
     inset: 0;

package/llms-full.txt

@@ -45,7 +45,7 @@
 - import: `import { WrAvatar } from 'ngwr/avatar'`
 - selector: `wr-avatar`
 - exports: WrAvatar, WrAvatarSize, WrAvatarShape
-- Image avatar with a fixed square or rounded shape. Shows a spinner while the image loads.
+- Image avatar with a square, rounded, circle or squircle shape. Projected initials stand in while the image loads and when it fails.
 
 ## ngwr/back-top
 - import: `import { WrBackTop } from 'ngwr/back-top'`
@@ -461,7 +461,7 @@
 - import: `import { WrI18n } from 'ngwr/i18n'`
 - selector: `[wrT]`
 - exports: WrI18n, WrTPipe, WrTDirective, WR_I18N_CONFIG, DEFAULT_WR_I18N_CONFIG, WrI18nCatalog, WrI18nConfig, WrI18nConfigResolved, WrI18nParams, WrI18nMissingHandler, WR_I18N_LOADER, WrI18nLoader, WR_I18N_BASE_CATALOGS, WrI18nBaseCatalogs, WrI18nStaticLoader, WrI18nStaticCatalogs, WrI18nStaticScopedCatalogs, WrI18nHttpLoader, WrI18nHttpLoaderConfig, provideWrI18n, provideWrI18nBaseCatalogs, provideWrI18nStaticLoader, provideWrI18nHttpLoader, ProvideWrI18nOptions, useI18nText, readI18nText, useI18nFormatter
-- Reactive i18n service. Active locale lives on a signal, catalogs load lazily through a swappable loader (HTTP or static), and double-brace placeholders interpolate at render time. Scopes let feature modules ship and load their own catalogs.
+- Reactive i18n service. Active locale lives on a signal, catalogs load lazily through a swappable loader (HTTP or static), and double-brace placeholders interpolate at render time. Scopes let feature modules ship and load their own catalogs. Keep ngwr's own strings with `provideWrI18nBaseCatalogs` rather than spreading `wrEn` into your catalog: a spread is shallow, so any namespace you share with ngwr, e.g. `common`, `validation`, `table`, keeps only the side spread last, and the other side's keys stop resolving with nothing logged — ngwr's components fall back to English and a `wrT` read of a lost key renders the raw key.
 
 ## ngwr/i18n/ar
 - import: `import { wrAr } from 'ngwr/i18n/ar'`
@@ -568,7 +568,7 @@
 ## ngwr/image-cropper
 - import: `import { WrImageCropper } from 'ngwr/image-cropper'`
 - selector: `wr-image-cropper`
-- exports: WrImageCropper, WrCropRect, WrCropHandle, WrImageOutputType
+- exports: WrImageCropper, WrCropRect, WrCropHandle, WrImageCropperStatus, WrImageLoadError, WrImageOutputType
 - DOM-based crop UI. Drag the box to move, drag any of the eight handles to resize. Optional `[aspectRatio]` locks the box shape. `(cropped)` fires with a `Blob` after each drag end — wire to upload or preview.
 
 ## ngwr/image-cropper/testing
@@ -840,8 +840,8 @@
 
 ## ngwr/select
 - import: `import { WrSelect } from 'ngwr/select'`
-- selector: `wr-option-group`, `wr-option`, `wr-select`
-- exports: WrSelect, WrOption, WrOptionGroup, WR_SELECT, WrSelectContext, WrSelectMode, WrSelectSearchLoader, WrSelectTagValidator, WrSelectSize
+- selector: `wr-option-group`, `ng-template[wrOptionLeading]`, `wr-option`, `wr-select`
+- exports: WrSelect, WrOption, WrOptionGroup, WrOptionLeading, WR_SELECT, WrSelectContext, WrOptionLeadingContext, WrOptionLeadingPlacement, WrSelectMode, WrSelectSearchLoader, WrSelectTagValidator, WrSelectSize
 - Native-like select built on CDK Overlay. A signal-forms native control — it implements `FormValueControl`, so `[formField]` binds straight to its `value` model. `[(value)]` works standalone, and `[(ngModel)]` / reactive forms keep working through [Angular 22's forms bridge](/guides/forms).
 
 ## ngwr/select/testing

package/llms.txt

@@ -84,7 +84,12 @@ Add from their entry points as needed:
   / `select`, and `linkTarget` / `copyable` on `markdown`. There is deliberately no
   `color` key — a bound `[color]="null"` means "no intent", which a default cannot
   express without inventing a sentinel.
-- `provideWrI18n(...)` + `provideWrI18nStaticLoader(...)` — localization.
+- `provideWrI18n(...)` + `provideWrI18nBaseCatalogs({ en: wrEn })` +
+  `provideWrI18nStaticLoader(...)` — localization. ngwr's catalogs go in as a
+  BASE, never spread into yours: a spread is shallow, so any namespace you share
+  with ngwr, e.g. `common`, `validation`, `table`, keeps only the side spread
+  last, and the other side's keys stop resolving with nothing logged — ngwr's
+  components fall back to English and a `wrT` read renders the raw key.
 - `provideWrDateAdapter(...)` — calendar + date-picker (`ngwr/date/adapters/fns`
   or `ngwr/date/adapters/luxon`).
 
@@ -106,8 +111,12 @@ one element at a time; a step whose target is missing is skipped, not floated.
 
 ## Upgrading to v14
 
-Run `ng update ngwr@14`. It rewrites the renames and REPORTS the rest — read its
-output, because the reported half is where the silent failures are.
+Run `ng update ngwr@14`, once, from whatever major the app is on — it runs every
+migration between the installed version and 14, in order. Do not step through the
+majors, and never target a 7.x, 8.x or 9.x release: their schematics die with
+`exports is not defined in ES module scope`. It rewrites the renames and REPORTS
+the rest — read its output, because the reported half is where the silent
+failures are.
 
 Rewritten for you (six renames, one word per concept):
 

package/mcp/providers.js

@@ -46,8 +46,14 @@ const REQUIRED_PROVIDERS = [
         test: /^WrTPipe$|^WrTDirective$|^WrI18n/,
         // Two entry points, and the comment has to say so: the catalog `wrEn` is
         // `ngwr/i18n/en`, not `ngwr/i18n`, which exports neither catalog.
-        provider: "provideWrI18n() + provideWrI18nStaticLoader({ en: wrEn }) // from 'ngwr/i18n' + 'ngwr/i18n/en'",
-        why: 'the pipe and directive read from a catalog you provide',
+        //
+        // `wrEn` goes in as a BASE and the loader carries only the app's keys. A
+        // loader serves only the catalog it is given, so the other way to keep both
+        // is a spread, and a spread is shallow: it silently drops one side of every
+        // namespace the two catalogs share. This line is what an agent pastes, so it
+        // has to be the form that survives the app adding its first `common` key.
+        provider: "provideWrI18n() + provideWrI18nBaseCatalogs({ en: wrEn }) + provideWrI18nStaticLoader({ en: { … } }) // from 'ngwr/i18n' + 'ngwr/i18n/en'",
+        why: "the pipe and directive read from a catalog you provide. Register ngwr's with `provideWrI18nBaseCatalogs`, never spread it into yours: a spread is shallow, so any namespace you share with ngwr, e.g. `common`, `validation`, `table`, keeps only the side spread last, and the other side's keys stop resolving with nothing logged — ngwr's components fall back to English and a `wrT` read of a lost key renders the raw key",
     },
 ];
 export { REQUIRED_PROVIDERS };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ngwr",
-  "version": "14.5.0",
+  "version": "14.6.0",
   "bin": {
     "ngwr-mcp": "mcp/server.js"
   },

package/schematics/migrations/v14/index.js

@@ -101,28 +101,57 @@ Object.defineProperty(exports, "__esModule", { value: true });
  * Both are now zero for an app that does not opt in.
  */
 const IGNORE_DIRS = new Set(['node_modules', 'dist', '.git', '.cache', '.angular', 'coverage', '.next', '.nuxt']);
+/**
+ * What an open tag may hold between its name and the attribute a rule is after:
+ * a quoted value, consumed only as a PAIR, or any one character that is neither
+ * a quote nor `>`. Every element-scoped rule and attribute detector in this file
+ * is built on it, and both halves of "only as a pair" were earned.
+ *
+ * Stepping OVER a quoted value is what a plain `[^>]*?` got wrong: a `>` inside a
+ * binding looks like the end of the tag, so
+ * `<wr-alert [type]="n > 0 ? 'a' : 'b'" closeable>` left `closeable` behind while
+ * the same attributes in the other order moved. The leftover is SILENT — a static
+ * `closeable` / `totalItems="42"` that matches no input is an ordinary DOM
+ * attribute and `strictTemplates` says nothing, so the alert quietly loses its
+ * dismiss button. (Bracketed forms are loud: NG8002.)
+ *
+ * Never consuming a LONE quote is what the first fix got wrong. It spelled the
+ * fallback `[^>]`, which matches a quote as well, so the engine could backtrack
+ * into a single-quoted span that STARTS at the apostrophe inside `title="it's"`
+ * and runs past `/>` into the following element: `<wr-alert title="it's" />`
+ * then `<app-panel [label]="'x'" closeable />` renamed the PANEL's attribute. The
+ * same overlap made a miss exponential — one `<wr-alert>` holding twenty-two
+ * quoted attributes and nothing to rename took sixteen seconds in the bare
+ * `closeable` rule alone, where this form takes under a millisecond. And a miss
+ * did not stay inside its tag: since a pair may contain `>`, a pairing that
+ * started at a CLOSING quote jumped over `/>` into later elements, so an
+ * ordinary element without the attribute sent the search across the rest of the
+ * file. On a 64-line template that never finished, and because `ng update`
+ * commits each migration's tree separately, v12 and v13 landed while this one
+ * wrote nothing. The spec's timing cases are sized to fail in seconds on that form.
+ *
+ * What it guarantees: a match cannot leave the open tag it started in, as long as
+ * every quote in that tag opens or closes an attribute value. The one markup that
+ * breaks the condition is an UNQUOTED value holding a quote (`title=it's`), and a
+ * tag like that is skipped rather than guessed at — which costs nothing real,
+ * because Angular's own template parser refuses it (`Opening tag "input" not
+ * terminated.`).
+ */
+const IN_TAG = String.raw `(?:"[^"]*"|'[^']*'|[^>"'])*?`;
 /**
  * An open tag, up to and including the whitespace before some attribute.
- * `[^>]*?` cannot cross a `>`, so a rename can never escape the element it is
- * scoped to, however the tag wraps across lines.
  *
  * The anchor is `(?![-\w])` and NOT `\b`: a word boundary still matches at the
  * front of a longer element name, which is how a v9-shaped rule would have
  * renamed an attribute on `<wr-table-filter>` while claiming to touch only
  * `<wr-table>`. Every one of these four has such a neighbour — `wr-table-filter`
  * and `wr-table-sort`, `wr-window-container` and `wr-window-taskbar` — or would
- * acquire one the moment the catalog grows.
- *
- * Quoted values are stepped over rather than excluded, and that is the half a
- * plain `[^>]*?` gets wrong: a `>` inside a binding expression looks like the end
- * of the tag, so `<wr-alert [type]="n > 0 ? 'a' : 'b'" closeable>` left
- * `closeable` behind while the same attributes in the other order moved. The
- * leftover is SILENT — a static `closeable` / `totalItems="42"` that matches no
- * input is an ordinary DOM attribute and `strictTemplates` says nothing, so the
- * alert quietly loses its dismiss button. (Bracketed forms are loud: NG8002.)
- * `migration-v9` carries the same anchoring and the same hole.
+ * acquire one the moment the catalog grows. `migration-v9` carries the same
+ * anchoring and the same pattern.
  */
-const openTag = (name) => String.raw `<${name}(?![-\w])(?:"[^"]*"|'[^']*'|[^>])*?\s`;
+const openTag = (name) => String.raw `<${name}(?![-\w])${IN_TAG}\s`;
+/** The two elements `[wrInput]` applies to — its selector is `input[wrInput], textarea[wrInput]`. */
+const FIELD = String.raw `<(?:input|textarea)(?![-\w])`;
 const ALERT = openTag('wr-alert');
 const TABLE = openTag('wr-table');
 const PAGER = openTag('wr-pagination');
@@ -143,21 +172,15 @@ const HTML_TRANSFORMS = [
     // native attribute, so rewriting one that was never ngwr's silently rebinds a
     // character-width hint. The two orders are both real markup, hence two rules.
     {
-        pattern: /(<(?:input|textarea)(?![-\w])(?:"[^"]*"|'[^']*'|[^>])*?\swrInput(?:"[^"]*"|'[^']*'|[^>])*?\s)\[wrSize\]/g,
+        pattern: new RegExp(String.raw `(${FIELD}${IN_TAG}\swrInput${IN_TAG}\s)\[wrSize\]`, 'g'),
         replacement: '$1[size]',
     },
+    { pattern: new RegExp(String.raw `(${FIELD}${IN_TAG}\swrInput${IN_TAG}\s)wrSize=`, 'g'), replacement: '$1size=' },
     {
-        pattern: /(<(?:input|textarea)(?![-\w])(?:"[^"]*"|'[^']*'|[^>])*?\swrInput(?:"[^"]*"|'[^']*'|[^>])*?\s)wrSize=/g,
-        replacement: '$1size=',
-    },
-    {
-        pattern: /(<(?:input|textarea)(?![-\w])(?:"[^"]*"|'[^']*'|[^>])*?\s)\[wrSize\]((?:"[^"]*"|'[^']*'|[^>])*?\swrInput)/g,
+        pattern: new RegExp(String.raw `(${FIELD}${IN_TAG}\s)\[wrSize\](${IN_TAG}\swrInput)`, 'g'),
         replacement: '$1[size]$2',
     },
-    {
-        pattern: /(<(?:input|textarea)(?![-\w])(?:"[^"]*"|'[^']*'|[^>])*?\s)wrSize=((?:"[^"]*"|'[^']*'|[^>])*?\swrInput)/g,
-        replacement: '$1size=$2',
-    },
+    { pattern: new RegExp(String.raw `(${FIELD}${IN_TAG}\s)wrSize=(${IN_TAG}\swrInput)`, 'g'), replacement: '$1size=$2' },
     // <wr-table>, from [totalItems] to [total]
     { pattern: new RegExp(`(${TABLE})\\[totalItems\\]`, 'g'), replacement: '$1[total]' },
     { pattern: new RegExp(`(${TABLE})totalItems=`, 'g'), replacement: '$1total=' },
@@ -202,8 +225,12 @@ const GLOBAL_TRANSFORMS = [
     // keyed on it stops matching with no error — CSS does not have one.
     { pattern: /\bwr-window--chrome-normal\b/g, replacement: 'wr-window--chrome-md' },
 ];
-/** `<wr-tab …>` carrying a `routerLink`, however the tag is wrapped across lines. */
-const ROUTER_TAB = /<wr-tab\b[^>]*\brouterLink\b/;
+/**
+ * `<wr-tab …>` carrying a `routerLink`, however the tag is wrapped across lines
+ * and whatever an earlier binding compares — the plain `[^>]*` this used to be
+ * read `[disabled]="n > 0"` as the end of the tag and reported nothing.
+ */
+const ROUTER_TAB = new RegExp(String.raw `<wr-tab(?![-\w])${IN_TAG}\brouterLink\b`);
 const LOADING_BAR = /<wr-loading-bar\b/;
 /** `provideWrDateAdapter(` with no `locale:` before the call closes. */
 // `locale` as a key OR as shorthand, and the scan for it runs to the call's own
@@ -217,8 +244,20 @@ const DATE_ADAPTER_NO_LOCALE = /\bprovideWrDateAdapter\(\s*(?:\)|\{(?![\s\S]*?\b
 /** `provideWrI18n(` with no `defaultLocale:` before the call closes. */
 const I18N_NO_DEFAULT_LOCALE = /\bprovideWrI18n\(\s*(?:\)|\{(?![^})]*\bdefaultLocale\s*:))/;
 const DEFAULT_CONFIG = /\bDEFAULT_WR_I18N_CONFIG\b/;
-/** `ofLabel` on a pagination tag, bound (`[ofLabel]`) or static. */
-const OF_LABEL = /<wr-pagination\b[^>]*\[?ofLabel\]?\s*=/;
+/** `ofLabel` on a pagination tag, bound (`[ofLabel]`) or static, wherever it sits in the tag. */
+const OF_LABEL = new RegExp(String.raw `${PAGER}\[?ofLabel\]?\s*=`);
+/**
+ * `wrSize` still on a `[wrInput]` field AFTER the renames ran, in either
+ * attribute order and with any spacing around `=`. The renames read `wrSize=` and
+ * `[wrSize]` exactly, and whatever they do not move is silent: a static `wrSize`
+ * matches no input, lands on the field as a plain DOM attribute, and the control
+ * renders at its default size. So this is the one detector that reads the
+ * REWRITTEN text — its whole job is what the rules left behind.
+ */
+const LEFTOVER_WR_SIZE = [
+    new RegExp(String.raw `${FIELD}${IN_TAG}\swrInput${IN_TAG}\s\[?wrSize\]?\s*=`),
+    new RegExp(String.raw `${FIELD}${IN_TAG}\s\[?wrSize\]?\s*=${IN_TAG}\swrInput`),
+];
 // The half `OF_LABEL` cannot see. Apps that never bound the input still
 // translated the key, and `pagination.of` is gone: the range is one
 // `pagination.range` template now, so a catalog that defines the old key loses
@@ -285,6 +324,7 @@ function ngUpdateV14() {
         const defaultConfigs = [];
         const ofLabels = [];
         const staleCatalogs = [];
+        const leftoverSizes = [];
         let rewritten = 0;
         visit(tree, '/', filePath => {
             const lower = filePath.toLowerCase();
@@ -295,10 +335,11 @@ function ngUpdateV14() {
             // reach stylesheets too, because one of them is a BEM class.
             if (!isTs && !isHtml && !isStyle && !lower.endsWith('.json'))
                 return;
-            // Read ONCE. Every detector below then answers about the file the user
-            // wrote, not about the file a transform left behind — none of the five
-            // renames touches a reported token today, and relying on that is exactly
-            // the coupling that breaks the next time one is added.
+            // Read ONCE. Every detector below but the leftover `wrSize` check then
+            // answers about the file the user wrote, not about the file a transform
+            // left behind — none of the six renames touches a token those detectors
+            // report today, and relying on that is exactly the coupling that breaks
+            // the next time one is added.
             const content = tree.readText(filePath);
             if (isTs || isHtml || isStyle) {
                 const next = apply(content, [
@@ -310,6 +351,11 @@ function ngUpdateV14() {
                     tree.overwrite(filePath, next);
                     rewritten += 1;
                 }
+                // The one detector that reads what the renames LEFT rather than what the
+                // user wrote: a `wrSize` surviving them is exactly what it exists to name.
+                if ((isTs || isHtml) && LEFTOVER_WR_SIZE.some(pattern => pattern.test(next))) {
+                    leftoverSizes.push(filePath);
+                }
             }
             if (ROUTER_TAB.test(content))
                 routerTabs.push(filePath);
@@ -333,10 +379,19 @@ function ngUpdateV14() {
             context.logger.info(`ngwr v14 migration: rewrote ${rewritten} file(s) for the renames: on <wr-alert> from ` +
                 'closeable to closable, on <wr-table> from totalItems to total, on <wr-pagination> from ' +
                 'currentPage to page (and from currentPageChange to pageChange), from isDisabledWhenLoading ' +
-                'to disabledWhenLoading, and the window chromeSize scale from compact/normal to sm/md ' +
-                '(class .wr-window--chrome-compact to --chrome-sm).');
+                'to disabledWhenLoading, the window chromeSize scale from compact/normal to sm/md ' +
+                '(class .wr-window--chrome-compact to --chrome-sm), and on [wrInput] from wrSize to size ' +
+                '(and from [wrSize] to [size]).');
             context.logger.info('Verify the result with `git diff` — a few edge cases may need manual touch-up.');
         }
+        if (leftoverSizes.length > 0) {
+            context.logger.warn(`ngwr v14: \`wrSize\` is still on a [wrInput] field in ${leftoverSizes.length} file(s), in a spelling ` +
+                "the rename did not match. [wrInput]'s input has been `size` since v14, so a static wrSize is " +
+                'ignored — it lands as a plain DOM attribute and the field renders at its default size, with ' +
+                'nothing said — and a bound [wrSize] fails to compile (NG8002). Rename it to `size` by hand.');
+            for (const file of leftoverSizes)
+                context.logger.warn(`  ${file}`);
+        }
         if (staleCatalogs.length > 0) {
             context.logger.warn(`ngwr v14: a translated \`pagination.of\` found in ${staleCatalogs.length} file(s). The range is ` +
                 'one template now — replace it with `pagination.range` ("{{from}}–{{to}} of {{total}}") and ' +
@@ -399,7 +454,8 @@ function ngUpdateV14() {
             i18nProviders.length === 0 &&
             defaultConfigs.length === 0 &&
             ofLabels.length === 0 &&
-            staleCatalogs.length === 0) {
+            staleCatalogs.length === 0 &&
+            leftoverSizes.length === 0) {
             context.logger.info('ngwr v14 migration: nothing to do — no affected usage found.');
         }
         return tree;

package/schematics/migrations/v7/index.js

@@ -6,6 +6,17 @@
  * found in the LICENSE file at https://github.com/thekhegay/ngwr/blob/main/LICENSE
  */
 Object.defineProperty(exports, "__esModule", { value: true });
+/**
+ * What an open tag may hold before the attribute a rule is after. A quoted value
+ * is consumed only as a PAIR: the plain `[^>]*?` this replaced read a `>` inside
+ * a binding as the end of the tag, so
+ * `<wr-select [placeholder]="n > 0 ? 'a' : 'b'" multi>` kept its `multi` while the
+ * same attributes in the other order moved — and a lone quote is never consumed,
+ * so a rule cannot slide through an apostrophe in one element's value into the
+ * next element. `migration-v14`'s `IN_TAG` carries the full account, including
+ * the one shape this skips: an UNQUOTED value holding a quote (`title=it's`).
+ */
+const IN_TAG = String.raw `(?:"[^"]*"|'[^']*'|[^>"'])*?`;
 const HTML_TRANSFORMS = [
     // wr-autocomplete → wr-select mode="search"
     { pattern: /<wr-autocomplete(\s|>|\/)/g, replacement: '<wr-select mode="search"$1' },
@@ -35,9 +46,9 @@ const HTML_TRANSFORMS = [
     { pattern: /<wr-count-up-text(\s|>|\/)/g, replacement: '<wr-count-up$1' },
     { pattern: /<\/wr-count-up-text>/g, replacement: '</wr-count-up>' },
     // wr-select's deprecated [multi] alias → mode="multi"
-    { pattern: /(<wr-select\b[^>]*?)\s\[multi\]="true"/g, replacement: '$1 mode="multi"' },
-    { pattern: /(<wr-select\b[^>]*?)\s\[multi\]="false"/g, replacement: '$1' },
-    { pattern: /(<wr-select\b[^>]*?)\smulti(?=[\s>/])/g, replacement: '$1 mode="multi"' },
+    { pattern: new RegExp(String.raw `(<wr-select\b${IN_TAG})\s\[multi\]="true"`, 'g'), replacement: '$1 mode="multi"' },
+    { pattern: new RegExp(String.raw `(<wr-select\b${IN_TAG})\s\[multi\]="false"`, 'g'), replacement: '$1' },
+    { pattern: new RegExp(String.raw `(<wr-select\b${IN_TAG})\smulti(?=[\s>/])`, 'g'), replacement: '$1 mode="multi"' },
     // wr-image → wr-lightbox (rename — same surface)
     { pattern: /<wr-image(\s|>|\/)/g, replacement: '<wr-lightbox$1' },
     { pattern: /<\/wr-image>/g, replacement: '</wr-lightbox>' },
@@ -46,7 +57,7 @@ const HTML_TRANSFORMS = [
     // attribute form (`<h1 wr-animated-text …>`) has no 1:1 target and is
     // left for manual migration; a bound `[mode]` falls back to typewriter.
     {
-        pattern: /<wr-animated-text\b([^>]*?)\s*(\/>|>\s*<\/wr-animated-text>)/g,
+        pattern: new RegExp(String.raw `<wr-animated-text\b(${IN_TAG})\s*(\/>|>\s*<\/wr-animated-text>)`, 'g'),
         replacement: (_match, attrs) => {
             const mode = /\bmode\s*=\s*"(\w+)"/.exec(attrs)?.[1] ?? 'typewriter';
             const tag = mode === 'split' ? 'wr-split-text' : mode === 'scramble' ? 'wr-decrypt-text' : 'wr-typewriter';

package/schematics/migrations/v8/index.js

@@ -12,6 +12,17 @@ const DENSITY_MAP = [
     ['default', 'md'],
     ['comfortable', 'lg'],
 ];
+/**
+ * What an open tag may hold before the attribute a rule is after. A quoted value
+ * is consumed only as a PAIR: the plain `[^>]*?` this replaced read a `>` inside
+ * a binding as the end of the tag, so `<wr-pagination [disabled]="n > 0" size="xs" />`
+ * kept its `xs` while the same attributes in the other order moved — and a lone
+ * quote is never consumed, so a rule cannot slide through an apostrophe in one
+ * element's value into the next element. `migration-v14`'s `IN_TAG` carries the
+ * full account, including the one shape this skips: an UNQUOTED value holding a
+ * quote (`title=it's`).
+ */
+const IN_TAG = String.raw `(?:"[^"]*"|'[^']*'|[^>"'])*?`;
 const HTML_TRANSFORMS = [
     // density — directive attribute, string form: wrDensity="compact" → "sm"
     ...DENSITY_MAP.map(([from, to]) => ({
@@ -29,8 +40,8 @@ const HTML_TRANSFORMS = [
         replacement: `$1${to}$2`,
     })),
     // pagination size — scoped to the element so other `size="xs"` attrs are untouched
-    { pattern: /(<wr-pagination\b[^>]*?\ssize=")xs(")/g, replacement: '$1sm$2' },
-    { pattern: /(<wr-pagination\b[^>]*?\ssize=")xl(")/g, replacement: '$1lg$2' },
+    { pattern: new RegExp(String.raw `(<wr-pagination\b${IN_TAG}\ssize=")xs(")`, 'g'), replacement: '$1sm$2' },
+    { pattern: new RegExp(String.raw `(<wr-pagination\b${IN_TAG}\ssize=")xl(")`, 'g'), replacement: '$1lg$2' },
 ];
 const TS_TRANSFORMS = [
     // density — provideWrDensity({ defaultDensity: 'compact' }) → 'sm'

package/schematics/migrations/v9/index.js

@@ -14,17 +14,26 @@ Object.defineProperty(exports, "__esModule", { value: true });
  * `FormValueControl`) and must be left alone — renaming it would break every
  * bound group.
  *
- * Quoted values are STEPPED OVER rather than excluded, and that is the half a
- * plain `[^>]*?` got wrong for two majors: a `>` inside a binding expression
- * looks like the end of the tag, so `<wr-checkbox [disabled]="n > 0" value="a">`
- * kept its `value` while the same attributes in the other order moved. The
- * leftover is SILENT — a static `value="a"` that matches no input is an ordinary
- * DOM attribute, `strictTemplates` says nothing, and every checkbox in the group
- * keeps the default identity `null`, so they all toggle together. That is the
- * exact defect this migration exists to prevent, reintroduced by the migration
- * itself. `migration-v14` fixed the same anchoring; this is that fix, ported.
+ * A quoted value is consumed only as a PAIR, and both halves of that matter.
+ * Stepping OVER it is what a plain `[^>]*?` got wrong for two majors: a `>`
+ * inside a binding expression looks like the end of the tag, so
+ * `<wr-checkbox [disabled]="n > 0" value="a">` kept its `value` while the same
+ * attributes in the other order moved. The leftover is SILENT — a static
+ * `value="a"` that matches no input is an ordinary DOM attribute,
+ * `strictTemplates` says nothing, and every checkbox in the group keeps the
+ * default identity `null`, so they all toggle together. That is the exact defect
+ * this migration exists to prevent, reintroduced by the migration itself.
+ *
+ * Never consuming a LONE quote is the half the first fix missed. It spelled the
+ * fallback `[^>]`, which matches a quote too, so the engine could backtrack into
+ * a single-quoted span starting at the apostrophe of `label="it's"` and running
+ * past `/>` into the next element: `<wr-checkbox label="it's" />` followed by
+ * `<wr-select [x]="'y'" value="z" />` renamed the SELECT's form model. Now a rename
+ * stays inside one open tag whenever every quote in it opens or closes a value;
+ * an UNQUOTED value holding a quote (`title=it's`) breaks that, and is skipped.
+ * `migration-v14`'s `IN_TAG` carries the same pattern and the longer account.
  */
-const CHECKBOX_TAG = String.raw `<wr-checkbox(?![-\w])(?:"[^"]*"|'[^']*'|[^>])*?\s`;
+const CHECKBOX_TAG = String.raw `<wr-checkbox(?![-\w])(?:"[^"]*"|'[^']*'|[^>"'])*?\s`;
 const HTML_TRANSFORMS = [
     // <wr-checkbox … value="x">  →  checkboxValue="x"
     { pattern: new RegExp(`(${CHECKBOX_TAG})value=`, 'g'), replacement: '$1checkboxValue=' },

package/schematics/use/symbol-map.json

@@ -165,6 +165,7 @@
   "WrSelect": "ngwr/select",
   "WrOption": "ngwr/select",
   "WrOptionGroup": "ngwr/select",
+  "WrOptionLeading": "ngwr/select",
   "WrShinyText": "ngwr/shiny-text",
   "WrShimmer": "ngwr/shiny-text",
   "WrSidebar": "ngwr/sidebar",

package/select/styles/_index.scss

@@ -120,6 +120,14 @@
     color: var(--wr-color-text-muted);
   }
 
+  // The selected option's leading visual on a single-mode button trigger. Never
+  // shrinks: the label beside it is the part that truncates.
+  &__value-leading {
+    display: inline-flex;
+    flex: none;
+    align-items: center;
+  }
+
   &__chevron {
     --wr-icon-size: 1rem;
     flex: 0 0 auto;
@@ -268,6 +276,17 @@
     user-select: none;
   }
 
+  // A selected option's leading visual — an avatar, an icon. Pulled toward the
+  // chip's start edge so a round avatar reads as the chip's cap rather than as a
+  // glyph floating in the padding, and spaced from the label by a little more
+  // than the chip's own gap.
+  &__chip-leading {
+    display: inline-flex;
+    flex: none;
+    align-items: center;
+    margin-inline: -0.25rem 0.125rem;
+  }
+
   &__chip-label {
     overflow: hidden;
     text-overflow: ellipsis;
@@ -424,6 +443,14 @@
     }
   }
 
+  // An option's leading visual — a sibling of the label inside the row's flex,
+  // so `--wr-option-inline-gap` spaces it like any projected icon.
+  &__leading {
+    display: inline-flex;
+    flex: none;
+    align-items: center;
+  }
+
   // Search-mode filter — out-of-match options collapse but stay in the
   // DOM so registration order survives the panel re-open.
   &--hidden {
@@ -461,6 +488,13 @@
     position: relative;
   }
 
+  // A virtual row is a block, not a flex row (one line, so it can ellipsize),
+  // so the leading visual takes its spacing as a margin instead of the gap.
+  .wr-option__leading {
+    vertical-align: middle;
+    margin-inline-end: var(--wr-option-inline-gap, 0.5rem);
+  }
+
   // Keyboard cursor highlight — the virtualized list is navigated by
   // aria-activedescendant, so real focus never lands on the row and the tint
   // is all there was. `--wr-color-hover` is translucent and lands within about

package/skills/ngwr/SKILL.md

@@ -44,8 +44,13 @@ guess gets backwards.
 - **There is no `ControlValueAccessor`.** Value components implement Signal
   Forms' `FormValueControl` / `FormCheckboxControl`. Bind
   `[formField]="form.x"`, or use the two-way model standalone —
-  `[(value)]`, `[(checked)]`. `[(ngModel)]` and reactive forms still work:
-  Angular 22 synthesises the accessor.
+  `[(value)]`, `[(checked)]`. `[(ngModel)]` and reactive forms still bind,
+  with no accessor created: Angular's `NgModel` / `FormControlDirective` drive
+  the `value` or `checked` model directly. That bridge does NOT apply template
+  validator directives — `required`, `minlength`, `maxlength`, `pattern` or
+  `email` on an ngwr control is silently ignored and the form submits — so put
+  validators on the `FormControl`. It also ignores `updateOn`, and a
+  `{ emitEvent: false }` write needs `markForCheck()`.
 - **`<wr-checkbox>` group identity is `checkboxValue`, not `value`.**
   `value` is reserved for the form value, so a leftover `value="x"` lands on the
   host as a plain DOM attribute, every box in the group keeps the default
@@ -95,8 +100,8 @@ cause.
 - `provideWrLoadingBarRouter() // from 'ngwr/loading-bar/router'`
   — without it the bar never responds to navigation; it only moves for manual start() / complete()
   — needed by: `WrLoadingBar`
-- `provideWrI18n() + provideWrI18nStaticLoader({ en: wrEn }) // from 'ngwr/i18n' + 'ngwr/i18n/en'`
-  — the pipe and directive read from a catalog you provide
+- `provideWrI18n() + provideWrI18nBaseCatalogs({ en: wrEn }) + provideWrI18nStaticLoader({ en: { … } }) // from 'ngwr/i18n' + 'ngwr/i18n/en'`
+  — the pipe and directive read from a catalog you provide. Register ngwr's with `provideWrI18nBaseCatalogs`, never spread it into yours: a spread is shallow, so any namespace you share with ngwr, e.g. `common`, `validation`, `table`, keeps only the side spread last, and the other side's keys stop resolving with nothing logged — ngwr's components fall back to English and a `wrT` read of a lost key renders the raw key
   — needed by: `WrTPipe`, `WrTDirective`, `WrI18n`
 
 ## Testing

package/skills/ngwr/references/catalog.md

@@ -171,7 +171,7 @@ root barrel for components.
 | `ngwr/scroll` | `import { WrScroll } from 'ngwr/scroll'` | — |
 | `ngwr/segmented` | `import { WrSegmented } from 'ngwr/segmented'` | `wr-segmented` |
 | `ngwr/segmented/testing` | `import { WrSegmentedHarness } from 'ngwr/segmented/testing'` | — |
-| `ngwr/select` | `import { WrSelect } from 'ngwr/select'` | `wr-option-group` `wr-option` `wr-select` |
+| `ngwr/select` | `import { WrSelect } from 'ngwr/select'` | `wr-option-group` `ng-template[wrOptionLeading]` `wr-option` `wr-select` |
 | `ngwr/select/testing` | `import { WrOptionHarness } from 'ngwr/select/testing'` | — |
 | `ngwr/shiny-text` | `import { WrShinyText } from 'ngwr/shiny-text'` | `[wrShimmer]` `wr-shiny-text` |
 | `ngwr/shiny-text/testing` | `import { WrShinyTextHarness } from 'ngwr/shiny-text/testing'` | — |

package/skills/ngwr/references/setup.md

@@ -60,9 +60,9 @@ Every date mode goes through an adapter; there is no built-in default. Needed by
 
 Without it the bar never responds to navigation; it only moves for manual start() / complete(). Needed by `WrLoadingBar`.
 
-### `provideWrI18n() + provideWrI18nStaticLoader({ en: wrEn }) // from 'ngwr/i18n' + 'ngwr/i18n/en'`
+### `provideWrI18n() + provideWrI18nBaseCatalogs({ en: wrEn }) + provideWrI18nStaticLoader({ en: { … } }) // from 'ngwr/i18n' + 'ngwr/i18n/en'`
 
-The pipe and directive read from a catalog you provide. Needed by `WrTPipe`, `WrTDirective`, `WrI18n`.
+The pipe and directive read from a catalog you provide. Register ngwr's with `provideWrI18nBaseCatalogs`, never spread it into yours: a spread is shallow, so any namespace you share with ngwr, e.g. `common`, `validation`, `table`, keeps only the side spread last, and the other side's keys stop resolving with nothing logged — ngwr's components fall back to English and a `wrT` read of a lost key renders the raw key. Needed by `WrTPipe`, `WrTDirective`, `WrI18n`.
 
 ## Optional, app-wide