@artstorefronts/arthelper-nav 0.1.0-alpha.0 → 0.1.0-alpha.1

package/README.md

@@ -31,21 +31,13 @@ Peer dependencies (from `package.json` — install these yourself, they are not
 }
 ```
 
-> **Not yet on npm.** Publishing is automatic: `.github/workflows/release-nav.yml` runs on
-> any push to `develop` that touches `packages/nav`, and publishes when the version in
-> `packages/nav/package.json` is not already on the registry. There is no tag and no
-> manual release step — **bumping that version in your PR is what ships the package**, and
-> a PR that changes the published surface without bumping it fails CI.
+> **Getting a change released.** There is no tag and no manual release step: bump the
+> version in `packages/nav/package.json` in the PR that changes the package, and merging
+> to `develop` publishes it. CI publishes only when that version is absent from the
+> registry, and a PR that changes the published surface while leaving the version alone
+> fails its own check — so a change cannot quietly land without reaching you.
 >
-> The `@artstorefronts` scope already exists (it publishes `@artstorefronts/ui` and
-> `@artstorefronts/cli`). What is still missing is a **trusted publisher** configured on
-> npm for this package, pointing at this repository and the workflow filename
-> `release-nav.yml`. Authentication is OIDC, so there is no token to create or rotate.
-> Until that is configured, `npm install @artstorefronts/arthelper-nav` has nothing to
-> resolve.
->
-> To develop against it before the first publish, use a workspace link or a path
-> dependency from the satellite repo:
+> **Testing an unreleased change.** Link the workspace, or use a path dependency:
 >
 > ```bash
 > cd packages/nav && yarn link
@@ -54,7 +46,8 @@ Peer dependencies (from `package.json` — install these yourself, they are not
 >
 > `react` and `react-dom` are peer dependencies, so make sure the satellite's bundler
 > resolves a single copy of React — a linked package pulling in its own is the usual
-> cause of the duplicate-React hooks error.
+> cause of the duplicate-React hooks error. `npm pack` plus installing the tarball avoids
+> that failure mode entirely and resolves more like the real thing.
 
 ## Minimal mounting example
 

package/dist/fallback.d.ts

@@ -1,12 +1,26 @@
 import type { NavConfigPayload } from './types.js';
 /**
- * The static config compiled into the package. Used whenever the fetch fails,
- * times out, or has not resolved yet, so the bar reserves its final 56px from
- * first paint and never renders blank.
+ * The static config compiled into the package. Used whenever the fetch fails, times out,
+ * or has not resolved yet, so the bar reserves its final 56px from first paint and never
+ * renders blank.
  *
- * It carries ONLY entries that have a destination. Changing it requires a
- * package release, which is exactly why it holds the stable first-party
- * destination and never the satellites — those arrive over the wire.
+ * It carries the WHOLE catalog, not just the enabled entries, and that is load-bearing
+ * rather than tidiness. A host's own `activeAppId` entry is always rendered and indicated,
+ * resolved from this list when the payload omits it — so a satellite whose id is missing
+ * here loses its chip entirely during an endpoint outage, and with it any indication of
+ * where the user is and anything for NavTrigger to dock. Every app that can mount the bar
+ * needs an entry, whether or not it is currently switched on.
+ *
+ * `enabled` here still governs what renders: the same enabled-and-has-destination filter
+ * runs against this list as against the fetched payload, so a disabled entry contributes
+ * its label, icon, order and destination without appearing as a tile.
+ *
+ * These are the production domains, which is why they can live in compiled code at all.
+ * Changing this list requires a package release, so it is deliberately the stable
+ * first-party set — anything situational (a stage host, a locally-run satellite) belongs
+ * in the config row, where an admin can edit it without a release. `enabled` states drift
+ * from the row over time; that is expected and harmless, since the row wins whenever the
+ * endpoint is reachable.
  */
 declare const FALLBACK_CONFIG: NavConfigPayload;
 export { FALLBACK_CONFIG };

package/dist/fallback.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"fallback.d.ts","sourceRoot":"","sources":["../src/fallback.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,YAAY,CAAC;AAEnD;;;;;;;;GAQG;AACH,QAAA,MAAM,eAAe,EAAE,gBAKtB,CAAC;AAEF,OAAO,EAAE,eAAe,EAAE,CAAC"}
+{"version":3,"file":"fallback.d.ts","sourceRoot":"","sources":["../src/fallback.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,YAAY,CAAC;AAEnD;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,QAAA,MAAM,eAAe,EAAE,gBAyBtB,CAAC;AAEF,OAAO,EAAE,eAAe,EAAE,CAAC"}

package/dist/fallback.js

@@ -1,17 +1,51 @@
 /**
- * The static config compiled into the package. Used whenever the fetch fails,
- * times out, or has not resolved yet, so the bar reserves its final 56px from
- * first paint and never renders blank.
+ * The static config compiled into the package. Used whenever the fetch fails, times out,
+ * or has not resolved yet, so the bar reserves its final 56px from first paint and never
+ * renders blank.
  *
- * It carries ONLY entries that have a destination. Changing it requires a
- * package release, which is exactly why it holds the stable first-party
- * destination and never the satellites — those arrive over the wire.
+ * It carries the WHOLE catalog, not just the enabled entries, and that is load-bearing
+ * rather than tidiness. A host's own `activeAppId` entry is always rendered and indicated,
+ * resolved from this list when the payload omits it — so a satellite whose id is missing
+ * here loses its chip entirely during an endpoint outage, and with it any indication of
+ * where the user is and anything for NavTrigger to dock. Every app that can mount the bar
+ * needs an entry, whether or not it is currently switched on.
+ *
+ * `enabled` here still governs what renders: the same enabled-and-has-destination filter
+ * runs against this list as against the fetched payload, so a disabled entry contributes
+ * its label, icon, order and destination without appearing as a tile.
+ *
+ * These are the production domains, which is why they can live in compiled code at all.
+ * Changing this list requires a package release, so it is deliberately the stable
+ * first-party set — anything situational (a stage host, a locally-run satellite) belongs
+ * in the config row, where an admin can edit it without a release. `enabled` states drift
+ * from the row over time; that is expected and harmless, since the row wins whenever the
+ * endpoint is reachable.
  */
 const FALLBACK_CONFIG = {
     schema_version: 1,
     theme: { mode: 'dark', accent_color: '#2aa34f', alignment: 'left' },
     logo: { label: 'ArtHelper', href: 'https://www.arthelper.com' },
-    apps: [{ id: 'home', label: 'Home', icon: 'house', href: 'https://www.arthelper.com', enabled: true }],
+    apps: [
+        { id: 'home', label: 'Home', icon: 'house', href: 'https://www.arthelper.com/community', enabled: true },
+        { id: 'the-daily', label: 'The Daily', icon: 'sunrise', href: 'https://thedaily.arthelper.com', enabled: false },
+        { id: 'art-review', label: 'Art Review', icon: 'star', href: 'https://artreview.arthelper.com', enabled: true },
+        {
+            id: 'creative-sparks',
+            label: 'Creative Sparks',
+            icon: 'sparkles',
+            href: 'https://sparks.arthelper.com',
+            enabled: false,
+        },
+        { id: 'mockups', label: 'Mockups', icon: 'frame', href: 'https://mockups.arthelper.com', enabled: false },
+        { id: 'art-books', label: 'Art Books', icon: 'book-open', href: 'https://artbooks.arthelper.com', enabled: false },
+        {
+            id: 'social-posting',
+            label: 'Social Posting',
+            icon: 'megaphone',
+            href: 'https://copilot.arthelper.com',
+            enabled: false,
+        },
+    ],
 };
 export { FALLBACK_CONFIG };
 //# sourceMappingURL=fallback.js.map

package/dist/fallback.js.map

@@ -1 +1 @@
-{"version":3,"file":"fallback.js","sourceRoot":"","sources":["../src/fallback.ts"],"names":[],"mappings":"AAEA;;;;;;;;GAQG;AACH,MAAM,eAAe,GAAqB;IACxC,cAAc,EAAE,CAAC;IACjB,KAAK,EAAE,EAAE,IAAI,EAAE,MAAM,EAAE,YAAY,EAAE,SAAS,EAAE,SAAS,EAAE,MAAM,EAAE;IACnE,IAAI,EAAE,EAAE,KAAK,EAAE,WAAW,EAAE,IAAI,EAAE,2BAA2B,EAAE;IAC/D,IAAI,EAAE,CAAC,EAAE,EAAE,EAAE,MAAM,EAAE,KAAK,EAAE,MAAM,EAAE,IAAI,EAAE,OAAO,EAAE,IAAI,EAAE,2BAA2B,EAAE,OAAO,EAAE,IAAI,EAAE,CAAC;CACvG,CAAC;AAEF,OAAO,EAAE,eAAe,EAAE,CAAC"}
+{"version":3,"file":"fallback.js","sourceRoot":"","sources":["../src/fallback.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,MAAM,eAAe,GAAqB;IACxC,cAAc,EAAE,CAAC;IACjB,KAAK,EAAE,EAAE,IAAI,EAAE,MAAM,EAAE,YAAY,EAAE,SAAS,EAAE,SAAS,EAAE,MAAM,EAAE;IACnE,IAAI,EAAE,EAAE,KAAK,EAAE,WAAW,EAAE,IAAI,EAAE,2BAA2B,EAAE;IAC/D,IAAI,EAAE;QACJ,EAAE,EAAE,EAAE,MAAM,EAAE,KAAK,EAAE,MAAM,EAAE,IAAI,EAAE,OAAO,EAAE,IAAI,EAAE,qCAAqC,EAAE,OAAO,EAAE,IAAI,EAAE;QACxG,EAAE,EAAE,EAAE,WAAW,EAAE,KAAK,EAAE,WAAW,EAAE,IAAI,EAAE,SAAS,EAAE,IAAI,EAAE,gCAAgC,EAAE,OAAO,EAAE,KAAK,EAAE;QAChH,EAAE,EAAE,EAAE,YAAY,EAAE,KAAK,EAAE,YAAY,EAAE,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,iCAAiC,EAAE,OAAO,EAAE,IAAI,EAAE;QAC/G;YACE,EAAE,EAAE,iBAAiB;YACrB,KAAK,EAAE,iBAAiB;YACxB,IAAI,EAAE,UAAU;YAChB,IAAI,EAAE,8BAA8B;YACpC,OAAO,EAAE,KAAK;SACf;QACD,EAAE,EAAE,EAAE,SAAS,EAAE,KAAK,EAAE,SAAS,EAAE,IAAI,EAAE,OAAO,EAAE,IAAI,EAAE,+BAA+B,EAAE,OAAO,EAAE,KAAK,EAAE;QACzG,EAAE,EAAE,EAAE,WAAW,EAAE,KAAK,EAAE,WAAW,EAAE,IAAI,EAAE,WAAW,EAAE,IAAI,EAAE,gCAAgC,EAAE,OAAO,EAAE,KAAK,EAAE;QAClH;YACE,EAAE,EAAE,gBAAgB;YACpB,KAAK,EAAE,gBAAgB;YACvB,IAAI,EAAE,WAAW;YACjB,IAAI,EAAE,+BAA+B;YACrC,OAAO,EAAE,KAAK;SACf;KACF;CACF,CAAC;AAEF,OAAO,EAAE,eAAe,EAAE,CAAC"}

package/dist/index.css

@@ -200,8 +200,20 @@
   gap: 4px;
   align-items: center;
   justify-content: var(--ahsuite-tiles-justify);
+  /* Grow into the row's leftover space. Without this the row is sized to its own
+   * content, so `justify-content` has nothing to distribute and `alignment: centered`
+   * renders identically to `left` — the variable was set correctly all along, the
+   * layout simply could not express it. `min-width: 0` lets the row shrink below its
+   * content so `overflow: hidden` clips rather than overflowing a narrow bar. */
+  flex: 1 1 auto;
+  min-width: 0;
   overflow: hidden;
-  max-width: 1200px;
+  /* 100%, not a fixed cap. This is the property the collapse animates (to 0), so it has
+   * to stay — but a 1200px cap stopped the row growing on a wide viewport, which left
+   * `alignment: centered` visibly left-of-centre (546px out at 2560px wide). The cap was
+   * invisible while the row was content-sized and never affected the left-aligned case,
+   * since tiles sit left whatever the row's width. */
+  max-width: 100%;
   opacity: 1;
   transform: translateY(0);
   transition:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@artstorefronts/arthelper-nav",
-  "version": "0.1.0-alpha.0",
+  "version": "0.1.0-alpha.1",
   "description": "The ArtHelper suite navigation bar — a config-driven, cross-origin app switcher.",
   "license": "ISC",
   "type": "module",