[Bug]: 新创建的 react+ts+express 项目执行 pnpm dev 报错

[donotlb]

Describe the bug

复现步骤:

pnpm create blocklet my-blocklet

cd my-blocklet
pnpm i
pnpm dev

报错如下:

> blocklet dev

ℹ Try to dev blocklet from /Users/donotlb/repos/my-blocklet

ℹ Server DID zNKsaN9y3majBrxJmvYxGH7r8F1rDPBbFPqw
ℹ Server config from /Users/donotlb/blocklet-server/dev-server2/.blocklet-server/config.yml
✔ Installing application my-blocklet... Done in 0.121s
✔ Installing Component my-blocklet@0.1.0... Done in 0.325s
✔ Component my-blocklet@0.1.0 was successfully installed





2026-01-06T17:15:47: npm warn Unknown env config "shamefully-hoist". This will stop working in the next major version of npm.
2026-01-06T17:15:47: npm warn Unknown env config "npm-globalconfig". This will stop working in the next major version of npm.
2026-01-06T17:15:47: npm warn Unknown env config "recursive". This will stop working in the next major version of npm.
2026-01-06T17:15:47: npm warn Unknown env config "verify-deps-before-run". This will stop working in the next major version of npm.
2026-01-06T17:15:47: npm warn Unknown env config "auto-install-peers". This will stop working in the next major version of npm.
2026-01-06T17:15:47: npm warn Unknown env config "_jsr-registry". This will stop working in the next major version of npm.
2026-01-06T17:15:47: npm warn Unknown project config "shamefully-hoist". This will stop working in the next major version of npm.
2026-01-06T17:15:47:
2026-01-06T17:15:47: > my-blocklet@0.1.0 start
2026-01-06T17:15:47: > cross-env NODE_ENV=development nodemon --exec tsx api/dev.ts -w api
2026-01-06T17:15:47:
2026-01-06T17:15:49: [nodemon] 3.1.11
2026-01-06T17:15:49: [nodemon] to restart at any time, enter `rs`
2026-01-06T17:15:49: [nodemon] watching path(s): api/**/*
2026-01-06T17:15:49: [nodemon] watching extensions: ts,json
2026-01-06T17:15:49: [nodemon] starting `tsx api/dev.ts`
2026-01-06T17:15:50: [dotenv-flow@4.1.0]: ".env*" files loading failed: no ".env*" files matching pattern ".env[.development][.local]" in "/Users/donotlb/repos/my-blocklet" dir undefined
2026-01-06T17:15:50: refresh connection token {
2026-01-06T17:15:50:   exp: '1767691250',
2026-01-06T17:15:50:   iat: '1767690950',
2026-01-06T17:15:50:   iss: 'did:abt:zNKiYYKqHo3v1VLFmu4xt6wYYuDokHufFWML',
2026-01-06T17:15:50:   nbf: '1767690950',
2026-01-06T17:15:50:   version: '1.0.0'
2026-01-06T17:15:50: }
2026-01-06T17:15:50: > my-blocklet v0.1.0 ready on 17069
2026-01-06T17:15:50: file:///Users/donotlb/repos/my-blocklet/node_modules/.pnpm/vite-plugin-blocklet@0.14.4_rollup@4.55.1_vite@7.3.0_@types+node@20.19.27_jiti@2.6.1_tsx@4.21.0_yaml@2.8.2_/node_modules/vite-plugin-blocklet/libs/utils.js:5
2026-01-06T17:15:50: import { fromPublicKey, isValid } from '@arcblock/did';
2026-01-06T17:15:50:          ^^^^^^^^^^^^^
2026-01-06T17:15:50: SyntaxError: The requested module '@arcblock/did' does not provide an export named 'fromPublicKey'
2026-01-06T17:15:50:     at #_instantiate (node:internal/modules/esm/module_job:254:21)
2026-01-06T17:15:50:     at async ModuleJob.run (node:internal/modules/esm/module_job:362:5)
2026-01-06T17:15:50:     at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:665:26)
2026-01-06T17:15:50:
2026-01-06T17:15:50: Node.js v24.4.1
2026-01-06T17:15:50: [nodemon] app crashed - waiting for file changes before starting...

Reproduction Steps

\

Observed Behavior

\

Expected Behavior

\

Possible Solution

No response

Additional Information/Context

No response

[donotlb]

让 claude 帮忙修复，看起来有点复杂，临时使用，仅供参考

fix-esm-packages.mjs

/* eslint-disable no-console */
import { existsSync, readFileSync, readdirSync, writeFileSync } from 'fs';
import { dirname, join } from 'path';
import { fileURLToPath } from 'url';

// eslint-disable-next-line @typescript-eslint/naming-convention
const __dirname = dirname(fileURLToPath(import.meta.url));
const nodeModulesPath = join(__dirname, '..', 'node_modules');

// Packages that need type: module added
const packagesToFix = ['@arcblock', '@ocap'];

function fixPackage(packagePath) {
  const packageJsonPath = join(packagePath, 'package.json');

  if (!existsSync(packageJsonPath)) {
    return;
  }

  try {
    const content = readFileSync(packageJsonPath, 'utf8');
    const pkg = JSON.parse(content);

    // Only add type: module if it doesn't already exist and package has ESM exports
    if (!pkg.type && pkg.exports && pkg.exports['.'] && pkg.exports['.'].import) {
      pkg.type = 'module';
      writeFileSync(packageJsonPath, `${JSON.stringify(pkg, null, 2)}\n`);
      console.log(`Fixed: ${pkg.name}`);
    }
  } catch (e) {
    // Ignore errors for individual packages
  }
}

function scanAndFix(basePath, prefix) {
  const scopePath = join(basePath, prefix);

  if (!existsSync(scopePath)) {
    return;
  }

  try {
    const packages = readdirSync(scopePath);
    for (const pkg of packages) {
      const packagePath = join(scopePath, pkg);
      fixPackage(packagePath);
    }
  } catch (e) {
    // Ignore errors
  }
}

// Fix packages in node_modules
for (const prefix of packagesToFix) {
  scanAndFix(nodeModulesPath, prefix);
}

// Also fix packages in .pnpm directory (pnpm stores packages there)
const pnpmPath = join(nodeModulesPath, '.pnpm');
if (existsSync(pnpmPath)) {
  try {
    const dirs = readdirSync(pnpmPath);
    for (const dir of dirs) {
      // Check if directory name starts with @arcblock or @ocap (encoded as @arcblock+ or @ocap+)
      if (dir.startsWith('@arcblock+') || dir.startsWith('@ocap+')) {
        const innerNodeModules = join(pnpmPath, dir, 'node_modules');
        for (const prefix of packagesToFix) {
          scanAndFix(innerNodeModules, prefix);
        }
      }
    }
  } catch (e) {
    // Ignore errors
  }
}

console.log('ESM packages fix completed');

---

discuss kit 没有此问题，让 cc 对比了下两个仓库，没发现问题,

我无法找到确切的原因，但发现了几个可能的因素：

  | 因素               | discuss-kit-lll                      | vibe-docs              |
  |--------------------|--------------------------------------|------------------------|
  | 项目结构           | Monorepo (pnpm workspace)            | 单项目                 |
  | @arcblock/did 版本 | 1.28.1                               | 1.28.2                 |
  | pnpm 存储路径      | @arcblock+did@1.28.1_encoding@0.1.13 | @arcblock+did@1.28.2   |
  | Vite 版本          | 7.0.0                                | 7.3.0 (降级后仍有问题) |

  最可能的原因：

  1. pnpm workspace 的模块解析行为不同 - 在 monorepo 中，pnpm 可能使用不同的符号链接策略
  2. peer dependency 影响 - encoding@0.1.13 后缀表明 discuss-kit-lll 的依赖树不同，这可能影响 Node.js 的模块解析顺序
  3. 缓存/安装时机 - discuss-kit-lll 的 node_modules 可能在 Node.js v24 ESM 行为变化之前安装

  无论如何，postinstall 脚本添加 type: module 是一个可靠的解决方案，因为它直接解决了 Node.js 无法正确识别 ESM 文件的根本问题。