Replies: 27 comments 57 replies
-
|
话说桌面端能带来什么独占功能/优势吗 |
Beta Was this translation helpful? Give feedback.
-
|
目前看会有的是 MCP，然后会有和 OS 级别交互的能力 |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
-
研发问题 & 关键思路记录1. service 层复用 server.ts 还是新建 electron.ts由于 nextjs 的 standalone 模式会完整输出可以直接运行的 next 应用，next-electron-rsc 模块会直接通过 next的入口文件启动 next 实例，因此在启动 electron 的时候等于同时启动了一个 nextjs 的进程。 这里的问题就是当前端将请求发到 service 层时，应该走独立的 electron main端执行，还是走 nextjs 的服务端调用。 和 Claude 聊完以后，感觉比较理想的方式应该是这样： 这样一来大部分 service 和 router 层的东西都可以复用，只需要替换 db 即可。 2. 如何开启 AsarAsar 和 pnpm 的软链模式有冲突，替换成 |
Beta Was this translation helpful? Give feedback.
-
|
打算什么时候发布桌面版？ |
Beta Was this translation helpful? Give feedback.
-
|
桌面版已经发布啦 |
Beta Was this translation helpful? Give feedback.
-
|
在问题 1 的基础上衍生下来的几个问题，和 claude 聊出了一个更加完善的架构设计方案 Electron + Next.js 完整应用架构设计综合架构图以下是一个完整的 Electron + Next.js 应用架构图，包含所有关键组件及其交互关系： 详细组件关系图下面是更详细的组件关系和交互流程图： 组件功能详解1. Electron 主进程组件1.1 应用入口点 (main.ts)
1.2 窗口管理 (BrowserWindow)
1.3 IPC 服务器 (ipc-server.ts)
1.4 协议处理器 (next-electron-rsc)
2. Next.js 服务端组件2.1 IPC 客户端 (electron-ipc-client.ts)
2.2 Next.js 服务器 (next-server)
2.3 数据库初始化 (db-factory.ts)
2.4 React 服务端组件 (RSC)
3. Electron 渲染进程组件3.1 预加载脚本 (preload.ts)
3.2 WebView (BrowserView)
3.3 Next.js 客户端 (React DOM)
3.4 tRPC 客户端
通信流程详解1. 启动流程2. 数据库初始化流程3. 页面渲染流程4. API 调用流程技术选型和集成点1. next-electron-rsc 集成
2. IPC 通信层
3. 数据库层
4. WebView 渲染
核心实现挑战和解决方案1. 避免构建引用问题挑战：Next.js 构建时可能会尝试包含 Electron 依赖，导致构建错误。 解决方案：
2. 进程通信可靠性挑战：确保 Next.js 服务端和 Electron 主进程之间的通信可靠。 解决方案：
3. 数据库初始化顺序挑战：确保数据库在 Next.js 服务端启动后正确初始化。 解决方案：
总结这个完整的 Electron + Next.js 架构设计提供了：
通过这种架构，你可以充分利用 Next.js 的先进特性和 Electron 的桌面能力，构建功能强大且用户体验一流的桌面应用。 |
Beta Was this translation helpful? Give feedback.
-
Electron 与 Next.js 集成的结构化架构设计1. 整体架构首先，让我们明确定义 Electron 主进程和 Next.js 服务端进程之间的关系和通信架构： 2. 通信架构我们将采用本地 IPC 通信机制，让 Next.js 服务端能够与 Electron 主进程通信： 3. IPC 通信方案考虑到跨平台和可靠性，我们将使用命名管道 (Windows) 和 Unix 套接字 (macOS/Linux) 作为 IPC 机制，它们比 TCP 连接更安全（仅限本地进程）且更高效。 通信协议设计我们将设计一个简单的请求-响应协议： 示例： // 请求
{ "id": "123", "method": "GET_DATABASE_PATH", "params": {} }
// 成功响应
{ "id": "123", "result": "/Users/username/Library/Application Support/LobeChatApp/lobechat.db" }
// 错误响应
{ "id": "123", "error": "Failed to get database path" }4. 具体实现方案Electron 主进程实现// src-electron/ipc-server.ts
import { app } from 'electron';
import path from 'path';
import fs from 'fs';
import net from 'net';
import os from 'os';
export class ElectronIPCServer {
private server: net.Server;
private socketPath: string;
constructor() {
const isWindows = process.platform === 'win32';
// 创建唯一的套接字路径，避免冲突
this.socketPath = isWindows
? '\\\\.\\pipe\\lobechat-electron-ipc'
: path.join(os.tmpdir(), 'lobechat-electron-ipc.sock');
// 如果是 Unix 套接字，确保文件不存在
if (!isWindows && fs.existsSync(this.socketPath)) {
fs.unlinkSync(this.socketPath);
}
// 创建服务器
this.server = net.createServer(this.handleConnection.bind(this));
}
// 启动服务器
public start(): Promise<void> {
return new Promise((resolve, reject) => {
this.server.on('error', (err) => {
console.error('IPC Server error:', err);
reject(err);
});
this.server.listen(this.socketPath, () => {
console.log(`Electron IPC server listening on ${this.socketPath}`);
// 将套接字路径写入临时文件，供 Next.js 服务端读取
const tempDir = app.getPath('temp');
const socketInfoPath = path.join(tempDir, 'lobechat-electron-ipc-info.json');
fs.writeFileSync(socketInfoPath, JSON.stringify({ socketPath: this.socketPath }), 'utf-8');
resolve();
});
});
}
// 处理客户端连接
private handleConnection(socket: net.Socket): void {
let dataBuffer = '';
socket.on('data', (data) => {
dataBuffer += data.toString();
try {
// 尝试解析 JSON 消息
const message = JSON.parse(dataBuffer);
dataBuffer = ''; // 重置缓冲区
// 处理请求
this.handleRequest(socket, message);
} catch (err) {
// 如果不是有效的 JSON，可能是消息不完整，继续等待
}
});
socket.on('error', (err) => {
console.error('Socket error:', err);
});
}
// 处理客户端请求
private handleRequest(socket: net.Socket, request: any): void {
const { id, method, params } = request;
// 根据请求方法执行相应的操作
switch (method) {
case 'GET_DATABASE_PATH':
this.handleGetDatabasePath(socket, id);
break;
case 'GET_USER_DATA_PATH':
this.handleGetUserDataPath(socket, id);
break;
default:
this.sendError(socket, id, `Unknown method: ${method}`);
}
}
// 处理获取数据库路径的请求
private handleGetDatabasePath(socket: net.Socket, id: string): void {
try {
const userDataPath = app.getPath('userData');
const dbPath = path.join(userDataPath, 'lobechat.db');
this.sendResult(socket, id, dbPath);
} catch (err) {
this.sendError(socket, id, `Failed to get database path: ${err.message}`);
}
}
// 处理获取用户数据路径的请求
private handleGetUserDataPath(socket: net.Socket, id: string): void {
try {
const userDataPath = app.getPath('userData');
this.sendResult(socket, id, userDataPath);
} catch (err) {
this.sendError(socket, id, `Failed to get user data path: ${err.message}`);
}
}
// 发送结果
private sendResult(socket: net.Socket, id: string, result: any): void {
socket.write(JSON.stringify({ id, result }));
}
// 发送错误
private sendError(socket: net.Socket, id: string, error: string): void {
socket.write(JSON.stringify({ id, error }));
}
// 关闭服务器
public close(): Promise<void> {
return new Promise((resolve) => {
this.server.close(() => {
console.log('Electron IPC server closed');
// 删除套接字文件（Unix 平台）
if (process.platform !== 'win32' && fs.existsSync(this.socketPath)) {
fs.unlinkSync(this.socketPath);
}
resolve();
});
});
}
}
// 在 Electron 主进程中使用
export const initIPCServer = async (): Promise<ElectronIPCServer> => {
const ipcServer = new ElectronIPCServer();
await ipcServer.start();
return ipcServer;
};在 Electron 主进程中初始化 IPC 服务器： // src-electron/main.ts
import { app, BrowserWindow } from 'electron';
import { initIPCServer } from './ipc-server';
import { createHandler } from 'next-electron-rsc';
let ipcServer: any = null;
app.whenReady().then(async () => {
// 初始化 IPC 服务器
ipcServer = await initIPCServer();
// 其他 Electron 初始化代码...
// ...
// 设置应用退出事件处理
app.on('will-quit', async () => {
if (ipcServer) {
await ipcServer.close();
}
});
});Next.js 服务端实现// src/utils/electron-ipc-client.ts
import net from 'net';
import fs from 'fs';
import os from 'os';
import path from 'path';
export class ElectronIPCClient {
private socketPath: string | null = null;
private connected: boolean = false;
private socket: net.Socket | null = null;
private requestQueue: Map<string, { resolve: Function, reject: Function }> = new Map();
private reconnectTimeout: NodeJS.Timeout | null = null;
private connectionAttempts: number = 0;
private maxConnectionAttempts: number = 5;
constructor() {
this.initialize();
}
// 初始化客户端
private initialize(): void {
try {
// 从临时文件读取套接字路径
const tempDir = os.tmpdir();
const socketInfoPath = path.join(tempDir, 'lobechat-electron-ipc-info.json');
if (fs.existsSync(socketInfoPath)) {
const socketInfo = JSON.parse(fs.readFileSync(socketInfoPath, 'utf-8'));
this.socketPath = socketInfo.socketPath;
} else {
// 如果找不到套接字信息，使用默认路径
this.socketPath = process.platform === 'win32'
? '\\\\.\\pipe\\lobechat-electron-ipc'
: path.join(os.tmpdir(), 'lobechat-electron-ipc.sock');
}
} catch (err) {
console.error('Failed to initialize IPC client:', err);
this.socketPath = null;
}
}
// 连接到 Electron IPC 服务器
private connect(): Promise<void> {
if (this.connected || !this.socketPath) {
return Promise.resolve();
}
return new Promise((resolve, reject) => {
try {
this.socket = net.createConnection(this.socketPath, () => {
this.connected = true;
this.connectionAttempts = 0;
console.log('Connected to Electron IPC server');
resolve();
});
this.socket.on('data', (data) => {
try {
const response = JSON.parse(data.toString());
const { id, result, error } = response;
const pending = this.requestQueue.get(id);
if (pending) {
this.requestQueue.delete(id);
if (error) {
pending.reject(new Error(error));
} else {
pending.resolve(result);
}
}
} catch (err) {
console.error('Failed to parse response:', err);
}
});
this.socket.on('error', (err) => {
console.error('Socket error:', err);
this.connected = false;
this.handleDisconnect();
reject(err);
});
this.socket.on('close', () => {
console.log('Socket closed');
this.connected = false;
this.handleDisconnect();
});
} catch (err) {
console.error('Failed to connect to IPC server:', err);
this.handleDisconnect();
reject(err);
}
});
}
// 处理断开连接
private handleDisconnect(): void {
// 清除重连定时器
if (this.reconnectTimeout) {
clearTimeout(this.reconnectTimeout);
this.reconnectTimeout = null;
}
// 拒绝所有待处理的请求
for (const [id, { reject }] of this.requestQueue) {
reject(new Error('Connection to Electron IPC server lost'));
}
this.requestQueue.clear();
// 尝试重新连接
if (this.connectionAttempts < this.maxConnectionAttempts) {
this.connectionAttempts++;
const delay = Math.min(1000 * Math.pow(2, this.connectionAttempts - 1), 30000);
this.reconnectTimeout = setTimeout(() => {
this.connect().catch((err) => {
console.error(`Reconnection attempt ${this.connectionAttempts} failed:`, err);
});
}, delay);
}
}
// 发送请求到 Electron IPC 服务器
public async sendRequest<T>(method: string, params: any = {}): Promise<T> {
if (!this.socketPath) {
throw new Error('Electron IPC connection not available');
}
// 如果未连接，先连接
if (!this.connected) {
await this.connect();
}
return new Promise<T>((resolve, reject) => {
try {
const id = Math.random().toString(36).substring(2, 15);
const request = { id, method, params };
// 将请求添加到队列
this.requestQueue.set(id, { resolve, reject });
// 设置超时
const timeout = setTimeout(() => {
this.requestQueue.delete(id);
reject(new Error(`Request ${method} timed out`));
}, 10000);
// 发送请求
this.socket!.write(JSON.stringify(request), (err) => {
if (err) {
clearTimeout(timeout);
this.requestQueue.delete(id);
reject(err);
}
});
} catch (err) {
reject(err);
}
});
}
// 获取数据库路径
public async getDatabasePath(): Promise<string> {
return this.sendRequest<string>('GET_DATABASE_PATH');
}
// 获取用户数据路径
public async getUserDataPath(): Promise<string> {
return this.sendRequest<string>('GET_USER_DATA_PATH');
}
// 关闭连接
public close(): void {
if (this.reconnectTimeout) {
clearTimeout(this.reconnectTimeout);
this.reconnectTimeout = null;
}
if (this.socket) {
this.socket.end();
this.socket = null;
}
this.connected = false;
}
}
// 创建单例客户端
let ipcClientInstance: ElectronIPCClient | null = null;
export const getElectronIPCClient = (): ElectronIPCClient => {
if (!ipcClientInstance) {
ipcClientInstance = new ElectronIPCClient();
}
return ipcClientInstance;
};在 Next.js 数据库模块中使用 IPC 客户端： // src/database/core/electron.ts
import { PGlite } from '@electric-sql/pglite';
import { drizzle as pgliteDrizzle } from 'drizzle-orm/pglite';
import * as schema from '@/database/schemas';
import { getElectronIPCClient } from '@/utils/electron-ipc-client';
import { LobeChatDatabase } from '../type';
// 初始化 PGLite 实例
export const getPgliteInstance = async (): Promise<LobeChatDatabase> => {
try {
// 从 Electron 主进程获取数据库路径
const ipcClient = getElectronIPCClient();
const dbPath = await ipcClient.getDatabasePath();
// 初始化 PGLite
const client = new PGlite(dbPath);
return pgliteDrizzle({ client, schema }) as unknown as LobeChatDatabase;
} catch (error) {
console.error('Failed to initialize PGLite:', error);
throw new Error(`Failed to initialize database: ${error.message}`);
}
};数据库工厂模式实现： // src/database/core/factory.ts
import { isDesktop } from '@/const/version';
import { getDBInstance as getWebDBInstance } from '@/database/core/web-server';
import { LobeChatDatabase } from '../type';
// 数据库实例缓存
let dbInstance: LobeChatDatabase | null = null;
// 根据环境创建适当的数据库实例
export const getDatabaseInstance = async (): Promise<LobeChatDatabase> => {
// 如果已经有缓存的实例，直接返回
if (dbInstance) return dbInstance;
if (isDesktop) {
// 动态导入 Electron 数据库模块
const { getPgliteInstance } = await import('./electron');
dbInstance = await getPgliteInstance();
return dbInstance;
} else {
// Web 环境使用 Neon Postgres
dbInstance = getWebDBInstance();
return dbInstance;
}
};5. 错误处理和恢复机制这个架构设计包含了以下错误处理和恢复机制：
6. 部署考虑Electron 应用构建在 includeSubNodeModules: true
files:
- build
- from: '.next/standalone/demo/'
to: '.next/standalone/demo/'Next.js 构建配置在 module.exports = {
output: 'standalone',
webpack: (config, { isServer, dev }) => {
// 排除 Electron 相关模块
config.externals = [...(config.externals || []), 'electron'];
return config;
},
experimental: {
outputFileTracingIncludes: {
'*': ['public/**/*', '.next/static/**/*'],
},
},
};7. 总结这个设计方案提供了一个完整的架构，使 Electron 主进程和 Next.js 服务端进程能够可靠地通信：
这种架构允许你在不同环境中使用相同的代码库，同时充分利用 Electron 的系统能力和 Next.js 的 Web 功能。 |
Beta Was this translation helpful? Give feedback.
-
|
端侧的用户授权流程 |
Beta Was this translation helpful? Give feedback.
-
|
是否考虑过增加单独的网络Proxy配置机制？不依赖系统的Proxy，以便用户可以灵活使用网络 参考Cherry Studio https://github.com/CherryHQ/cherry-studio/blob/main/src/main/services/ProxyManager.ts |
Beta Was this translation helpful? Give feedback.
-
|
@stephonye 倒是可以后面添加 |
Beta Was this translation helpful? Give feedback.
This comment has been hidden.
This comment has been hidden.
-
|
桌面版本希望可以支持类似快捷键打开快捷助手以及划词快捷小窗口功能。类似豆包的那种。 |
Beta Was this translation helpful? Give feedback.
-
|
这个可以抄一下主流的大模型桌面版 |
Beta Was this translation helpful? Give feedback.
-
IPC 进程间通信electron-client-ipc （Render 进程与 Main 进程通信）设计一个框架来实现轻巧的 Render 端与 main 端通信
export interface DevtoolsDispatchEvents {
/**
* open the LobeHub Devtools
*/
openDevtools: () => void;
}
import { dispatch } from '@/utils/electron/dispatch';
class DevtoolsService {
async openDevtools(): Promise<void> {
return dispatch('openDevtools');
}
}
export const electronDevtoolsService = new DevtoolsService();
// src/utils/electron/dispatch.ts
import { DispatchInvoke } from '@lobechat/electron-client-ipc';
/**
* client 端请求 sketch 端 event 数据的方法
*/
export const dispatch: DispatchInvoke = async (event, ...data) => {
if (!window.electronAPI) throw new Error('electronAPI not found');
return window.electronAPI?.invoke(event, ...data);
};这样应用层使用就可以当成是一个普通的 Service 来使用： onClick={async () => {
if (isDesktop) {
const { electronDevtoolsService } = await import('@/services/electron/devtools');
await electronDevtoolsService.openDevtools();
return;
} |
Beta Was this translation helpful? Give feedback.
-
Main 端配置存储机制概述大部分用户侧的业务数据将通过 pglite 存储，因此在 main 端使用基于 electron-store 的，轻量化实现一些设置数据的持久化，用于管理应用配置。本文档描述了当前的实现和方法。 存储管理类
|
| 方法 | 说明 | 参数 | 返回值 |
|---|---|---|---|
get |
获取配置项 | key: 配置键defaultValue?: 默认值 |
配置值 |
set |
设置配置项 | key: 配置键value: 配置值 |
无 |
delete |
删除配置项 | key: 配置键 |
无 |
clear |
清空所有配置 | 无 | 无 |
has |
检查配置项是否存在 | key: 配置键 |
boolean |
openInEditor |
在编辑器中打开配置文件 | 无 | Promise<void> |
使用示例
// 初始化
const store = new StoreManager(app);
// 获取配置
const value = store.get('someKey');
// 设置配置
store.set('someKey', newValue);
// 检查配置是否存在
if (store.has('optionalFeature')) {
// 执行相关操作
}
// 删除配置
store.delete('temporaryConfig');
// 在开发环境中直接编辑配置文件
await store.openInEditor();Beta Was this translation helpful? Give feedback.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
-
|
我今天搞了一下，目前问题感觉还是有的，我在设置界面，点击claude得设置和其他ai模型设置就会出现这个报错，然后无法关闭。 |
Beta Was this translation helpful? Give feedback.
-
|
哪个版本？ |
Beta Was this translation helpful? Give feedback.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
-
|
Beta Was this translation helpful? Give feedback.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
-
|
OpenAI以外的所有提供商都会提示 Key 不正确或为空，请检查 |
Beta Was this translation helpful? Give feedback.
-
我除了自定义的服务商，别的都不能用 |
Beta Was this translation helpful? Give feedback.
-
我是Windows端的 |
Beta Was this translation helpful? Give feedback.
-
|
同出现 请问解决了吗 |
Beta Was this translation helpful? Give feedback.
-
刚下载了最新的版本，问题还在，最近一直在用网页端，logto 应该被遗弃了 |
Beta Was this translation helpful? Give feedback.
-
我casdoor也这样，因为这个问题以及头像文件不能访问，导致我桌面端几乎不可用 |
Beta Was this translation helpful? Give feedback.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
-
|
怎么把Vercel部署的服务端连到Mac桌面端上啊，没看到设置里有相关的入口 |
Beta Was this translation helpful? Give feedback.
-
|
我用的Clerk认证登录，是不是要在Clerk里添加redirect urls啊 还是说得在Vercel里添加一个rediretct url相关的环境变量？ |
Beta Was this translation helpful? Give feedback.
-
|
升到1.82.9好啦，成功绑定！ |
Beta Was this translation helpful? Give feedback.
-
你需要添加 app url 确保网址是一样的 |
Beta Was this translation helpful? Give feedback.
-
|
cadoor在哪配置啊，提示 POST https://lobe.xxxx.xxx/oidc/consent 502 (Bad Gateway) |
Beta Was this translation helpful? Give feedback.
-
对对，我在桌面端填的是完全一样的应用地址，在Clerk没配重定向，正常绑定Vercel了~ |
Beta Was this translation helpful? Give feedback.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
-
|
我mac也是授权后无法跳转 |
Beta Was this translation helpful? Give feedback.
-
|
mac中占用了全局的cmd+e？ 没有快捷键设置的地方。 cmd+e快捷推出dmg挂载 |
Beta Was this translation helpful? Give feedback.
-
|
好像是，这个后面加一下自定义吧 |
Beta Was this translation helpful? Give feedback.
-
|
@arvinxx |
Beta Was this translation helpful? Give feedback.
-
|
如果你是 minio 的话，要在 minio 里找下允许跨域的配置 |
Beta Was this translation helpful? Give feedback.
-
大佬，怎么设置minio跨域啊，是要容器的控制台里面吗 |
Beta Was this translation helpful? Give feedback.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
and others
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
背景
桌面端是我们必须要做的东西，无论是从产品体验，还是说能力边界，桌面端都是能够给我们带来很多拓展能力边界的形态。
设计思路
首先桌面端选型上是 Electron 这个无可争议，我之前还做过一个带有自动化 ci workflow 的 electron 脚手架模板，基本上是轻车熟路了。
不过在具体评估可行方案时，我们需要考虑现有 Nextjs 项目的复用问题，因此调研到了几种可能的潜在可选项。
基座调研
ToDesktop
ToDesktop 是一款专业的 Web 应用转桌面应用工具，允许开发者快速将现有 Web 应用转换为跨平台（Windows、Mac 和 Linux）的原生桌面应用。无需编写额外代码即可实现基础功能，同时提供丰富的原生 API 扩展能力。
ToDesktop 的核心优势包括：自动更新系统、原生通知、离线支持、全局热键、系统托盘、深度链接、启动项设置等原生功能。它提供了直观的拖放式构建器，使开发者能够轻松定制应用外观和行为。
对于企业用户，ToDesktop 还提供代码签名、下载分析、品牌化下载链接等高级功能。其定价从个人免费使用到企业级解决方案不等，适合从个人开发者到大型企业的各类需求。
这个方案的优点是省心，可以一键将在线网页转为 desktop 套壳应用。但缺点有几个：
因此这个方案被抛弃了。
next-electron-rsc
这个方案来源于 https://medium.com/@kirill.konshin/the-ultimate-electron-app-with-next-js-and-react-server-components-a5c0cabda72b 这篇文章，通过一天的尝试发现可以很完美地跑起来。因此整个实现的基座就会基于这个包来搞。
独立 repo VS 主仓库子目录
本来一开始想的是独立 repo，但是评估下来发现维护整个成本会有点高，因为我们现在的 cloud 是在 开源版 lobe-chat 基础上的一个私有仓库，如果开源版桌面端是一个独立 repo，就意味着 cloud 的仓库也需要对应变成独立 repo，一次性维护4个仓库显然成本有点过高了。
进展
Beta Was this translation helpful? Give feedback.
All reactions