npm run dev 报错:fatal - Error: Parse config file failed: [/Users/xxx/Desktop/projects/xxx/.umirc.ts]

[liaodalin19903]

运行npm run dev的时候报错:

$ pnpm run dev

> @ dev /Users/xxx/Desktop/projects/xxx
> max dev

fatal - Error: Parse config file failed: [/Users/xxx/Desktop/projects/xxx/.umirc.ts]
    at Function.getUserConfig (/Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/@[email protected]/node_modules/@umijs/core/dist/config/config.js:161:17)
    at Config.getUserConfig (/Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/@[email protected]/node_modules/@umijs/core/dist/config/config.js:58:19)
    at Service.run (/Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/@[email protected]/node_modules/@umijs/core/dist/service/service.js:231:37)
    at Service.run2 (/Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/[email protected]_4igwsy37cad63ltlhziorzny2q/node_modules/umi/dist/service/service.js:65:23)
    at /Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/[email protected]_4igwsy37cad63ltlhziorzny2q/node_modules/umi/dist/cli/forkedDev.js:24:19
    at Object.<anonymous> (/Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/[email protected]_4igwsy37cad63ltlhziorzny2q/node_modules/umi/dist/cli/forkedDev.js:37:3)
    at Module._compile (node:internal/modules/cjs/loader:1155:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1209:10)
    at Module.load (node:internal/modules/cjs/loader:1033:32)
    at Function.Module._load (node:internal/modules/cjs/loader:868:12) {
  [cause]: Error: Parse file failed: [/Users/xxx/Desktop/projects/xxx/.umirc.ts]
      at transform (/Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/@[email protected]/node_modules/@umijs/utils/dist/register.js:49:11)
      at revert.ext (/Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/@[email protected]/node_modules/@umijs/utils/dist/register.js:55:62)
      at Module._compile (/Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/@[email protected]/node_modules/@umijs/utils/compiled/pirates/index.js:1:1609)
      at Module._extensions..js (node:internal/modules/cjs/loader:1209:10)
      at Object.newLoader [as .ts] (/Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/@[email protected]/node_modules/@umijs/utils/compiled/pirates/index.js:1:1684)
      at Module.load (node:internal/modules/cjs/loader:1033:32)
      at Function.Module._load (node:internal/modules/cjs/loader:868:12)
      at Module.require (node:internal/modules/cjs/loader:1057:19)
      at require (node:internal/modules/cjs/helpers:103:18)
      at Function.getUserConfig (/Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/@[email protected]/node_modules/@umijs/core/dist/config/config.js:156:54) {
    [cause]: Error: 
    You installed esbuild for another platform than the one you're currently using.
    This won't work because esbuild is written with native code and needs to
    install a platform-specific binary executable.
    
    Specifically the "@esbuild/darwin-x64" package is present but this platform
    needs the "@esbuild/darwin-arm64" package instead. People often get into this
    situation by installing esbuild with npm running inside of Rosetta 2 and then
    trying to use it with node running outside of Rosetta 2, or vice versa (Rosetta
    2 is Apple's on-the-fly x86_64-to-arm64 translation service).
    
    If you are installing with npm, you can try ensuring that both npm and node are
    not running under Rosetta 2 and then reinstalling esbuild. This likely involves
    changing how you installed npm and/or node. For example, installing node with
    the universal installer here should work: https://nodejs.org/en/download/. Or
    you could consider using yarn instead of npm which has built-in support for
    installing a package on multiple platforms simultaneously.
    
    If you are installing with yarn, you can try listing both "arm64" and "x64"
    in your ".yarnrc.yml" file using the "supportedArchitectures" feature:
    https://yarnpkg.com/configuration/yarnrc/#supportedArchitectures
    Keep in mind that this means multiple copies of esbuild will be present.
    
    Another alternative is to use the "esbuild-wasm" package instead, which works
    the same way on all platforms. But it comes with a heavy performance cost and
    can sometimes be 10x slower than the "esbuild" package, so you may also not
    want to do that.
    
        at generateBinPath (/Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/[email protected]/node_modules/esbuild/lib/main.js:1841:17)
        at esbuildCommandAndArgs (/Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/[email protected]/node_modules/esbuild/lib/main.js:1922:33)
        at ensureServiceIsRunning (/Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/[email protected]/node_modules/esbuild/lib/main.js:2087:25)
        at startSyncServiceWorker (/Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/[email protected]/node_modules/esbuild/lib/main.js:2310:19)
        at Object.<anonymous> (/Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/[email protected]/node_modules/esbuild/lib/main.js:2351:3)
        at Module._compile (node:internal/modules/cjs/loader:11
mba:umimax-mark-logicmanager markleo$ pnpm run dev

> @ dev /Users/xxx/Desktop/projects/xxx
> max dev

fatal - Error: Parse config file failed: [/Users/xxx/Desktop/projects/xxx/.umirc.ts]
    at Function.getUserConfig (/Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/@[email protected]/node_modules/@umijs/core/dist/config/config.js:161:17)
    at Config.getUserConfig (/Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/@[email protected]/node_modules/@umijs/core/dist/config/config.js:58:19)
    at Service.run (/Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/@[email protected]/node_modules/@umijs/core/dist/service/service.js:231:37)
    at Service.run2 (/Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/[email protected]_4igwsy37cad63ltlhziorzny2q/node_modules/umi/dist/service/service.js:65:23)
    at /Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/[email protected]_4igwsy37cad63ltlhziorzny2q/node_modules/umi/dist/cli/forkedDev.js:24:19
    at Object.<anonymous> (/Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/[email protected]_4igwsy37cad63ltlhziorzny2q/node_modules/umi/dist/cli/forkedDev.js:37:3)
    at Module._compile (node:internal/modules/cjs/loader:1155:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1209:10)
    at Module.load (node:internal/modules/cjs/loader:1033:32)
    at Function.Module._load (node:internal/modules/cjs/loader:868:12) {
  [cause]: Error: Parse file failed: [/Users/xxx/Desktop/projects/xxx/.umirc.ts]
      at transform (/Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/@[email protected]/node_modules/@umijs/utils/dist/register.js:49:11)
      at revert.ext (/Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/@[email protected]/node_modules/@umijs/utils/dist/register.js:55:62)
      at Module._compile (/Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/@[email protected]/node_modules/@umijs/utils/compiled/pirates/index.js:1:1609)
      at Module._extensions..js (node:internal/modules/cjs/loader:1209:10)
      at Object.newLoader [as .ts] (/Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/@[email protected]/node_modules/@umijs/utils/compiled/pirates/index.js:1:1684)
      at Module.load (node:internal/modules/cjs/loader:1033:32)
      at Function.Module._load (node:internal/modules/cjs/loader:868:12)
      at Module.require (node:internal/modules/cjs/loader:1057:19)
      at require (node:internal/modules/cjs/helpers:103:18)
      at Function.getUserConfig (/Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/@[email protected]/node_modules/@umijs/core/dist/config/config.js:156:54) {
    [cause]: Error: 
    You installed esbuild for another platform than the one you're currently using.
    This won't work because esbuild is written with native code and needs to
    install a platform-specific binary executable.
    
    Specifically the "@esbuild/darwin-x64" package is present but this platform
    needs the "@esbuild/darwin-arm64" package instead. People often get into this
    situation by installing esbuild with npm running inside of Rosetta 2 and then
    trying to use it with node running outside of Rosetta 2, or vice versa (Rosetta
    2 is Apple's on-the-fly x86_64-to-arm64 translation service).
    
    If you are installing with npm, you can try ensuring that both npm and node are
    not running under Rosetta 2 and then reinstalling esbuild. This likely involves
    changing how you installed npm and/or node. For example, installing node with
    the universal installer here should work: https://nodejs.org/en/download/. Or
    you could consider using yarn instead of npm which has built-in support for
    installing a package on multiple platforms simultaneously.
    
    If you are installing with yarn, you can try listing both "arm64" and "x64"
    in your ".yarnrc.yml" file using the "supportedArchitectures" feature:
    https://yarnpkg.com/configuration/yarnrc/#supportedArchitectures
    Keep in mind that this means multiple copies of esbuild will be present.
    
    Another alternative is to use the "esbuild-wasm" package instead, which works
    the same way on all platforms. But it comes with a heavy performance cost and
    can sometimes be 10x slower than the "esbuild" package, so you may also not
    want to do that.
    
        at generateBinPath (/Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/[email protected]/node_modules/esbuild/lib/main.js:1841:17)
        at esbuildCommandAndArgs (/Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/[email protected]/node_modules/esbuild/lib/main.js:1922:33)
        at ensureServiceIsRunning (/Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/[email protected]/node_modules/esbuild/lib/main.js:2087:25)
        at startSyncServiceWorker (/Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/[email protected]/node_modules/esbuild/lib/main.js:2310:19)
        at Object.<anonymous> (/Users/xxx/Desktop/projects/xxx/node_modules/.pnpm/[email protected]/node_modules/esbuild/lib/main.js:2351:3)
        at Module._compile (node:internal/modules/cjs/loader:1155:14)
        at Object.Module._extensions..js (node:internal/modules/cjs/loader:1209:10)
        at Module.load (node:internal/modules/cjs/loader:1033:32)
        at Function.Module._load (node:internal/modules/cjs/loader:868:12)
        at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
  }
}
fatal - A complete log of this run can be found in:
fatal - /Users/xxx/Desktop/projects/xxx/node_modules/.cache/logger/umi.log
fatal - Consider reporting a GitHub issue on https://github.com/umijs/umi/issues
mba:umimax-mark-logicmanager markleo$ 

---

.umirc.ts配置文件如下：

import { defineConfig } from '@umijs/max';

export default defineConfig({
  antd: {},
  access: {},
  model: {},
  initialState: {},
  request: {},
  layout: {
    title: '@umijs/max',
  },
  routes: [
    {
      path: '/',
      redirect: '/home',
    },
    {
      name: '首页',
      path: '/home',
      component: './Home',
    },
    {
      name: '权限演示',
      path: '/access',
      component: './Access',
    },
    {
        name: ' CRUD 示例',
        path: '/table',
        component: './Table',
    },
  ],
  npmClient: 'pnpm'
});

[liaodalin19903]

已解决，清除npm缓存，删除node_modules，使用cnpm重新安装即可。

[shaimaHamila]

I keep encountering this error almost daily, and having to clear the npm cache, delete node_modules, and reinstall everything is getting really frustrating—and it doesn't always work. Is there a more permanent solution or something else I could try to prevent this from happening so frequently?