@vit-foundation/ui 0.20.1 → 0.22.0

package/dist/components/timeline/TimelineMilestone.svelte

@@ -25,7 +25,7 @@
 <script lang="ts">
 	import { getUiConfig } from '../../config/context.js';
 	import ActionLabel from '../../edit/ActionLabel.svelte';
-	import type { MilestoneCategory, MilestoneData } from '../../content/types.js';
+	import { MILESTONE_CATEGORIES, type MilestoneData } from '../../content/types.js';
 	import EditFrame from '../../edit/chrome/EditFrame.svelte';
 	import EditPanel from '../../edit/chrome/EditPanel.svelte';
 	import Editable from '../../edit/Editable.svelte';
@@ -46,7 +46,7 @@
 
 	const config = getUiConfig();
 
-	const CATEGORIES = Object.keys(MILESTONE_CATEGORY_COLOR) as MilestoneCategory[];
+	// The set's own order, not a colour map's key order and not a cast.
 
 	/**
 	 * The panel rows, zipped from the map's descriptors and this milestone's
@@ -58,7 +58,7 @@
 			edit?.occurredOn && { descriptor: edit.occurredOn, value: milestone.occurredOn },
 			edit?.category && {
 				descriptor: {
-					options: CATEGORIES.map((category) => ({
+					options: MILESTONE_CATEGORIES.map((category) => ({
 						value: category,
 						label: milestoneCategoryLabel(category, config.messages)
 					})),

package/dist/components/timeline/TimelineMilestone.svelte.d.ts

@@ -20,7 +20,7 @@ export interface MilestoneEditMap {
         kind: 'remove';
     }>;
 }
-import type { MilestoneData } from '../../content/types.js';
+import { type MilestoneData } from '../../content/types.js';
 interface Props {
     milestone: MilestoneData;
     /** Marks fields editable where an edit adapter is active. */

package/dist/content/index.d.ts

@@ -1,4 +1,4 @@
 export { renderBody } from './richtext.js';
 export type { RichTextBlock } from './richtext.js';
-export { CONTACT_CATEGORIES, REACTIONS } from './types.js';
+export { CONTACT_CATEGORIES, MILESTONE_CATEGORIES, PROJECT_KINDS, REACTIONS } from './types.js';
 export type { CollaboratorData, CommentData, CommentThreadData, ContactCategory, FieldConstraint, FormFailReason, JobOpeningData, MilestoneCategory, MilestoneData, ProjectCardData, ProjectKind, Reaction, ReactionSummary, ReactionTarget, SortDirection, TeamMemberData, WeeklyCardData } from './types.js';

package/dist/content/index.js

@@ -1,2 +1,2 @@
 export { renderBody } from './richtext.js';
-export { CONTACT_CATEGORIES, REACTIONS } from './types.js';
+export { CONTACT_CATEGORIES, MILESTONE_CATEGORIES, PROJECT_KINDS, REACTIONS } from './types.js';

package/dist/content/types.d.ts

@@ -28,7 +28,9 @@ export interface WeeklyCardData {
     excerpt: string;
     imageUrl: string;
 }
-export type ProjectKind = 'collaboration' | 'passion';
+/** The kinds a project can have, in display order — a host's enum derives from this. */
+export declare const PROJECT_KINDS: readonly ["collaboration", "passion"];
+export type ProjectKind = (typeof PROJECT_KINDS)[number];
 /** A project as its card shows it. */
 export interface ProjectCardData {
     id: number;
@@ -43,7 +45,23 @@ export interface ProjectCardData {
     externalUrl: string | null;
     hasStory: boolean;
 }
-export type MilestoneCategory = 'education' | 'lab' | 'foundation' | 'collaboration' | 'press';
+/**
+ * The timeline's categories, in DISPLAY ORDER — every select that offers them
+ * and every host enum derives from this.
+ *
+ * The order was an emergent property of two unrelated literals before: the
+ * panel select read `Object.keys(MILESTONE_CATEGORY_COLOR)` while vit-brain's
+ * record form spelled its own array, so one CMS offered the same field in two
+ * orders and seeded a new row with the third member of one of them. The order
+ * kept here is the colour map's, which is the one with a reason attached (its
+ * slots are fixed and never reordered).
+ *
+ * A tuple rather than a union for the reason `CONTACT_CATEGORIES` is one: a
+ * `satisfies readonly MilestoneCategory[]` binds the element type and never
+ * the list, so a host could drop a member and still compile.
+ */
+export declare const MILESTONE_CATEGORIES: readonly ["foundation", "lab", "education", "collaboration", "press"];
+export type MilestoneCategory = (typeof MILESTONE_CATEGORIES)[number];
 /** One timeline milestone. */
 export interface MilestoneData {
     id: number;

package/dist/content/types.js

@@ -3,6 +3,30 @@
  * applied. The website's zod-inferred types satisfy these structurally; the
  * package states them itself so consumers owe it no schema library.
  */
+/** The kinds a project can have, in display order — a host's enum derives from this. */
+export const PROJECT_KINDS = ['collaboration', 'passion'];
+/**
+ * The timeline's categories, in DISPLAY ORDER — every select that offers them
+ * and every host enum derives from this.
+ *
+ * The order was an emergent property of two unrelated literals before: the
+ * panel select read `Object.keys(MILESTONE_CATEGORY_COLOR)` while vit-brain's
+ * record form spelled its own array, so one CMS offered the same field in two
+ * orders and seeded a new row with the third member of one of them. The order
+ * kept here is the colour map's, which is the one with a reason attached (its
+ * slots are fixed and never reordered).
+ *
+ * A tuple rather than a union for the reason `CONTACT_CATEGORIES` is one: a
+ * `satisfies readonly MilestoneCategory[]` binds the element type and never
+ * the list, so a host could drop a member and still compile.
+ */
+export const MILESTONE_CATEGORIES = [
+    'foundation',
+    'lab',
+    'education',
+    'collaboration',
+    'press'
+];
 /** The reactions a weekly or comment can carry, in display order. */
 export const REACTIONS = ['like', 'love', 'clap'];
 /** The contact form's reasons, in display order — the host schema derives its enum from this. */

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,25 @@ 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 { MILESTONE_CATEGORIES, PROJECT_KINDS } from './content/types.js';
+export type { MilestoneCategory, ProjectKind } 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';
+/**
+ * The descriptor factories. `edit/helpers.ts` imports nothing but types from
+ * two modules this subpath already anchors, so it needed a door rather than a
+ * split.
+ *
+ * They were reachable only beside the components, which cost vit-brain an
+ * eslint exception that switched `no-restricted-imports` off WHOLESALE for the
+ * two files calling one factory each — and one of those, `mirror.ts`, is
+ * already reached from a server repository by `import type`. A per-specifier
+ * door replaces a per-file hole.
+ */
+export { chromeEdit, chromeProperty, collectionOf, entityEdit, entityProperty, pageCopyEdit } from './edit/helpers.js';

package/dist/contract.js

@@ -20,7 +20,44 @@
  * 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';
+// The two content vocabularies a host's zod enum derives from, the way its
+// contact form already derives from CONTACT_CATEGORIES below. Values, because
+// a type cannot be the source of an enum.
+export { MILESTONE_CATEGORIES, PROJECT_KINDS } 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';
+/**
+ * The descriptor factories. `edit/helpers.ts` imports nothing but types from
+ * two modules this subpath already anchors, so it needed a door rather than a
+ * split.
+ *
+ * They were reachable only beside the components, which cost vit-brain an
+ * eslint exception that switched `no-restricted-imports` off WHOLESALE for the
+ * two files calling one factory each — and one of those, `mirror.ts`, is
+ * already reached from a server repository by `import type`. A per-specifier
+ * door replaces a per-file hole.
+ */
+export { chromeEdit, chromeProperty, collectionOf, entityEdit, entityProperty, pageCopyEdit } from './edit/helpers.js';

package/dist/utils/milestones.d.ts

@@ -5,6 +5,11 @@ import type { MilestoneCategory } from '../content/types.js';
  * teal, slots are never reordered). Labels always accompany the color dot,
  * so color is never the only encoding. The --series-* tokens ship in
  * tokens.css.
+ *
+ * Keyed, not positional, so a member added to `MILESTONE_CATEGORIES` fails to
+ * compile here rather than silently taking slot 6 — and so the display order
+ * is `MILESTONE_CATEGORIES`' to decide, not a side effect of this literal's
+ * key order, which is what the panel select used to read.
  */
 export declare const MILESTONE_CATEGORY_COLOR: Record<MilestoneCategory, string>;
 /**

package/dist/utils/milestones.js

@@ -3,6 +3,11 @@
  * teal, slots are never reordered). Labels always accompany the color dot,
  * so color is never the only encoding. The --series-* tokens ship in
  * tokens.css.
+ *
+ * Keyed, not positional, so a member added to `MILESTONE_CATEGORIES` fails to
+ * compile here rather than silently taking slot 6 — and so the display order
+ * is `MILESTONE_CATEGORIES`' to decide, not a side effect of this literal's
+ * key order, which is what the panel select used to read.
  */
 export const MILESTONE_CATEGORY_COLOR = {
     foundation: 'var(--series-1)',

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.1",
+	"version": "0.22.0",
 	"scripts": {
 		"dev": "vite dev",
 		"build": "vite build && npm run prepack",

package/dist/components/jobs/index.d.ts

@@ -1,2 +0,0 @@
-export { default as JobList } from './JobList.svelte';
-export type { JobEditMap } from './JobList.svelte';

package/dist/components/jobs/index.js

@@ -1 +0,0 @@
-export { default as JobList } from './JobList.svelte';

package/dist/components/layout/index.d.ts

@@ -1,3 +0,0 @@
-export { default as Footer } from './Footer.svelte';
-export { default as Nav } from './Nav.svelte';
-export { default as PageShell } from './PageShell.svelte';

package/dist/components/layout/index.js

@@ -1,3 +0,0 @@
-export { default as Footer } from './Footer.svelte';
-export { default as Nav } from './Nav.svelte';
-export { default as PageShell } from './PageShell.svelte';

package/dist/components/projects/index.d.ts

@@ -1,2 +0,0 @@
-export { default as ProjectCard } from './ProjectCard.svelte';
-export type { ProjectEditMap } from './ProjectCard.svelte';

package/dist/components/projects/index.js

@@ -1 +0,0 @@
-export { default as ProjectCard } from './ProjectCard.svelte';

package/dist/components/team/index.d.ts

@@ -1,3 +0,0 @@
-export { default as CollaboratorList } from './CollaboratorList.svelte';
-export { default as TeamMemberCard } from './TeamMemberCard.svelte';
-export type { TeamMemberEditMap } from './TeamMemberCard.svelte';

package/dist/components/team/index.js

@@ -1,2 +0,0 @@
-export { default as CollaboratorList } from './CollaboratorList.svelte';
-export { default as TeamMemberCard } from './TeamMemberCard.svelte';

package/dist/components/timeline/index.d.ts

@@ -1,3 +0,0 @@
-export { default as Timeline } from './Timeline.svelte';
-export { default as TimelineMilestone } from './TimelineMilestone.svelte';
-export type { MilestoneEditMap } from './TimelineMilestone.svelte';

package/dist/components/timeline/index.js

@@ -1,2 +0,0 @@
-export { default as Timeline } from './Timeline.svelte';
-export { default as TimelineMilestone } from './TimelineMilestone.svelte';

package/dist/components/ui/index.d.ts

@@ -1,20 +0,0 @@
-export { default as Button } from './Button.svelte';
-export { default as CardMedia } from './CardMedia.svelte';
-export { default as CardTitle } from './CardTitle.svelte';
-export { default as CopyIntro } from './CopyIntro.svelte';
-export { default as DateText } from './DateText.svelte';
-export { default as DecorShapes } from './DecorShapes.svelte';
-export { default as Field } from './Field.svelte';
-export { default as FilterChips } from './FilterChips.svelte';
-export { default as FormErrorFeedback } from './FormErrorFeedback.svelte';
-export { default as FormFeedback } from './FormFeedback.svelte';
-export { default as FormResultSlot } from './FormResultSlot.svelte';
-export { default as GhostButton } from './GhostButton.svelte';
-export { default as Honeypot } from './Honeypot.svelte';
-export { default as Link } from './Link.svelte';
-export { default as LocaleField } from './LocaleField.svelte';
-export { default as NewsletterIntentField } from './NewsletterIntentField.svelte';
-export { default as Pagination } from './Pagination.svelte';
-export { default as RichText } from './RichText.svelte';
-export { default as SearchInput } from './SearchInput.svelte';
-export { default as ShareRow } from './ShareRow.svelte';

package/dist/components/ui/index.js

@@ -1,20 +0,0 @@
-export { default as Button } from './Button.svelte';
-export { default as CardMedia } from './CardMedia.svelte';
-export { default as CardTitle } from './CardTitle.svelte';
-export { default as CopyIntro } from './CopyIntro.svelte';
-export { default as DateText } from './DateText.svelte';
-export { default as DecorShapes } from './DecorShapes.svelte';
-export { default as Field } from './Field.svelte';
-export { default as FilterChips } from './FilterChips.svelte';
-export { default as FormErrorFeedback } from './FormErrorFeedback.svelte';
-export { default as FormFeedback } from './FormFeedback.svelte';
-export { default as FormResultSlot } from './FormResultSlot.svelte';
-export { default as GhostButton } from './GhostButton.svelte';
-export { default as Honeypot } from './Honeypot.svelte';
-export { default as Link } from './Link.svelte';
-export { default as LocaleField } from './LocaleField.svelte';
-export { default as NewsletterIntentField } from './NewsletterIntentField.svelte';
-export { default as Pagination } from './Pagination.svelte';
-export { default as RichText } from './RichText.svelte';
-export { default as SearchInput } from './SearchInput.svelte';
-export { default as ShareRow } from './ShareRow.svelte';

package/dist/components/weeklies/index.d.ts

@@ -1,7 +0,0 @@
-export { default as CommentSection } from './CommentSection.svelte';
-export type { CommentFormInstance } from './CommentSection.svelte';
-export { default as ReactionBar } from './ReactionBar.svelte';
-export type { CommentReactionChip, ReactionBarForms, WeeklyReactionChip } from './ReactionBar.svelte';
-export { default as SortSelect } from './SortSelect.svelte';
-export { default as WeeklieCard } from './WeeklieCard.svelte';
-export type { WeeklyEditMap } from './WeeklieCard.svelte';

package/dist/components/weeklies/index.js

@@ -1,4 +0,0 @@
-export { default as CommentSection } from './CommentSection.svelte';
-export { default as ReactionBar } from './ReactionBar.svelte';
-export { default as SortSelect } from './SortSelect.svelte';
-export { default as WeeklieCard } from './WeeklieCard.svelte';