@dimina-kit/devtools 0.4.0-dev.20260824071518 → 0.4.0-dev.20260828161241

package/dist/main/api.d.ts

@@ -2,7 +2,7 @@ export { launch, buildDefaultMenu, openSettingsWindow } from './app/launch.js';
 export type { WorkbenchAppInstance } from './app/app.js';
 export { suppressEpipe, setupCdpPort } from './app/bootstrap.js';
 export { asMiniappRuntime } from './runtime/miniapp-runtime.js';
-export type { MiniappRuntime, MiniappSessionAppInfo, DiminaHostToolbarPageBridge, } from './runtime/miniapp-runtime.js';
+export type { MiniappRuntime, MiniappSessionAppInfo, DiminaHostToolbarPageBridge, DiminaHostSidebarPageBridge, DiminaHostDialogPageBridge, } from './runtime/miniapp-runtime.js';
 export { createWorkbenchContext } from './services/workbench-context.js';
 export type { WorkbenchContext, CreateContextOptions } from './services/workbench-context.js';
 export { createMainWindow } from './windows/main-window/index.js';

package/dist/main/app/app.js

@@ -4,6 +4,7 @@ import { registerProjectFsIpc } from '../ipc/project-fs.js';
 import { app, BrowserWindow, nativeImage, session } from 'electron';
 import fs from 'fs';
 import path from 'path';
+import { HOST_SIDEBAR_DEFAULT_WIDTH } from '../../shared/constants.js';
 import { rendererDir as defaultRendererDir, defaultPreloadPath, devtoolsPackageRoot } from '../utils/paths.js';
 import { installThemeBackgroundSync } from '../utils/theme.js';
 import { createMainWindow, wireMainWindowEvents } from '../windows/main-window/index.js';
@@ -17,7 +18,7 @@ import { createWorkbenchContext } from '../services/workbench-context.js';
 import { setupCompileWorkerStandby } from '../services/compile-standby.js';
 import { loadWorkbenchSettings, applyTheme } from '../services/settings/index.js';
 import { installAppMenu } from '../menu/index.js';
-import { registerAppIpc, registerInternalDevtoolsIpc, registerTooltipIpc, popoverModule, projectsModule, sessionModule, settingsModule, simulatorModule, } from '../ipc/index.js';
+import { registerAppIpc, registerInternalDevtoolsIpc, registerTooltipIpc, registerProjectCreateIpc, registerViewsIpc, popoverModule, projectsModule, sessionModule, settingsModule, simulatorModule, } from '../ipc/index.js';
 import { startAutomationServer } from '../services/automation/index.js';
 import { startMcpServer, setNativeHost, setActiveBridgeId, setNativeOverviewProvider, } from '../services/mcp/index.js';
 import { setupSimulatorStorage } from '../services/simulator-storage/index.js';
@@ -168,6 +169,10 @@ function createContext(config, mainWindow, rendererDir) {
         projectTemplates: config.projectTemplates,
         builtinTemplates: config.builtinTemplates,
         customCreateProjectDialog: config.customCreateProjectDialog,
+        // No cast needed here: the hook receives the project record, so the
+        // main-process `Project` the context hands it satisfies the structural
+        // `EditableProject` the config declares.
+        customEditProjectDialog: config.customEditProjectDialog,
         onBeforeOpenProject: config.onBeforeOpenProject,
     });
 }
@@ -411,6 +416,19 @@ onInstanceCreated) {
     // overlay is core UI chrome (every toolbar in this app relies on it), not a
     // host-configurable feature.
     context.registry.add(registerTooltipIpc(context));
+    // Unconditional: the project-create dialog is core UI chrome (the built-in
+    // "新建项目" flow every host falls back to), not a host-configurable feature.
+    context.registry.add(registerProjectCreateIpc(context));
+    // Unconditional (not a toggleable BUILTIN_MODULES entry): placement/host-
+    // slot IPC has no real dependency on the simulator module — `ctx.views`
+    // (ViewManager) is constructed unconditionally regardless of
+    // `modules.simulator`, and host-sidebar in particular lives on the
+    // project-list page, unrelated to the simulator webview. Every renderer
+    // entry point also blocks its first render on `AllocatePlacementGeneration`
+    // (see renderer-placement-generation.ts) — gating any of this behind the
+    // simulator toggle would strand a host that disables it on the fatal
+    // boot-failure page, or leave placement silently non-functional.
+    context.registry.add(registerViewsIpc(context));
     // Referer/CORS webRequest policy for the simulator runtime's sessions (shared
     // fallback + every per-project partition). Registered into the context
     // registry so its configurator + per-session listeners are torn down with the
@@ -497,13 +515,52 @@ onInstanceCreated) {
     instance.registerSimulatorApi('login', async () => {
         return 'hello';
     });
+    // devtools' own default content for the host-sidebar slot: a narrow icon
+    // rail (logo + 小程序/小游戏 toggle) filtering the project-list grid by
+    // `Project.type`. Loaded BEFORE `config.onSetup` runs below, so any
+    // downstream `loadURL`/`loadFile` call inside onSetup necessarily happens
+    // later and naturally supersedes this default via plain chronological
+    // ordering — no override flag needed.
+    context.registry.add(context.views.hostSidebar.onMessage('project-category-selected', (payload) => {
+        const category = payload?.category;
+        if (category !== 'miniprogram' && category !== 'minigame')
+            return;
+        context.notify.hostSidebarCategorySelected(category);
+    }));
+    context.views.hostSidebar
+        .loadFile(path.join(rendererDir, 'entries/host-sidebar-default/index.html'))
+        .catch((err) => {
+        console.warn('[workbench] failed to load host-sidebar default content:', err);
+    });
+    // Seed the notified width with the rail's own known intrinsic width
+    // (`HOST_SIDEBAR_DEFAULT_WIDTH`) instead of leaving it at 0 until the
+    // rail's in-page advertiser reports back. That report can never arrive on
+    // its own: the placeholder above only becomes "desired visible" once a
+    // nonzero width is known (project-list-screen.tsx), attach only happens
+    // for a "desired visible" view (placement-reconciler.ts), and the rail's
+    // advertiser (view-anchor's measure-loop.ts) only ever fires via
+    // `requestAnimationFrame`, which Chromium never schedules for a
+    // WebContentsView that was never attached — a structural deadlock, not a
+    // slow-to-resolve race. `setWidthMode({fixed})` pushes the seed
+    // synchronously (no attach/rAF dependency) and, critically, retains it in
+    // `getHostSidebarWidth()` too, so a renderer that mounts and pulls before
+    // any push replays the real seed instead of a stale 0. Flipping back to
+    // 'auto' immediately after, before anything has attached or advertised, is
+    // a same-tick no-op past the seed (`setExtentMode`'s reapply branch only
+    // fires once something has actually been advertised) — it leaves the slot
+    // in 'auto' for whichever content ends up loaded (this rail's own later
+    // report, or a downstream replacement's), not pinned.
+    context.views.hostSidebar.setWidthMode({ fixed: HOST_SIDEBAR_DEFAULT_WIDTH });
+    context.views.hostSidebar.setWidthMode('auto');
     if (config.onSetup) {
         await config.onSetup(instance);
     }
     if (config.updateChecker) {
         instance.updateManager = new UpdateManager({
             checker: config.updateChecker,
-            mainWindow,
+            showUpdatePanel: (info) => context.views.showUpdateDialog(info),
+            notifyDownloadProgress: (percent) => context.views.notifyUpdateDownloadProgress(percent),
+            hideUpdatePanel: () => context.views.hideUpdateDialog(),
             senderPolicy: context.senderPolicy,
             checkInterval: config.updateOptions?.checkInterval,
             initialDelay: config.updateOptions?.initialDelay,