@vit-foundation/ui 0.20.0 → 0.21.0

package/dist/config/types.d.ts

@@ -9,7 +9,14 @@ import type { EditMessages } from './edit-messages.js';
  */
 export declare const LOCALES: readonly ["ca", "en", "es"];
 export type Locale = (typeof LOCALES)[number];
-export declare const BASE_LOCALE: Locale;
+/**
+ * Declared as the LITERAL, not widened to `Locale`. `Exclude<Locale, typeof
+ * BASE_LOCALE>` is how a host names "the locales that are not canonical" —
+ * the set a translations editor fills from the canonical one — and the
+ * annotation threw that away, resolving it to `never`. A consumer that wants
+ * the wide type can still write `const l: Locale = BASE_LOCALE`.
+ */
+export declare const BASE_LOCALE = "ca";
 /** One primary-navigation entry, rendered by Nav and repeated by Footer. */
 export interface SiteLink {
     /** Present only where the nav is editable — structural ops need identity. */

package/dist/config/types.js

@@ -6,4 +6,11 @@
  * consumer option.
  */
 export const LOCALES = ['ca', 'en', 'es'];
+/**
+ * Declared as the LITERAL, not widened to `Locale`. `Exclude<Locale, typeof
+ * BASE_LOCALE>` is how a host names "the locales that are not canonical" —
+ * the set a translations editor fills from the canonical one — and the
+ * annotation threw that away, resolving it to `never`. A consumer that wants
+ * the wide type can still write `const l: Locale = BASE_LOCALE`.
+ */
 export const BASE_LOCALE = 'ca';

package/dist/content-components.d.ts

@@ -21,7 +21,9 @@ export * from './content/index.js';
 export { MILESTONE_CATEGORY_COLOR, matchesMilestoneFilter, milestoneCategoryLabel } from './utils/milestones.js';
 export { createUrlFilters } from './utils/url-filters.svelte.js';
 export type { UrlFilters, UrlFiltersConfig } from './utils/url-filters.svelte.js';
-export { createWeeklyList, WEEKLY_LIST_DEFAULTS } from './utils/weekly-list.svelte.js';
-export type { WeeklyList, WeeklyListConfig, WeeklyListFilters, WeeklyListPage, WeeklyListServerData } from './utils/weekly-list.svelte.js';
+export { createWeeklyList } from './utils/weekly-list.svelte.js';
+export type { WeeklyList, WeeklyListConfig } from './utils/weekly-list.svelte.js';
+export { WEEKLY_LIST_DEFAULTS } from './utils/weekly-list-contract.js';
+export type { WeeklyListFilters, WeeklyListPage, WeeklyListServerData } from './utils/weekly-list-contract.js';
 export { contactCategoryLabel } from './utils/contact.js';
 export { formatDate, yearOf } from './utils/dates.js';

package/dist/content-components.js

@@ -15,6 +15,9 @@ export * from './content/index.js';
 export { MILESTONE_CATEGORY_COLOR, matchesMilestoneFilter, milestoneCategoryLabel } from './utils/milestones.js';
 // The two list rules: URL-mirrored filters, and the weeklies index over them.
 export { createUrlFilters } from './utils/url-filters.svelte.js';
-export { createWeeklyList, WEEKLY_LIST_DEFAULTS } from './utils/weekly-list.svelte.js';
+export { createWeeklyList } from './utils/weekly-list.svelte.js';
+// The list's contract is component-free on purpose, so ./contract carries it
+// too — a host's +page.server.ts reads these without loading the grid.
+export { WEEKLY_LIST_DEFAULTS } from './utils/weekly-list-contract.js';
 export { contactCategoryLabel } from './utils/contact.js';
 export { formatDate, yearOf } from './utils/dates.js';

package/dist/contract.d.ts

@@ -20,6 +20,22 @@
  * It adds nothing. Every name below is already exported from a semantic
  * subpath and stays there — this is a second door into the same rooms, not a
  * new floor, and the barrel remains the surface a component host reads.
+ *
+ * It was cut to fit ONE consumer, and the second one did not fit through it.
+ * vit-brain's four restatements were the motive, so the first version carried
+ * the locale vocabulary, the edit contract and REACTIONS — and of the fifteen
+ * names fndvit-website's SERVER modules take from the barrel, it covered
+ * exactly one. Its `schemas/{common,auth,comment,contact}.ts` and
+ * `remote/result.ts` are read by `server/auth.ts`, `server/form-action.ts` and
+ * eleven repositories, so that site reaches a sixty-component graph to obtain
+ * string bounds and a hidden field's name.
+ *
+ * The fix moved no files, which is the tell that the seam was in the right
+ * place and merely too narrow: `forms/constraints.ts`, `forms/transport.ts`,
+ * `forms/types.ts` and `utils/paths.ts` were ALREADY component-free leaves —
+ * they import nothing but `content/types.js`, or nothing at all. They were
+ * what this subpath promises, with no door onto them. Now there is one, and
+ * the guard walks them like the rest.
  */
 export { LOCALES, BASE_LOCALE } from './config/types.js';
 export type { Locale, NotParameterized, ParameterizedKey, ParameterlessKey, SiteLink, UiMessages } from './config/types.js';
@@ -27,3 +43,11 @@ export { localize } from './edit/types.js';
 export type { CollectionRef, ContentRef, EditableEntity, EditDescriptor, EntityOp, LocalizedText, PropertyDescriptor, PropertyOption, PropertyType, PropertyValue } from './edit/types.js';
 export { REACTIONS } from './content/types.js';
 export type { Reaction, ReactionSummary, SortDirection } from './content/types.js';
+export { WEEKLY_LIST_DEFAULTS } from './utils/weekly-list-contract.js';
+export type { WeeklyListFilters, WeeklyListPage, WeeklyListServerData } from './utils/weekly-list-contract.js';
+export { CONTACT_CATEGORIES } from './content/types.js';
+export type { ContactCategory, FieldConstraint, FormFailReason } from './content/types.js';
+export { COMMENT_BODY, CONTACT_MESSAGE, CONTACT_NAME, DISPLAY_NAME, EMAIL, LOGIN_PASSWORD, PASSWORD } from './forms/constraints.js';
+export { hasNewsletterIntent, HONEYPOT_FIELD, isNewsletterIntent, NEWSLETTER_INTENT_PARAM, NEWSLETTER_INTENT_VALUE, withNewsletterIntent } from './forms/transport.js';
+export type { FormFail, FormFieldIssue, FormResultLike, FormResultOf, KeyedRemoteForms, RemoteField, RemoteFormAttributes, RemoteFormInstance } from './forms/types.js';
+export { buildQueryString, isExternalUrl, isInternalPath, isPathUnder } from './utils/paths.js';

package/dist/contract.js

@@ -20,7 +20,28 @@
  * It adds nothing. Every name below is already exported from a semantic
  * subpath and stays there — this is a second door into the same rooms, not a
  * new floor, and the barrel remains the surface a component host reads.
+ *
+ * It was cut to fit ONE consumer, and the second one did not fit through it.
+ * vit-brain's four restatements were the motive, so the first version carried
+ * the locale vocabulary, the edit contract and REACTIONS — and of the fifteen
+ * names fndvit-website's SERVER modules take from the barrel, it covered
+ * exactly one. Its `schemas/{common,auth,comment,contact}.ts` and
+ * `remote/result.ts` are read by `server/auth.ts`, `server/form-action.ts` and
+ * eleven repositories, so that site reaches a sixty-component graph to obtain
+ * string bounds and a hidden field's name.
+ *
+ * The fix moved no files, which is the tell that the seam was in the right
+ * place and merely too narrow: `forms/constraints.ts`, `forms/transport.ts`,
+ * `forms/types.ts` and `utils/paths.ts` were ALREADY component-free leaves —
+ * they import nothing but `content/types.js`, or nothing at all. They were
+ * what this subpath promises, with no door onto them. Now there is one, and
+ * the guard walks them like the rest.
  */
 export { LOCALES, BASE_LOCALE } from './config/types.js';
 export { localize } from './edit/types.js';
 export { REACTIONS } from './content/types.js';
+export { WEEKLY_LIST_DEFAULTS } from './utils/weekly-list-contract.js';
+export { CONTACT_CATEGORIES } from './content/types.js';
+export { COMMENT_BODY, CONTACT_MESSAGE, CONTACT_NAME, DISPLAY_NAME, EMAIL, LOGIN_PASSWORD, PASSWORD } from './forms/constraints.js';
+export { hasNewsletterIntent, HONEYPOT_FIELD, isNewsletterIntent, NEWSLETTER_INTENT_PARAM, NEWSLETTER_INTENT_VALUE, withNewsletterIntent } from './forms/transport.js';
+export { buildQueryString, isExternalUrl, isInternalPath, isPathUnder } from './utils/paths.js';

package/dist/utils/weekly-list-contract.d.ts

@@ -0,0 +1,66 @@
+import type { SortDirection, WeeklyCardData } from '../content/types.js';
+/**
+ * The weeklies index's contract, without the view that runs it.
+ *
+ * `createWeeklyList` needs the Svelte compiler — four `$state` cells, an
+ * `$effect` and three `$derived` — so it lives in a `.svelte.ts` rune module.
+ * These four names do not: they are what a HOST has to agree with this
+ * package about before any of that runs, and a host agrees with them on the
+ * server. `+page.server.ts` builds `WeeklyListServerData`, a query schema
+ * takes its defaults from `WEEKLY_LIST_DEFAULTS`, and a repository answers
+ * `WeeklyListPage`.
+ *
+ * They were in the rune module, which put them behind `./content` — eight
+ * components — and, worse, out of reach of `./contract` altogether, because
+ * that subpath's guard refuses a rune module by name (they need the
+ * compiler, so a server import of one is the defect the guard exists to
+ * catch). So the release that gave `pageSize` an owner, to end a restatement
+ * in two repositories that cannot import each other, shipped it where
+ * neither host's server could import it: fndvit-website's
+ * `schemas/weekly.ts` reaches it through `./content` and is itself read by
+ * `routes/weeklies/+page.server.ts`.
+ *
+ * Splitting the file is the whole fix. Nothing moves for a component host —
+ * `./content` still exports every name from here — and the four facts a
+ * server needs stop being locked behind a graph it must not load.
+ */
+/**
+ * The weeklies index's URL defaults: the value a param stands for when it is
+ * absent. Both halves of the URL contract — `createWeeklyList` omitting a
+ * default, the host's query schema supplying one — must name the same values,
+ * so a host derives its schema defaults from here rather than restating them.
+ *
+ * `pageSize` is here for the same reason one step further out. It is not a
+ * URL param: it is what a page of this list HOLDS, which the grid this
+ * package renders decides. Every host was spelling its own — fndvit-website
+ * as `WEEKLIES_PAGE_SIZE`, vit-brain's mirror as a bare `12` in markup — and
+ * the two must agree, because the mirror exists to page the same corpus the
+ * site pages. Two repositories that cannot import each other were each
+ * holding half of one number. `createWeeklyList` still READS the size from
+ * `config.server().pageSize`, so a host may still answer something else; this
+ * is the value it should answer unless it means to differ.
+ */
+export declare const WEEKLY_LIST_DEFAULTS: {
+    readonly sort: "desc";
+    readonly page: 1;
+    readonly pageSize: 12;
+};
+/** A type alias, not an interface: createUrlFilters needs an index signature. */
+export type WeeklyListFilters = {
+    q: string;
+    theme: string | null;
+    sort: SortDirection;
+};
+/** One page of the list plus the unpaged total (for the pagination). */
+export interface WeeklyListPage {
+    items: WeeklyCardData[];
+    total: number;
+}
+/** The server-rendered page, re-read on every navigation. */
+export interface WeeklyListServerData {
+    weeklies: WeeklyCardData[];
+    total: number;
+    page: number;
+    pageSize: number;
+    query: WeeklyListFilters;
+}

package/dist/utils/weekly-list-contract.js

@@ -0,0 +1,42 @@
+/**
+ * The weeklies index's contract, without the view that runs it.
+ *
+ * `createWeeklyList` needs the Svelte compiler — four `$state` cells, an
+ * `$effect` and three `$derived` — so it lives in a `.svelte.ts` rune module.
+ * These four names do not: they are what a HOST has to agree with this
+ * package about before any of that runs, and a host agrees with them on the
+ * server. `+page.server.ts` builds `WeeklyListServerData`, a query schema
+ * takes its defaults from `WEEKLY_LIST_DEFAULTS`, and a repository answers
+ * `WeeklyListPage`.
+ *
+ * They were in the rune module, which put them behind `./content` — eight
+ * components — and, worse, out of reach of `./contract` altogether, because
+ * that subpath's guard refuses a rune module by name (they need the
+ * compiler, so a server import of one is the defect the guard exists to
+ * catch). So the release that gave `pageSize` an owner, to end a restatement
+ * in two repositories that cannot import each other, shipped it where
+ * neither host's server could import it: fndvit-website's
+ * `schemas/weekly.ts` reaches it through `./content` and is itself read by
+ * `routes/weeklies/+page.server.ts`.
+ *
+ * Splitting the file is the whole fix. Nothing moves for a component host —
+ * `./content` still exports every name from here — and the four facts a
+ * server needs stop being locked behind a graph it must not load.
+ */
+/**
+ * The weeklies index's URL defaults: the value a param stands for when it is
+ * absent. Both halves of the URL contract — `createWeeklyList` omitting a
+ * default, the host's query schema supplying one — must name the same values,
+ * so a host derives its schema defaults from here rather than restating them.
+ *
+ * `pageSize` is here for the same reason one step further out. It is not a
+ * URL param: it is what a page of this list HOLDS, which the grid this
+ * package renders decides. Every host was spelling its own — fndvit-website
+ * as `WEEKLIES_PAGE_SIZE`, vit-brain's mirror as a bare `12` in markup — and
+ * the two must agree, because the mirror exists to page the same corpus the
+ * site pages. Two repositories that cannot import each other were each
+ * holding half of one number. `createWeeklyList` still READS the size from
+ * `config.server().pageSize`, so a host may still answer something else; this
+ * is the value it should answer unless it means to differ.
+ */
+export const WEEKLY_LIST_DEFAULTS = { sort: 'desc', page: 1, pageSize: 12 };

package/dist/utils/weekly-list.svelte.d.ts

@@ -1,45 +1,6 @@
 import type { Locale } from '../config/types.js';
 import type { SortDirection, WeeklyCardData } from '../content/types.js';
-/**
- * The weeklies index's URL defaults: the value a param stands for when it is
- * absent. Both halves of the URL contract — this module omitting a default,
- * the host's query schema supplying one — must name the same values, so a
- * host derives its schema defaults from here rather than restating them.
- *
- * `pageSize` is here for the same reason one step further out. It is not a
- * URL param: it is what a page of this list HOLDS, which the grid this
- * package renders decides. Every host was spelling its own — fndvit-website
- * as `WEEKLIES_PAGE_SIZE`, vit-brain's mirror as a bare `12` in markup — and
- * the two must agree, because the mirror exists to page the same corpus the
- * site pages. Two repositories that cannot import each other were each
- * holding half of one number. `createWeeklyList` still READS the size from
- * `config.server().pageSize`, so a host may still answer something else; this
- * is the value it should answer unless it means to differ.
- */
-export declare const WEEKLY_LIST_DEFAULTS: {
-    readonly sort: "desc";
-    readonly page: 1;
-    readonly pageSize: 12;
-};
-/** A type alias, not an interface: createUrlFilters needs an index signature. */
-export type WeeklyListFilters = {
-    q: string;
-    theme: string | null;
-    sort: SortDirection;
-};
-/** One page of the list plus the unpaged total (for the pagination). */
-export interface WeeklyListPage {
-    items: WeeklyCardData[];
-    total: number;
-}
-/** The server-rendered page, re-read on every navigation. */
-export interface WeeklyListServerData {
-    weeklies: WeeklyCardData[];
-    total: number;
-    page: number;
-    pageSize: number;
-    query: WeeklyListFilters;
-}
+import type { WeeklyListFilters, WeeklyListPage, WeeklyListServerData } from './weekly-list-contract.js';
 export interface WeeklyListConfig {
     /** Reads the route's `data`; called inside an effect, so it tracks it. */
     server: () => WeeklyListServerData;

package/dist/utils/weekly-list.svelte.js

@@ -1,22 +1,6 @@
 import { buildQueryString } from './paths.js';
 import { createUrlFilters } from './url-filters.svelte.js';
-/**
- * The weeklies index's URL defaults: the value a param stands for when it is
- * absent. Both halves of the URL contract — this module omitting a default,
- * the host's query schema supplying one — must name the same values, so a
- * host derives its schema defaults from here rather than restating them.
- *
- * `pageSize` is here for the same reason one step further out. It is not a
- * URL param: it is what a page of this list HOLDS, which the grid this
- * package renders decides. Every host was spelling its own — fndvit-website
- * as `WEEKLIES_PAGE_SIZE`, vit-brain's mirror as a bare `12` in markup — and
- * the two must agree, because the mirror exists to page the same corpus the
- * site pages. Two repositories that cannot import each other were each
- * holding half of one number. `createWeeklyList` still READS the size from
- * `config.server().pageSize`, so a host may still answer something else; this
- * is the value it should answer unless it means to differ.
- */
-export const WEEKLY_LIST_DEFAULTS = { sort: 'desc', page: 1, pageSize: 12 };
+import { WEEKLY_LIST_DEFAULTS } from './weekly-list-contract.js';
 /** The index's path, shared by the mirrored URL and the paging hrefs. */
 const WEEKLIES_PATH = '/weeklies';
 /**

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@vit-foundation/ui",
-	"version": "0.20.0",
+	"version": "0.21.0",
 	"scripts": {
 		"dev": "vite dev",
 		"build": "vite build && npm run prepack",