fix(hub): resolve baked statics with their mount resolveFrom

buildHub copies statics from ctx.views.buildStaticDirs, which for a plugin's
RemoteAssets client bundle (e.g. @devframes/plugin-a11y--assets) must re-resolve
with the plugin's importMetaUrl as resolveFrom to hit the locally-installed
copy; without it resolution fell back to a stale CDN back-proxy cache, baking an
outdated SPA (surfaced by the a11y summary sticky e2e). Record resolveFrom on
each buildStaticDirs entry and pass it through when baking.

Author: antfubot

packages/devframe/src/node/host-views.ts

@@ -7,7 +7,7 @@ export class DevframeViewHost implements DevframeViewHostType {
   /**
    * @internal
    */
-  public buildStaticDirs: { baseUrl: string, source: StaticAssetsSource }[] = []
+  public buildStaticDirs: { baseUrl: string, source: StaticAssetsSource, resolveFrom?: string | null }[] = []
 
   constructor(
     public readonly context: DevframeNodeContext,
@@ -30,7 +30,7 @@ export class DevframeViewHost implements DevframeViewHostType {
       throw diagnostics.DF0008({ distDir: resolved })
     }
 
-    this.buildStaticDirs.push({ baseUrl, source })
+    this.buildStaticDirs.push({ baseUrl, source, resolveFrom: defaultResolveFrom })
     this.context.host.mountStatic(baseUrl, resolved)
   }
 }

packages/devframe/src/types/views.ts

@@ -2,9 +2,14 @@ import type { StaticAssetsSource } from './remote-assets'
 
 export interface DevframeViewHost {
   /**
+   * Static mounts registered through {@link DevframeViewHost.hostStatic}, each
+   * carrying the `resolveFrom` base it was mounted with so a build step that
+   * copies these itself (rather than serving them live) re-resolves a remote
+   * source to the same locally-installed copy it would serve live.
+   *
    * @internal
    */
-  buildStaticDirs: { baseUrl: string, source: StaticAssetsSource }[]
+  buildStaticDirs: { baseUrl: string, source: StaticAssetsSource, resolveFrom?: string | null }[]
   /**
    * Helper to host static files
    * - In `dev` mode, it will register middleware to `viteServer.middlewares` to host the static files

packages/hub/src/node/build.ts

@@ -185,12 +185,15 @@ async function createAndMountContext(options: BuildHubOptions, base: string, cwd
  * source by materializing every listed file. Reads the list rather than
  * relying on a live host `mountStatic`, so a context whose host copied no
  * statics at mount time (the build host, or a kit's) still gets its assets in.
+ * Each source re-resolves with the `resolveFrom` it was mounted with, so a
+ * remote source (e.g. a plugin's `--assets` package) resolves to the same
+ * locally-installed copy it would serve live.
  */
 async function copyBuildStatics(ctx: DevframeHubContext, resolveOutPath: (urlBase: string) => string): Promise<void> {
   const storageDir = ctx.host.getStorageDir('project')
-  for (const { baseUrl, source } of ctx.views.buildStaticDirs) {
+  for (const { baseUrl, source, resolveFrom } of ctx.views.buildStaticDirs) {
     const target = resolveOutPath(baseUrl)
-    const resolved = resolveStaticAssetsSource(source, storageDir)
+    const resolved = resolveStaticAssetsSource(source, storageDir, resolveFrom)
     await fs.mkdir(dirname(target), { recursive: true })
     if (typeof resolved === 'string')
       await fs.cp(resolved, target, { recursive: true })

tests/__snapshots__/tsnapi/devframe/index.snapshot.d.ts

@@ -367,6 +367,7 @@ export interface DevframeViewHost {
   buildStaticDirs: {
     baseUrl: string;
     source: StaticAssetsSource;
+    resolveFrom?: string | null;
   }[];
   hostStatic: (_: string, _: StaticAssetsSource, _?: string | null) => void;
 }