@startsimpli/integrations 0.2.29 → 0.2.30

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@startsimpli/integrations",
-  "version": "0.2.29",
+  "version": "0.2.30",
   "description": "Provider-agnostic types, API clients, hooks, and UI primitives for email + calendar integrations across StartSimpli apps.",
   "main": "./src/index.ts",
   "types": "./src/index.ts",

package/src/__tests__/barrel-exports.test.ts

@@ -0,0 +1,78 @@
+/**
+ * EVERY PAGE COMPOSER IS REACHABLE FROM THE PACKAGE ROOT.
+ *
+ * WHY THIS EXISTS. `PlanningPage` shipped in the tarball — the FILE was there,
+ * at `src/components/pages/PlanningPage.tsx` — while the one line exporting it
+ * from `src/components/index.ts` had been dropped by an unrelated PR's merge
+ * resolution. Nothing caught it: type-check passes (the file compiles), the unit
+ * tests pass (they import the module directly), and `npm pack` includes it. The
+ * failure surfaced two publishes later, in a CUSTOMER'S docker build:
+ *
+ *     The export PlanningPage was not found in module
+ *     .../@startsimpli/integrations/src/index.ts
+ *     Did you mean to import ConnectionsPage?
+ *
+ * That is the worst possible place to find it — a tenant's deploy, against a
+ * published artifact, with the composer's own tests green the whole time.
+ *
+ * So the barrel is asserted against the DIRECTORY rather than against a list
+ * somebody has to remember to update. A new composer is exported or this fails;
+ * a merge that drops an export line fails here instead of in a deploy.
+ */
+import { readdirSync } from 'node:fs';
+import { join } from 'node:path';
+import { describe, expect, it } from 'vitest';
+
+import * as pkg from '../index';
+
+const PAGES_DIR = join(__dirname, '..', 'components', 'pages');
+
+/** Files that are not composers and are deliberately not re-exported by name. */
+const NOT_A_COMPOSER = new Set([
+  // Shared prop/api types — re-exported explicitly and selectively by the barrel
+  // so a fork gets the ones it needs without the internal slot unions.
+  'types.ts',
+  // The shared pieces two composers mount; exported by NAME, asserted below.
+  'work-items.tsx',
+  // A SUB-COMPONENT, not a composer: ConnectionsPage is its only mount, and the
+  // roster is the one list on that screen that shows OTHER people's accounts —
+  // it is meaningless outside the page that gates it. Listed here rather than
+  // exported, so this stays a real assertion about what a fork can reach and not
+  // a rubber stamp.
+  'MemberConnectionRoster.tsx',
+]);
+
+function composerNames(): string[] {
+  return readdirSync(PAGES_DIR)
+    .filter((f) => f.endsWith('.tsx') && !NOT_A_COMPOSER.has(f))
+    .map((f) => f.replace(/\.tsx$/, ''));
+}
+
+describe('package barrel', () => {
+  it('re-exports every page composer in components/pages', () => {
+    const missing = composerNames().filter((name) => !(name in pkg));
+    expect(missing, `not exported from @startsimpli/integrations: ${missing.join(', ')}`)
+      .toEqual([]);
+  });
+
+  it('exports the pieces the tracker and the planner share', () => {
+    // These are what stop the two screens drifting. If the barrel loses them, a
+    // fork silently reimplements the row and the divergence starts.
+    for (const name of ['WorkItemRow', 'UnfilteredNotice', 'isOverdue', 'compareForScreen']) {
+      expect(pkg, `missing shared export ${name}`).toHaveProperty(name);
+    }
+  });
+
+  it('exports the planning client alongside its screen', () => {
+    // A screen with no client is a mount nobody can wire; they ship together or
+    // the fork gets a confusing half-error at build time.
+    expect(pkg).toHaveProperty('PlanningPage');
+    expect(pkg).toHaveProperty('createPlanningApi');
+  });
+
+  it('still exports the composers that were already shipping', () => {
+    for (const name of ['ConnectionsPage', 'LibraryPage', 'AskPage', 'TrackerPage']) {
+      expect(pkg, `regressed export ${name}`).toHaveProperty(name);
+    }
+  });
+});

package/src/components/index.ts

@@ -36,3 +36,20 @@ export type {
 export * from './pages/LibraryPage';
 export * from './pages/AskPage';
 export * from './pages/TrackerPage';
+
+// The planning toolset (bd startsim-8l6ef): focuses, and the items filed under
+// them. `work-items` carries the pieces the tracker and the planner SHARE — the
+// row, the honesty banner, the overdue/changed predicates — so two views over
+// one list cannot drift into disagreeing about what they mean.
+export * from './pages/PlanningPage';
+export {
+  PRIORITY_LABELS,
+  UnfilteredNotice,
+  WORK_ITEM_DEFAULTS,
+  WorkItemRow,
+  changedSince,
+  compareForScreen,
+  isOverdue,
+  priorityLabel,
+} from './pages/work-items';
+export type { WorkItemSlot } from './pages/work-items';