[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f-3cW5X2kPgV6XYvUIGPj-6F3qgHUs1LBtSOeYlI6nAI":3,"$fJU-4tot_gC5fDkujNeoE-cGsdMy5V_KcdUXLuAnTFgw":16,"$fbq8LvJpeVq4hUcMLpl3Rf52w0Jtj8bAYOENW7uvgBHE":423},{"slug":4,"title":5,"description":6,"content":7,"content_html":8,"pub_date":9,"tags":10,"draft":15},"npm-electron-install-fix","彻底解决 npm 安装 Electron 失败的问题","分析 npm install electron 失败的根本原因（下载二进制超时\u002F被墙），通过国内镜像（npmmirror）彻底解决，并介绍多种备选方案和常见错误排查。","# 彻底解决 npm 安装 Electron 失败的问题\n\nElectron 的安装是前端工程师最常碰壁的环节之一，尤其是在国内网络环境下。本文系统梳理根因，并提供 2024-2025 年最新有效的解决方案，覆盖 npm、pnpm、Yarn、Bun 以及 CI\u002FCD 场景。\n\n## Electron 安装为何特殊\n\n### 两阶段安装机制\n\n安装 Electron 不像普通 npm 包那样只下载 JavaScript 代码。它分两个阶段：\n\n**阶段一**：npm 下载 `electron` 包本身（只有几 KB 的 JS 代码和配置）\n\n**阶段二**：`postinstall` 脚本运行 `electron\u002Finstall.js`，从 GitHub Releases 下载预编译的二进制文件（`electron-vX.X.X-platform-arch.zip`），大小约 100~300 MB。\n\n```\nnode_modules\u002Felectron\u002F\n  install.js         ← postinstall 运行这个\n  path.txt           ← 记录已下载的二进制路径\n  dist\u002F\n    electron         ← 这才是真正的 Electron 可执行文件\n    resources\u002F\n    ...\n```\n\n### 国内网络根因\n\n预编译二进制文件托管在 `https:\u002F\u002Fgithub.com\u002Felectron\u002Felectron\u002Freleases`。由于众所周知的原因，GitHub Releases 的下载在国内极不稳定：\n\n- 下载速度极慢（可能 10KB\u002Fs 甚至更低）\n- 频繁超时（默认超时 30s）\n- 随机中断\n\n这导致 `npm install` 在 `node_modules\u002F.cache` 阶段挂起，最终以如下错误结束：\n\n```\nRequestError: connect ETIMEDOUT 140.82.114.4:443\n  at ClientRequest.\u003Canonymous> (node_modules\u002Fgot\u002Fsource\u002Frequest-as-event-emitter.js:178:14)\n  ...\n\n或\n\n× [Electron] Downloading Electron... failed\n  Error: read ECONNRESET\n```\n\n## 三种解决方案\n\n### 方案一：.npmrc 镜像（最推荐）\n\n在项目根目录（或用户主目录）创建\u002F修改 `.npmrc`：\n\n```ini\n# 设置 Electron 镜像\nELECTRON_MIRROR=https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F\n\n# 也可以设置 npm registry 镜像\nregistry=https:\u002F\u002Fregistry.npmmirror.com\n```\n\n`npmmirror.com`（原淘宝镜像，现官方维护）是目前最稳定的国内镜像，同步 GitHub Releases 通常在几分钟内。\n\n**全局设置（推荐放在 `~\u002F.npmrc`）**：\n\n```bash\nnpm config set ELECTRON_MIRROR https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F\nnpm config set registry https:\u002F\u002Fregistry.npmmirror.com\n```\n\n验证设置：\n\n```bash\nnpm config get ELECTRON_MIRROR\n# 输出：https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F\n```\n\n### 方案二：环境变量\n\n不想改 `.npmrc`？可以通过环境变量临时设置：\n\n```bash\n# Linux\u002FmacOS\nexport ELECTRON_MIRROR=https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F\nnpm install electron\n\n# Windows PowerShell\n$env:ELECTRON_MIRROR = \"https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F\"\nnpm install electron\n\n# Windows CMD\nset ELECTRON_MIRROR=https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F\nnpm install electron\n```\n\n也可以在单次命令中指定（跨平台推荐用 `cross-env`）：\n\n```bash\nnpx cross-env ELECTRON_MIRROR=https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F npm install\n```\n\n### 方案三：手动缓存\n\n如果网络实在无法访问，可以手动下载二进制文件并放到缓存目录。\n\n**1. 确定需要的版本和文件名**：\n\n```bash\n# 查看 package.json 中的 electron 版本\ncat node_modules\u002Felectron\u002Fpackage.json | grep '\"version\"'\n# 例如：\"version\": \"32.0.0\"\n\n# 文件名格式\n# electron-v{version}-{platform}-{arch}.zip\n# 例如：electron-v32.0.0-win32-x64.zip\n#       electron-v32.0.0-linux-x64.zip\n#       electron-v32.0.0-darwin-arm64.zip\n```\n\n**2. 手动下载**（可通过有代理的机器或手机热点下载）：\n\n从 `https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002Fv32.0.0\u002F` 下载对应平台的 zip 文件。\n\n**3. 放到缓存目录**：\n\n```bash\n# Windows\n%LOCALAPPDATA%\\electron\\Cache\n# macOS\n~\u002FLibrary\u002FCaches\u002Felectron\u002F\n\n# Linux\n~\u002F.cache\u002Felectron\u002F\n\n# 具体路径可以通过 electron-download 查看：\nnode -e \"const p = require('path'); console.log(p.join(require('os').homedir(), '.cache', 'electron'))\"\n```\n\n将下载的 zip 文件直接放入以上目录，重新运行 `npm install`，install.js 会检测到本地缓存并跳过下载。\n\n## pnpm 的对应方案\n\npnpm 使用相同的环境变量：\n\n```bash\n# .npmrc（pnpm 也读取）\nELECTRON_MIRROR=https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F\n\n# 或环境变量\nELECTRON_MIRROR=https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F pnpm install\n```\n\npnpm 特有的配置（`~\u002F.pnpmfile.cjs` 或 `.pnpmrc`）：\n\n```ini\n# .pnpmrc\nelectron_mirror=https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F\n```\n\n## Yarn 的对应方案\n\nYarn Classic (v1)：\n\n```bash\n# 全局设置\nyarn config set ELECTRON_MIRROR https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F\n\n# .yarnrc（项目级）\nELECTRON_MIRROR \"https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F\"\n```\n\nYarn Berry (v2+)：\n\n```yaml\n# .yarnrc.yml\nnpmRegistryServer: \"https:\u002F\u002Fregistry.npmmirror.com\"\n\n# Electron 镜像通过环境变量设置，Yarn Berry 不支持 .npmrc 中的 ELECTRON_MIRROR\n# 在 .env 文件中设置（需要 dotenv 支持），或在 shell 中 export\n```\n\n## Bun 的对应方案\n\nBun 也遵循 `ELECTRON_MIRROR` 环境变量：\n\n```bash\nELECTRON_MIRROR=https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F bun install\n```\n\nBun 的 `bunfig.toml` 配置：\n\n```toml\n[install]\nregistry = \"https:\u002F\u002Fregistry.npmmirror.com\"\n# 注意：截至 2024 年底，Bun 不直接在 bunfig.toml 支持 ELECTRON_MIRROR\n# 需要通过环境变量设置\n```\n\n## CI\u002FCD 配置\n\n### GitHub Actions\n\n```yaml\n# .github\u002Fworkflows\u002Fbuild.yml\nname: Build\n\non: [push]\n\njobs:\n  build:\n    runs-on: ubuntu-latest\n    \n    env:\n      # GitHub Actions 网络畅通，不需要镜像\n      # 但可以通过 electron\u002Fcache 缓存加速\n      ELECTRON_CACHE: ${{ github.workspace }}\u002F.cache\u002Felectron\n      \n    steps:\n      - uses: actions\u002Fcheckout@v4\n      \n      # 缓存 Electron 二进制（大幅减少安装时间）\n      - name: Cache Electron\n        uses: actions\u002Fcache@v4\n        with:\n          path: ${{ env.ELECTRON_CACHE }}\n          key: ${{ runner.os }}-electron-${{ hashFiles('**\u002Fpackage-lock.json') }}\n          restore-keys: |\n            ${{ runner.os }}-electron-\n      \n      - name: Install dependencies\n        run: npm install\n        env:\n          ELECTRON_CACHE: ${{ env.ELECTRON_CACHE }}\n```\n\n### 自建 CI（国内服务器）\n\n```yaml\n# 在国内 CI 环境中使用镜像\nsteps:\n  - name: Setup npm mirror\n    run: |\n      npm config set registry https:\u002F\u002Fregistry.npmmirror.com\n      npm config set ELECTRON_MIRROR https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F\n  \n  - name: Install\n    run: npm install\n```\n\n### Jenkins \u002F GitLab CI\n\n```groovy\n\u002F\u002F Jenkinsfile\nstage('Install') {\n    environment {\n        ELECTRON_MIRROR = 'https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F'\n        NPM_CONFIG_REGISTRY = 'https:\u002F\u002Fregistry.npmmirror.com'\n    }\n    steps {\n        sh 'npm install'\n    }\n}\n```\n\n```yaml\n# .gitlab-ci.yml\nvariables:\n  ELECTRON_MIRROR: \"https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F\"\n  NPM_CONFIG_REGISTRY: \"https:\u002F\u002Fregistry.npmmirror.com\"\n\ninstall:\n  script:\n    - npm install\n```\n\n## 验证方法\n\n安装成功后验证 Electron 是否可用：\n\n```bash\n# 查看安装的 Electron 版本\nnpx electron --version\n# 或\n.\u002Fnode_modules\u002F.bin\u002Felectron --version\n\n# 验证二进制文件存在\nls node_modules\u002Felectron\u002Fdist\u002F\n# Linux: electron  (可执行文件)\n# Windows: electron.exe\n# macOS: Electron.app\u002F\n\n# 检查 path.txt（记录实际路径）\ncat node_modules\u002Felectron\u002Fpath.txt\n```\n\n如果 `path.txt` 存在且内容指向有效的可执行文件，说明安装成功。\n\n## 2024-2025 最新可用镜像\n\n经过实测，以下镜像在 2025 年仍可用（按稳定性排序）：\n\n| 镜像 | URL | 备注 |\n|------|-----|------|\n| npmmirror（推荐） | `https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F` | 官方维护，同步快 |\n| 华为云 | `https:\u002F\u002Fmirrors.huaweicloud.com\u002Felectron\u002F` | 速度快 |\n| 腾讯云 | `https:\u002F\u002Fmirrors.cloud.tencent.com\u002Felectron\u002F` | 稳定 |\n| 阿里云 | `https:\u002F\u002Fcdn.npmmirror.com\u002Fbinaries\u002Felectron\u002F` | 同 npmmirror CDN |\n\n**注意**：各镜像的可用性随时间变化，如果某个镜像失效，请先尝试 npmmirror。\n\n## 常见问题排查\n\n```bash\n# 查看 install.js 的详细日志\nDEBUG=electron-download npm install electron\n\n# 清除缓存重新安装\nnpm cache clean --force\nrm -rf node_modules\u002Felectron\nnpm install electron\n\n# 指定版本安装（有时最新版镜像同步有延迟）\nnpm install electron@31.0.0\n\n# 网络诊断\ncurl -I https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F\ncurl -I https:\u002F\u002Fgithub.com\u002Felectron\u002Felectron\u002Freleases\n```\n\n掌握这些方法，Electron 的安装问题就再也不会困扰你了。\n","\u003Ch1>彻底解决 npm 安装 Electron 失败的问题\u003C\u002Fh1>\n\u003Cp>Electron 的安装是前端工程师最常碰壁的环节之一，尤其是在国内网络环境下。本文系统梳理根因，并提供 2024-2025 年最新有效的解决方案，覆盖 npm、pnpm、Yarn、Bun 以及 CI\u002FCD 场景。\u003C\u002Fp>\n\u003Ch2 id=\"electron-安装为何特殊\">Electron 安装为何特殊\u003C\u002Fh2>\n\u003Ch3 id=\"两阶段安装机制\">两阶段安装机制\u003C\u002Fh3>\n\u003Cp>安装 Electron 不像普通 npm 包那样只下载 JavaScript 代码。它分两个阶段：\u003C\u002Fp>\n\u003Cp>\u003Cstrong>阶段一\u003C\u002Fstrong>：npm 下载 \u003Ccode>electron\u003C\u002Fcode> 包本身（只有几 KB 的 JS 代码和配置）\u003C\u002Fp>\n\u003Cp>\u003Cstrong>阶段二\u003C\u002Fstrong>：\u003Ccode>postinstall\u003C\u002Fcode> 脚本运行 \u003Ccode>electron\u002Finstall.js\u003C\u002Fcode>，从 GitHub Releases 下载预编译的二进制文件（\u003Ccode>electron-vX.X.X-platform-arch.zip\u003C\u002Fcode>），大小约 100~300 MB。\u003C\u002Fp>\n\u003Cpre>\u003Ccode>node_modules\u002Felectron\u002F\n  install.js         ← postinstall 运行这个\n  path.txt           ← 记录已下载的二进制路径\n  dist\u002F\n    electron         ← 这才是真正的 Electron 可执行文件\n    resources\u002F\n    ...\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3 id=\"国内网络根因\">国内网络根因\u003C\u002Fh3>\n\u003Cp>预编译二进制文件托管在 \u003Ccode>https:\u002F\u002Fgithub.com\u002Felectron\u002Felectron\u002Freleases\u003C\u002Fcode>。由于众所周知的原因，GitHub Releases 的下载在国内极不稳定：\u003C\u002Fp>\n\u003Cul>\n\u003Cli>下载速度极慢（可能 10KB\u002Fs 甚至更低）\u003C\u002Fli>\n\u003Cli>频繁超时（默认超时 30s）\u003C\u002Fli>\n\u003Cli>随机中断\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>这导致 \u003Ccode>npm install\u003C\u002Fcode> 在 \u003Ccode>node_modules\u002F.cache\u003C\u002Fcode> 阶段挂起，最终以如下错误结束：\u003C\u002Fp>\n\u003Cpre>\u003Ccode>RequestError: connect ETIMEDOUT 140.82.114.4:443\n  at ClientRequest.<anonymous> (node_modules\u002Fgot\u002Fsource\u002Frequest-as-event-emitter.js:178:14)\n  ...\n\n或\n\n× [Electron] Downloading Electron... failed\n  Error: read ECONNRESET\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch2 id=\"三种解决方案\">三种解决方案\u003C\u002Fh2>\n\u003Ch3 id=\"方案一-npmrc-镜像-最推荐\">方案一：.npmrc 镜像（最推荐）\u003C\u002Fh3>\n\u003Cp>在项目根目录（或用户主目录）创建\u002F修改 \u003Ccode>.npmrc\u003C\u002Fcode>：\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-ini\"># 设置 Electron 镜像\nELECTRON_MIRROR=https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F\n\n# 也可以设置 npm registry 镜像\nregistry=https:\u002F\u002Fregistry.npmmirror.com\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Ccode>npmmirror.com\u003C\u002Fcode>（原淘宝镜像，现官方维护）是目前最稳定的国内镜像，同步 GitHub Releases 通常在几分钟内。\u003C\u002Fp>\n\u003Cp>\u003Cstrong>全局设置（推荐放在 \u003Ccode>~\u002F.npmrc\u003C\u002Fcode>）\u003C\u002Fstrong>：\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">npm config set ELECTRON_MIRROR https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F\nnpm config set registry https:\u002F\u002Fregistry.npmmirror.com\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>验证设置：\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">npm config get ELECTRON_MIRROR\n# 输出：https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3 id=\"方案二-环境变量\">方案二：环境变量\u003C\u002Fh3>\n\u003Cp>不想改 \u003Ccode>.npmrc\u003C\u002Fcode>？可以通过环境变量临时设置：\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\"># Linux\u002FmacOS\nexport ELECTRON_MIRROR=https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F\nnpm install electron\n\n# Windows PowerShell\n$env:ELECTRON_MIRROR = "https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F"\nnpm install electron\n\n# Windows CMD\nset ELECTRON_MIRROR=https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F\nnpm install electron\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>也可以在单次命令中指定（跨平台推荐用 \u003Ccode>cross-env\u003C\u002Fcode>）：\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">npx cross-env ELECTRON_MIRROR=https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F npm install\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3 id=\"方案三-手动缓存\">方案三：手动缓存\u003C\u002Fh3>\n\u003Cp>如果网络实在无法访问，可以手动下载二进制文件并放到缓存目录。\u003C\u002Fp>\n\u003Cp>\u003Cstrong>1. 确定需要的版本和文件名\u003C\u002Fstrong>：\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\"># 查看 package.json 中的 electron 版本\ncat node_modules\u002Felectron\u002Fpackage.json | grep '"version"'\n# 例如："version": "32.0.0"\n\n# 文件名格式\n# electron-v{version}-{platform}-{arch}.zip\n# 例如：electron-v32.0.0-win32-x64.zip\n#       electron-v32.0.0-linux-x64.zip\n#       electron-v32.0.0-darwin-arm64.zip\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>2. 手动下载\u003C\u002Fstrong>（可通过有代理的机器或手机热点下载）：\u003C\u002Fp>\n\u003Cp>从 \u003Ccode>https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002Fv32.0.0\u002F\u003C\u002Fcode> 下载对应平台的 zip 文件。\u003C\u002Fp>\n\u003Cp>\u003Cstrong>3. 放到缓存目录\u003C\u002Fstrong>：\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\"># Windows\n%LOCALAPPDATA%\\electron\\Cache\n# macOS\n~\u002FLibrary\u002FCaches\u002Felectron\u002F\n\n# Linux\n~\u002F.cache\u002Felectron\u002F\n\n# 具体路径可以通过 electron-download 查看：\nnode -e "const p = require('path'); console.log(p.join(require('os').homedir(), '.cache', 'electron'))"\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>将下载的 zip 文件直接放入以上目录，重新运行 \u003Ccode>npm install\u003C\u002Fcode>，install.js 会检测到本地缓存并跳过下载。\u003C\u002Fp>\n\u003Ch2 id=\"pnpm-的对应方案\">pnpm 的对应方案\u003C\u002Fh2>\n\u003Cp>pnpm 使用相同的环境变量：\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\"># .npmrc（pnpm 也读取）\nELECTRON_MIRROR=https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F\n\n# 或环境变量\nELECTRON_MIRROR=https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F pnpm install\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>pnpm 特有的配置（\u003Ccode>~\u002F.pnpmfile.cjs\u003C\u002Fcode> 或 \u003Ccode>.pnpmrc\u003C\u002Fcode>）：\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-ini\"># .pnpmrc\nelectron_mirror=https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch2 id=\"yarn-的对应方案\">Yarn 的对应方案\u003C\u002Fh2>\n\u003Cp>Yarn Classic (v1)：\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\"># 全局设置\nyarn config set ELECTRON_MIRROR https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F\n\n# .yarnrc（项目级）\nELECTRON_MIRROR "https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F"\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Yarn Berry (v2+)：\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-yaml\"># .yarnrc.yml\nnpmRegistryServer: "https:\u002F\u002Fregistry.npmmirror.com"\n\n# Electron 镜像通过环境变量设置，Yarn Berry 不支持 .npmrc 中的 ELECTRON_MIRROR\n# 在 .env 文件中设置（需要 dotenv 支持），或在 shell 中 export\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch2 id=\"bun-的对应方案\">Bun 的对应方案\u003C\u002Fh2>\n\u003Cp>Bun 也遵循 \u003Ccode>ELECTRON_MIRROR\u003C\u002Fcode> 环境变量：\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">ELECTRON_MIRROR=https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F bun install\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Bun 的 \u003Ccode>bunfig.toml\u003C\u002Fcode> 配置：\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-toml\">[install]\nregistry = "https:\u002F\u002Fregistry.npmmirror.com"\n# 注意：截至 2024 年底，Bun 不直接在 bunfig.toml 支持 ELECTRON_MIRROR\n# 需要通过环境变量设置\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch2 id=\"ci-cd-配置\">CI\u002FCD 配置\u003C\u002Fh2>\n\u003Ch3 id=\"github-actions\">GitHub Actions\u003C\u002Fh3>\n\u003Cpre>\u003Ccode class=\"language-yaml\"># .github\u002Fworkflows\u002Fbuild.yml\nname: Build\n\non: [push]\n\njobs:\n  build:\n    runs-on: ubuntu-latest\n    \n    env:\n      # GitHub Actions 网络畅通，不需要镜像\n      # 但可以通过 electron\u002Fcache 缓存加速\n      ELECTRON_CACHE: ${{ github.workspace }}\u002F.cache\u002Felectron\n      \n    steps:\n      - uses: actions\u002Fcheckout@v4\n      \n      # 缓存 Electron 二进制（大幅减少安装时间）\n      - name: Cache Electron\n        uses: actions\u002Fcache@v4\n        with:\n          path: ${{ env.ELECTRON_CACHE }}\n          key: ${{ runner.os }}-electron-${{ hashFiles('**\u002Fpackage-lock.json') }}\n          restore-keys: |\n            ${{ runner.os }}-electron-\n      \n      - name: Install dependencies\n        run: npm install\n        env:\n          ELECTRON_CACHE: ${{ env.ELECTRON_CACHE }}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3 id=\"自建-ci-国内服务器\">自建 CI（国内服务器）\u003C\u002Fh3>\n\u003Cpre>\u003Ccode class=\"language-yaml\"># 在国内 CI 环境中使用镜像\nsteps:\n  - name: Setup npm mirror\n    run: |\n      npm config set registry https:\u002F\u002Fregistry.npmmirror.com\n      npm config set ELECTRON_MIRROR https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F\n  \n  - name: Install\n    run: npm install\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3 id=\"jenkins-gitlab-ci\">Jenkins \u002F GitLab CI\u003C\u002Fh3>\n\u003Cpre>\u003Ccode class=\"language-groovy\">\u002F\u002F Jenkinsfile\nstage('Install') {\n    environment {\n        ELECTRON_MIRROR = 'https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F'\n        NPM_CONFIG_REGISTRY = 'https:\u002F\u002Fregistry.npmmirror.com'\n    }\n    steps {\n        sh 'npm install'\n    }\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cpre>\u003Ccode class=\"language-yaml\"># .gitlab-ci.yml\nvariables:\n  ELECTRON_MIRROR: "https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F"\n  NPM_CONFIG_REGISTRY: "https:\u002F\u002Fregistry.npmmirror.com"\n\ninstall:\n  script:\n    - npm install\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch2 id=\"验证方法\">验证方法\u003C\u002Fh2>\n\u003Cp>安装成功后验证 Electron 是否可用：\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\"># 查看安装的 Electron 版本\nnpx electron --version\n# 或\n.\u002Fnode_modules\u002F.bin\u002Felectron --version\n\n# 验证二进制文件存在\nls node_modules\u002Felectron\u002Fdist\u002F\n# Linux: electron  (可执行文件)\n# Windows: electron.exe\n# macOS: Electron.app\u002F\n\n# 检查 path.txt（记录实际路径）\ncat node_modules\u002Felectron\u002Fpath.txt\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>如果 \u003Ccode>path.txt\u003C\u002Fcode> 存在且内容指向有效的可执行文件，说明安装成功。\u003C\u002Fp>\n\u003Ch2 id=\"2024-2025-最新可用镜像\">2024-2025 最新可用镜像\u003C\u002Fh2>\n\u003Cp>经过实测，以下镜像在 2025 年仍可用（按稳定性排序）：\u003C\u002Fp>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>镜像\u003C\u002Fth>\n\u003Cth>URL\u003C\u002Fth>\n\u003Cth>备注\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>npmmirror（推荐）\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>官方维护，同步快\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>华为云\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>https:\u002F\u002Fmirrors.huaweicloud.com\u002Felectron\u002F\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>速度快\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>腾讯云\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>https:\u002F\u002Fmirrors.cloud.tencent.com\u002Felectron\u002F\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>稳定\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>阿里云\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>https:\u002F\u002Fcdn.npmmirror.com\u002Fbinaries\u002Felectron\u002F\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>同 npmmirror CDN\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003Cp>\u003Cstrong>注意\u003C\u002Fstrong>：各镜像的可用性随时间变化，如果某个镜像失效，请先尝试 npmmirror。\u003C\u002Fp>\n\u003Ch2 id=\"常见问题排查\">常见问题排查\u003C\u002Fh2>\n\u003Cpre>\u003Ccode class=\"language-bash\"># 查看 install.js 的详细日志\nDEBUG=electron-download npm install electron\n\n# 清除缓存重新安装\nnpm cache clean --force\nrm -rf node_modules\u002Felectron\nnpm install electron\n\n# 指定版本安装（有时最新版镜像同步有延迟）\nnpm install electron@31.0.0\n\n# 网络诊断\ncurl -I https:\u002F\u002Fnpmmirror.com\u002Fmirrors\u002Felectron\u002F\ncurl -I https:\u002F\u002Fgithub.com\u002Felectron\u002Felectron\u002Freleases\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>掌握这些方法，Electron 的安装问题就再也不会困扰你了。\u003C\u002Fp>\n","2024-03-01",[11,12,13,14],"electron","npm","前端工具链","国内镜像",false,[17,30,41,53,63,70,77,84,91,98,108,117,127,136,144,152,161,170,179,189,196,206,212,219,225,234,241,248,256,265,274,283,293,303,306,314,324,335,345,354,362,368,376,384,392,400,408,415],{"slug":18,"title":19,"description":20,"pub_date":21,"tags":22,"draft":15,"word_count":29},"ide-skills-guide","Agent Skills 完全指南：21 款第三方 Skill 深度评测与使用心得","全面评测 21 款第三方 Agent Skills，涵盖 Vue 生态、前端设计、构建工具、实用工具四大分类。从安装配置到实际使用场景，带你了解每个 Skill 的功能特点、最佳实践与使用心得。","2026-06-15",[23,24,25,26,27,28],"agent","skills","AI","效率工具","前端","Vue",4169,{"slug":31,"title":32,"description":33,"pub_date":34,"tags":35,"draft":15,"word_count":40},"linux-kernel-skeleton-struct-funcptr-container_of","Linux 内核骨架：struct、函数指针与 container_of","读懂 Linux 内核源码的三件套：巨大的 struct 组合代替继承、函数指针表实现虚派发、container_of 宏从嵌入成员找回完整对象。","2026-05-09",[36,37,38,39],"linux","kernel","C","container_of",1369,{"slug":42,"title":43,"description":44,"pub_date":45,"tags":46,"draft":15,"word_count":52},"astro-complete-guide-2025","Astro 5 深度剖析：Islands 架构原理、构建优化与 Cloudflare Workers 边缘部署","从编译器视角解析 Astro 5 的 Islands 架构实现原理，Content Layer API 的 Vite 插件机制，Server Islands 的流式渲染，以及如何在 Cloudflare Workers + D1 边缘环境下榨干性能。","2026-05-08",[47,48,49,50,51],"astro","frontend","cloudflare","performance","architecture",3663,{"slug":54,"title":55,"description":56,"pub_date":57,"tags":58,"draft":15,"word_count":62},"llm-prompt-engineering","Prompt Engineering 实战：让 LLM 真正听话的技巧","System prompt 怎么写、Few-shot 怎么设计、Chain-of-Thought 原理，以及常见失败模式和调试方法。","2026-05-03",[59,60,61],"ai","llm","工程实践",1723,{"slug":64,"title":65,"description":66,"pub_date":57,"tags":67,"draft":15,"word_count":69},"rag-system-design","RAG 系统设计：从 naive 到 production-ready","Retrieval-Augmented Generation 不只是「向量数据库 + LLM」，分块策略、召回质量、重排序、缓存才是工程核心。",[59,68,60,61],"rag",1613,{"slug":71,"title":72,"description":73,"pub_date":57,"tags":74,"draft":15,"word_count":76},"git-advanced-workflow","Git 进阶工作流：rebase、cherry-pick、bisect 的正确使用","merge 会了，但 rebase 总搞错？bisect 找 bug 提交？interactive rebase 整理历史？这篇一次说清楚。",[75,61],"git",1396,{"slug":78,"title":79,"description":80,"pub_date":57,"tags":81,"draft":15,"word_count":83},"docker-practical-guide","Docker 实战：从会用到用好","会 docker run 不够，Dockerfile 最佳实践、多阶段构建、Compose 编排、镜像瘦身才是日常真正需要的。",[82,36,61],"docker",1268,{"slug":85,"title":86,"description":87,"pub_date":57,"tags":88,"draft":15,"word_count":90},"anthropics-skills-guide","anthropics\u002Fskills：Anthropic 官方 Agent Skills 仓库解析","Anthropic 官方开源的 Agent Skills 标准仓库，127k stars，解析 SKILL.md 规范、17 个示例 skill 的设计模式，以及如何在 Claude Code \u002F Claude.ai \u002F API 中使用",[59,89,23,24],"Claude",2090,{"slug":92,"title":93,"description":94,"pub_date":57,"tags":95,"draft":15,"word_count":97},"karpathy-claude-code-guidelines","Karpathy 的 LLM 编码批评与 CLAUDE.md 最佳实践","基于 Andrej Karpathy 对 LLM 编程助手的观察，forrestchang 提炼出一个 CLAUDE.md 文件，4 条原则解决 AI 编码的典型失控问题：乱猜假设、过度设计、乱改代码、目标不清",[59,89,96,61],"Claude Code",2699,{"slug":99,"title":100,"description":101,"pub_date":57,"tags":102,"draft":15,"word_count":107},"typescript-advanced-patterns","TypeScript 高级模式：让类型系统为你工作","基础 TS 会了但类型总是 any？条件类型、映射类型、模板字面量类型、infer 关键字才是 TS 的真正威力。",[103,104,105,106],"typescript","类型系统","前端工程","高级模式",1419,{"slug":109,"title":110,"description":111,"pub_date":57,"tags":112,"draft":15,"word_count":116},"linux-performance-tuning","Linux 性能调优实战：从 top 到 perf 的完整工具链","遇到性能问题不知道从哪下手？这篇建立系统化的排查思路，从 CPU\u002F内存\u002FIO\u002F网络逐层分析。",[36,113,114,115],"性能","运维","系统编程",1524,{"slug":118,"title":119,"description":120,"pub_date":57,"tags":121,"draft":15,"word_count":126},"python-functional-programming","Python 函数式编程：map\u002Ffilter\u002Freduce 之外","Python 不是纯函数式语言，但 functools、itertools、偏函数、闭包这些工具用好了能让代码简洁一个量级。",[122,123,124,125],"python","函数式","闭包","装饰器",1867,{"slug":128,"title":129,"description":130,"pub_date":57,"tags":131,"draft":15,"word_count":135},"python-oop-guide","Python 面向对象：__init__ 之外你需要知道的","Python OOP 不只是 class + __init__，魔术方法、描述符、元类才是真正的武器。",[122,132,133,134],"OOP","面向对象","魔术方法",1792,{"slug":137,"title":138,"description":139,"pub_date":57,"tags":140,"draft":15,"word_count":143},"python-data-structures","Python 内置数据结构深度解析","list、dict、set、tuple 不只是数据容器，搞懂它们的底层实现和时间复杂度，才能写出高性能 Python。",[122,141,113,142],"数据结构","算法",1517,{"slug":145,"title":146,"description":147,"pub_date":57,"tags":148,"draft":15,"word_count":151},"python-basics-quick-start","Python 快速上手：写给有编程基础的人","已经会其他语言，想快速掌握 Python 的语法特性和思维方式，这篇是捷径。",[122,149,150],"入门","基础",1607,{"slug":153,"title":154,"description":155,"pub_date":57,"tags":156,"draft":15,"word_count":160},"python-dataclass-pydantic","Python dataclass vs Pydantic：数据类选型指南","dataclass 是标准库的轻量选择，Pydantic v2 是带验证的重武器，什么时候用哪个，这篇说清楚。",[122,157,158,159],"dataclass","pydantic","数据验证",1323,{"slug":162,"title":163,"description":164,"pub_date":57,"tags":165,"draft":15,"word_count":169},"python-asyncio-practical","Python asyncio 实战：从回调地狱到协程优雅","asyncio 是 Python 异步编程的核心，搞懂 event loop、Task、gather 这些概念才能写出真正高效的异步代码。",[122,166,167,168],"asyncio","并发","网络编程",1258,{"slug":171,"title":172,"description":173,"pub_date":57,"tags":174,"draft":15,"word_count":178},"python-type-hints-guide","Python 类型注解完全指南：从入门到实践","Python 3.5+ 引入类型注解，配合 mypy\u002Fpyright 让 Python 也能享受静态类型检查的好处。",[122,175,176,177],"typescript-style","type-hints","工具链",1102,{"slug":180,"title":181,"description":182,"pub_date":183,"tags":184,"draft":15,"word_count":188},"pwa-install-update-button","PWA 踩坑：为什么安装按钮从来不出现","从 beforeinstallprompt 到 Service Worker waiting，把 PWA 的安装与更新提示真正做对","2026-05-02",[185,186,187],"pwa","javascript","web",1683,{"slug":190,"title":191,"description":192,"pub_date":193,"tags":194,"draft":15,"word_count":195},"openclaw-vs-hermes-agent","OpenClaw vs Hermes Agent：两个本地优先 Agent 的设计差异","OpenClaw（Novita AI）和 Hermes Agent（Nous Research）都是本地运行的个人 AI Agent，但在记忆系统、技能学习、运行环境和模型生态上走了不同的路。深入对比两种架构的核心差异。","2026-05-01",[59,23,60],1679,{"slug":197,"title":198,"description":199,"pub_date":193,"tags":200,"draft":15,"word_count":205},"cpp-random-design-patterns","C++ 设计模式实战：RAII、观察者、工厂","用现代 C++（C++17\u002F20）实现三种高频设计模式：RAII 资源管理、观察者模式事件系统、工厂模式插件架构。每种模式给出问题场景、实现代码和真实工程案例。",[201,202,203,204],"cpp","设计模式","c++17","工程",2613,{"slug":207,"title":208,"description":209,"pub_date":193,"tags":210,"draft":15,"word_count":211},"data-structures-fundamentals","数据结构基础：从数组到红黑树","系统梳理常用数据结构的核心原理、时间复杂度和适用场景。数组、链表、栈、队列、哈希表、二叉树、堆、图，每种结构附实现要点和 C++ 代码片段。",[141,142,201,150],3004,{"slug":213,"title":214,"description":215,"pub_date":216,"tags":217,"draft":15,"word_count":218},"ai-agent-what-is","什么是 AI Agent？从 LLM 到自主执行","LLM 本身是无状态问答机，Agent 是什么让它’动’起来的？本文深入解析 Agent 的四个核心能力、ReAct 框架、工具调用原理，以及主流框架横向对比。","2026-04-30",[59,23,60],2116,{"slug":220,"title":221,"description":222,"pub_date":216,"tags":223,"draft":15,"word_count":224},"ai-agent-memory","AI Agent 的记忆系统：从上下文窗口到长期记忆","深入拆解 AI Agent 的四种记忆类型、上下文窗口压缩策略、RAG 向量检索原理，以及三种典型失败模式和工程选型建议。",[59,23,68],2052,{"slug":226,"title":227,"description":228,"pub_date":216,"tags":229,"draft":15,"word_count":233},"network-proxy-vpn-guide","代理与翻墙技术原理：从 HTTP 代理到现代协议","深入解析代理与 VPN 的本质区别，梳理从 SOCKS5 到 Shadowsocks、V2Ray\u002FXray、Hysteria2 的协议演进，以及机场订阅的技术本质。",[230,231,232],"网络","代理","协议",2148,{"slug":235,"title":236,"description":237,"pub_date":216,"tags":238,"draft":15,"word_count":151},"algorithm-binary-search","二分查找：永远写不对？记住这个模板","彻底搞清楚二分查找的边界问题：闭区间和左闭右开两套模板、三道经典 LeetCode 题目完整 C++ 实现，以及二分答案的进阶思路。",[142,239,240,201],"二分查找","leetcode",{"slug":242,"title":243,"description":244,"pub_date":216,"tags":245,"draft":15,"word_count":247},"algorithm-sliding-window","滑动窗口算法：从暴力到 O(n) 的思维跃迁","系统讲解滑动窗口算法的核心模板、适用题型，配合三道经典 LeetCode 题目的完整 C++ 实现，彻底理解双指针收缩思路。",[142,246,240,201],"滑动窗口",1943,{"slug":249,"title":250,"description":251,"pub_date":216,"tags":252,"draft":15,"word_count":255},"network-clash-config","Clash \u002F Mihomo 配置详解：规则、策略组与分流","深入解析 Clash\u002FMihomo 的核心配置结构，包括代理节点、策略组类型、规则优先级、DNS fake-ip 模式，以及一份实用的完整配置模板。",[230,253,231,254],"clash","配置",1292,{"slug":257,"title":258,"description":259,"pub_date":260,"tags":261,"draft":15,"word_count":264},"hid-hotplug","HID 设备热插拔检测：从 udev 到 node-hid","在 Linux 上用 node-hid + usb 库实现可靠的 USB HID 设备热插拔检测，踩坑记录","2026-04-28",[201,262,36,263,11],"hid","nodejs",2039,{"slug":266,"title":267,"description":268,"pub_date":269,"tags":270,"draft":15,"word_count":273},"electron-ipc-types","Electron IPC 类型安全：从 any 到完全类型化","用 TypeScript 泛型封装 Electron IPC，彻底消灭 any，preload 契约集中管理","2026-04-25",[11,103,271,272],"ipc","vue",1446,{"slug":275,"title":276,"description":277,"pub_date":278,"tags":279,"draft":15,"word_count":282},"element-plus-popover-hide","手动关闭多个 el-popover（不用 v-model:visible）","通过 ref + Reflect.get 调用 hide() 方法手动关闭 Element Plus Popover，解释 Vue3 Proxy 导致无法直接调用实例方法的原因。","2024-10-25",[272,280,281],"element-plus","vue3",1321,{"slug":284,"title":285,"description":286,"pub_date":287,"tags":288,"draft":15,"word_count":292},"vite-vue3-ts-elementplus-pinia","用 Vite+（vp）从零搭建 Vue3 + TypeScript + Element Plus + Pinia + Vue Router","使用 Vite+ 统一工具链（vp）一条命令搭建 Vue3 全家桶，涵盖按需导入、Pinia store、路由配置，以及常见坑的解决方案。","2024-08-27",[272,289,103,280,290,291],"vite","pinia","vite-plus",1960,{"slug":294,"title":295,"description":296,"pub_date":297,"tags":298,"draft":15,"word_count":302},"cef-lnk2038-iterator-debug-level","CEF LNK2038：解决 _ITERATOR_DEBUG_LEVEL 不匹配错误","分析 CEF（Chromium Embedded Framework）集成时出现的 LNK2038 _ITERATOR_DEBUG_LEVEL 链接错误，从根本原因到解决方案的完整指南。","2024-05-07",[201,299,300,301],"CEF","Visual Studio","链接错误",1509,{"slug":4,"title":5,"description":6,"pub_date":9,"tags":304,"draft":15,"word_count":305},[11,12,13,14],1494,{"slug":307,"title":308,"description":309,"pub_date":310,"tags":311,"draft":15,"word_count":313},"git-out-of-memory","解决 git 报错：Fatal: Out of memory, malloc failed","分析 git 大仓库操作时出现 Out of memory malloc failed 的根本原因，通过调整 pack.windowMemory、http.postBuffer 和 git repack 彻底解决。","2024-01-31",[75,36,312],"工具",2244,{"slug":315,"title":316,"description":317,"pub_date":318,"tags":319,"draft":15,"word_count":323},"vmware-tools-install","在 VMware 虚拟机中安装 open-vm-tools 完整指南","详解 VMware Tools 的作用、open-vm-tools 与官方 VMware Tools 的区别，以及在 Ubuntu 虚拟机中安装并生效的完整步骤和常见问题排查。","2023-11-21",[320,36,321,322],"VMware","Ubuntu","虚拟机",2523,{"slug":325,"title":326,"description":327,"pub_date":328,"tags":329,"draft":15,"word_count":334},"load-balancing-algorithms","负载均衡算法完全指南：从轮询到一致性哈希","系统梳理静态与动态负载均衡算法，涵盖轮询、随机、权重、IP Hash、一致性 Hash、最少连接、最快响应等，并对比 Nginx、Dubbo、Spring Cloud LoadBalancer 的实现差异。","2023-11-15",[330,331,332,333],"分布式","负载均衡","Nginx","微服务",1764,{"slug":336,"title":337,"description":338,"pub_date":339,"tags":340,"draft":15,"word_count":344},"win-cw2a-ca2w","ATL 字符串转换：CW2A 与 CA2W 完全指南","详解 ATL 宏 CW2A\u002FCA2W 在 Unicode 与 ANSI 之间的字符串转换用法、头文件依赖、USES_CONVERSION 宏的作用与常见陷阱。","2023-06-09",[201,341,342,343],"windows","ATL","字符串",1665,{"slug":346,"title":347,"description":348,"pub_date":339,"tags":349,"draft":15,"word_count":353},"csharp-sendmessage-cpp","C# 通过 SendMessage 向 C++ 窗口发送消息与字符串","使用 P\u002FInvoke 调用 user32.dll 的 SendMessage，从 C# 发送自定义 WM_USER 消息及字符串指针给 C++ 原生窗口，并在 C++ 侧正确接收和转换。",[350,201,341,351,352],"C#","互操作","PInvoke",1554,{"slug":355,"title":356,"description":357,"pub_date":358,"tags":359,"draft":15,"word_count":361},"win-postmessage-vector","Windows PostMessage 跨线程传递 std::vector 指针","通过 PostMessage 在 Windows 消息队列中传递 std::vector 指针，使用 reinterpret_cast 将指针装入 LPARAM，并在接收方正确释放内存。","2023-05-26",[201,341,360],"WinAPI",1823,{"slug":363,"title":364,"description":365,"pub_date":358,"tags":366,"draft":15,"word_count":367},"exe-dll-single-package","将 EXE 和 DLL 打包成单一可执行文件","介绍两种将 exe 和依赖 dll 打包成单文件的方案：Enigma Virtual Box 和 WinRAR 自解压，适合发布 Windows 桌面程序时简化分发流程。",[341,201,312],1619,{"slug":369,"title":370,"description":371,"pub_date":358,"tags":372,"draft":15,"word_count":375},"cpp-random-mt19937","C++ 现代随机数生成：用 mt19937 彻底告别 rand()","深入讲解为什么 rand() 不够用，以及如何用 C++11 的 \u003Crandom> 库正确生成高质量随机数，涵盖 mt19937、各种分布和线程安全。",[201,373,374],"c++11","random",1549,{"slug":377,"title":378,"description":379,"pub_date":380,"tags":381,"draft":15,"word_count":383},"win-startup-registry","C++ 实现程序开机自启动：注册表方式详解","通过操作 Windows 注册表 Run 键实现程序开机自启动，包括 HKCU 与 HKLM 区别、完整封装代码、工作目录问题和 UAC 权限处理。","2022-12-26",[341,201,382],"registry",1201,{"slug":385,"title":386,"description":387,"pub_date":388,"tags":389,"draft":15,"word_count":391},"mfc-cstring-wparam","MFC 中 CString 与 WPARAM 之间的转换","详解 MFC 消息传递中 CString 无法直接强转为 WPARAM 的原因，以及两种正确的转换方案，并介绍结构体指针传递的正确姿势。","2022-11-25",[390,201,341],"mfc",1546,{"slug":393,"title":394,"description":395,"pub_date":396,"tags":397,"draft":15,"word_count":399},"duilib-static-build","正确编译 Duilib 静态库：避免 ATL 依赖和链接错误","详解如何用 DuiLib_Static.vcxproj 编译 Duilib 静态库，解决 VARIANT 未定义、Unicode 配置不匹配和 ATL 依赖等常见问题。","2022-08-24",[201,398,341,390],"duilib",2639,{"slug":401,"title":402,"description":403,"pub_date":404,"tags":405,"draft":15,"word_count":407},"mfc-dpi-adaptive","MFC 界面自适应不同分辨率","MFC 对话框程序实现控件和字体随分辨率自动缩放的完整方案，附 DPI Awareness 配置说明","2022-08-17",[390,201,341,406],"dpi",1414,{"slug":409,"title":410,"description":411,"pub_date":412,"tags":413,"draft":15,"word_count":414},"mfc-drag-window","MFC 无标题栏窗口客户区拖动：三种方法对比","MFC 对话框去掉标题栏后如何实现拖动移动窗口，三种方案完整实现与适用场景分析","2022-08-16",[390,201,341],1633,{"slug":416,"title":417,"description":418,"pub_date":419,"tags":420,"draft":15,"word_count":422},"algorithm-number-complement","整数的补数：位运算掩码解法","LeetCode 476 题，用掩码 XOR 实现整数补数，附 C++\u002FPython\u002FJava 三种实现及补数与补码的区别","2021-03-08",[142,421,240],"位运算",1374,[]]