@vit-foundation/ui 0.18.0 → 0.20.0

package/README.md

@@ -31,6 +31,7 @@ Everything exports flat from the root, and again grouped by role:
 | [`/community`](./docs/components/community.md)                  | AuthPageShell, LoginForm, SignupForm, GoogleAuthForm, AccountPanel, NewsletterSignup, CommentSection, ReactionBar, ContactForm                                                                           |
 | [`/edit`](./docs/edit-mode.md)                                  | Editable, setEditAdapter/getEditAdapter, descriptors and helpers, collectionEditing, LocalizedText                                                                                                       |
 | [`/config`](./docs/getting-started.md#wiring-an-app-uiprovider) | UiProvider, UiConfig, the locale set, the default Catalan messages                                                                                                                                       |
+| `/contract`                                                     | The component-free half: LOCALES, BASE_LOCALE, localize, REACTIONS and the edit-descriptor types — the one subpath a host may import from SERVER code                                                    |
 | `/testing`                                                      | createRemoteFormMock — the remote-form stand-in for stories and tests                                                                                                                                    |
 
 Every component renders standalone (Catalan copy, identity hrefs); an app
@@ -83,5 +84,8 @@ diffable against history. The public structure is the semantic entry points
 above, assembled in `src/lib/{primitives,chrome,content-components,community}.ts`
 and `src/lib/forms/index.ts`.
 
-Releases: bump with `npm version`, push the `v*` tag, and the release
-workflow publishes to npm (requires the `NPM_TOKEN` secret).
+Releases are MANUAL: bump with `npm version`, then `npm publish`. The
+workflow this paragraph used to describe fired on every `v*` tag, had no
+`NPM_TOKEN` and no lint, check or test step, so it failed every time and was
+deleted; `prepublishOnly` (lint, check, unit tests) is the only publish gate
+now. Push the tag by all means — nothing reads it.

package/dist/contract.d.ts

@@ -0,0 +1,29 @@
+/**
+ * The contract, without the components: the vocabularies and the one reading
+ * rule a host needs on the SERVER, where a `.svelte` import cannot go.
+ *
+ * Every other subpath mixes the two. `./edit` exports `localize` beside
+ * `Editable.svelte`; `./config` exports `LOCALES` and `BASE_LOCALE` beside
+ * `UiProvider.svelte`; `./content` exports `REACTIONS` beside the cards. A
+ * host whose server code wants those VALUES has to import the barrel that
+ * drags a component graph into a server bundle, so vit-brain imported the
+ * types only and restated the values: `WEBSITE_LOCALES`, `CANONICAL_LOCALE`,
+ * its own `REACTIONS`, and a `hasLocalizedText` re-derived from `localize`'s
+ * body — four facts this package owns, one of them (the canonical locale)
+ * with no binding at all.
+ *
+ * So this subpath is the seam that restatement was standing in for. It is
+ * component-free BY TEST (`contract.test.ts` walks its import graph), which
+ * is what makes it a promise rather than a description: adding a `.svelte`
+ * anywhere beneath it fails here rather than in a consumer's server build.
+ *
+ * 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.
+ */
+export { LOCALES, BASE_LOCALE } from './config/types.js';
+export type { Locale, NotParameterized, ParameterizedKey, ParameterlessKey, SiteLink, UiMessages } from './config/types.js';
+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';

package/dist/contract.js

@@ -0,0 +1,26 @@
+/**
+ * The contract, without the components: the vocabularies and the one reading
+ * rule a host needs on the SERVER, where a `.svelte` import cannot go.
+ *
+ * Every other subpath mixes the two. `./edit` exports `localize` beside
+ * `Editable.svelte`; `./config` exports `LOCALES` and `BASE_LOCALE` beside
+ * `UiProvider.svelte`; `./content` exports `REACTIONS` beside the cards. A
+ * host whose server code wants those VALUES has to import the barrel that
+ * drags a component graph into a server bundle, so vit-brain imported the
+ * types only and restated the values: `WEBSITE_LOCALES`, `CANONICAL_LOCALE`,
+ * its own `REACTIONS`, and a `hasLocalizedText` re-derived from `localize`'s
+ * body — four facts this package owns, one of them (the canonical locale)
+ * with no binding at all.
+ *
+ * So this subpath is the seam that restatement was standing in for. It is
+ * component-free BY TEST (`contract.test.ts` walks its import graph), which
+ * is what makes it a promise rather than a description: adding a `.svelte`
+ * anywhere beneath it fails here rather than in a consumer's server build.
+ *
+ * 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.
+ */
+export { LOCALES, BASE_LOCALE } from './config/types.js';
+export { localize } from './edit/types.js';
+export { REACTIONS } from './content/types.js';

package/dist/index.d.ts

@@ -6,4 +6,4 @@ export * from './admin.js';
 export * from './forms/index.js';
 export * from './config/index.js';
 export * from './edit/index.js';
-export { buildQueryString, isExternalUrl, isInternalPath, isPathUnder } from './utils/paths.js';
+export { buildQueryString } from './utils/paths.js';

package/dist/index.js

@@ -12,5 +12,13 @@ export * from './forms/index.js';
 // App wiring: configuration context and the edit-mode contract.
 export * from './config/index.js';
 export * from './edit/index.js';
-// Path utilities shared with host apps.
-export { buildQueryString, isExternalUrl, isInternalPath, isPathUnder } from './utils/paths.js';
+// The one path utility a host actually reads: fndvit-website re-exports
+// `buildQueryString` from its own `utils/nav.ts`, so the URL a list mirrors
+// and the hrefs it renders are spelled by this function in both codebases.
+// The other three are NOT exported. `isInternalPath` and `isExternalUrl` are
+// the destination classifiers `Link` and `TimelineMilestone` branch on, and
+// `isPathUnder` is the prefix match `Nav` and `Sidebar` highlight the current
+// section with — all four in-package readers reach them by deep import, and
+// no host imports any of the three. Exporting them would pin their behaviour
+// into semver for no reader; `paths.test.ts` is what holds them instead.
+export { buildQueryString } from './utils/paths.js';

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

@@ -5,10 +5,21 @@ import type { SortDirection, WeeklyCardData } from '../content/types.js';
  * 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 = {

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

@@ -5,8 +5,18 @@ import { createUrlFilters } from './url-filters.svelte.js';
  * 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 };
+export const WEEKLY_LIST_DEFAULTS = { sort: 'desc', page: 1, pageSize: 12 };
 /** The index's path, shared by the mirrored URL and the paging hrefs. */
 const WEEKLIES_PATH = '/weeklies';
 /**

package/package.json

@@ -1,13 +1,13 @@
 {
 	"name": "@vit-foundation/ui",
-	"version": "0.18.0",
+	"version": "0.20.0",
 	"scripts": {
 		"dev": "vite dev",
 		"build": "vite build && npm run prepack",
 		"preview": "vite preview",
 		"prepare": "svelte-kit sync || echo ''",
 		"prepack": "svelte-kit sync && svelte-package && publint",
-		"_comment:prepublishOnly": "Publishing is MANUAL (the release workflow has no NPM_TOKEN and fails on every tag), so the gate belongs on the command that actually publishes. npm runs this before prepack.",
+		"_comment:prepublishOnly": "Publishing is MANUAL — the release workflow that fired on every v* tag had no NPM_TOKEN, failed every time, and was deleted, so this is the ONLY publish gate. npm runs it before prepack.",
 		"prepublishOnly": "npm run lint && npm run check && npm run test:unit -- --run",
 		"check": "svelte-kit sync && svelte-check --tsconfig ./tsconfig.json",
 		"check:watch": "svelte-kit sync && svelte-check --tsconfig ./tsconfig.json --watch",
@@ -69,6 +69,11 @@
 			"svelte": "./dist/edit/index.js",
 			"default": "./dist/edit/index.js"
 		},
+		"./contract": {
+			"types": "./dist/contract.d.ts",
+			"svelte": "./dist/contract.js",
+			"default": "./dist/contract.js"
+		},
 		"./config": {
 			"types": "./dist/config/index.d.ts",
 			"svelte": "./dist/config/index.js",