mometa Bug: pnpm install 出错

bug4

我试过 node v14 和v16都一样的出错，无法安装。 pnpm 7.17.0。 win 10

Dec 08 '22 10:12 qew4

+1

Jan 13 '23 06:01 HongxuanG

+1

Jan 29 '23 05:01 erhulee

信我已经收到谢谢你！

Jan 29 '23 05:01 qew4

+1

Feb 19 '23 13:02 xbx12138

+1

May 24 '23 07:05 FleeLight

信我已经收到谢谢你！

May 24 '23 07:05 qew4

怎么解决的

Jun 08 '23 03:06 bianningtao

信我已经收到谢谢你！

Jun 08 '23 03:06 qew4

我没有解决。这个项目根本不能用！

------------------ 原始邮件 ------------------ 发件人: @.>; 发送时间: 2023年6月8日(星期四) 中午11:28 收件人: @.>; 抄送: @.>; @.>; 主题: Re: [imcuttle/mometa] Bug: pnpm install 出错 (Issue #45)

怎么解决的

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

Jun 09 '23 01:06 qew4

好啊吧

| | ab2961513324 | | @.*** |

---- 回复的原邮件 ---- | 发件人 | @.> | | 日期 | 2023年06月09日 09:31 | | 收件人 | @.> | | 抄送至 | @.>@.> | | 主题 | Re: [imcuttle/mometa] Bug: pnpm install 出错 (Issue #45) |

我没有解决。这个项目根本不能用！

------------------ 原始邮件 ------------------ 发件人: @.>; 发送时间: 2023年6月8日(星期四) 中午11:28 收件人: @.>; 抄送: @.>; @.>; 主题: Re: [imcuttle/mometa] Bug: pnpm install 出错 (Issue #45)

怎么解决的

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

Jun 09 '23 02:06 bianningtao

可惜了一个好项目, pnpm install后报错了. │ [build:runtime] > @mometa/[email protected] node │ [build:runtime] > MOMETA_LOCAL=true NODE_OPTIONS="--loader ts-node/esm -r tsconfig-paths/register" node scripts/build.js │ [build:runtime] │ [build:runtime] (node:55555) ExperimentalWarning: Custom ESM Loaders is an experimental feature and might change at any time │ [build:runtime] (Use node --trace-warnings ... to show where the warning was created) │ [build:app ] (node:55563) ExperimentalWarning: Custom ESM Loaders is an experimental feature and might change at any time │ [build:app ] (Use node --trace-warnings ... to show where the warning was created) │ [build:runtime] Error [ERR_LOADER_CHAIN_INCOMPLETE]: "ts-node/esm 'resolve'" did not call the next hook in its chain and did not explicitly signal a short circuit. If this is intentional, include shortCircuit: true in the hook's return. │ [build:runtime] at new NodeError (node:internal/errors:405:5) │ [build:runtime] at ESMLoader.resolve (node:internal/modules/esm/loader:843:13) │ [build:runtime] at async ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:7) { │ [build:runtime] code: 'ERR_LOADER_CHAIN_INCOMPLETE' │ [build:runtime] } │ [build:app ] Error [ERR_LOADER_CHAIN_INCOMPLETE]: "ts-node/esm 'resolve'" did not call the next hook in its chain and did not explicitly signal a short circuit. If this is intentional, include shortCircuit: true in the hook's return. │ [build:app ] at new NodeError (node:internal/errors:405:5) │ [build:app ] at ESMLoader.resolve (node:internal/modules/esm/loader:843:13) │ [build:app ] at async ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:7) { │ [build:app ] code: 'ERR_LOADER_CHAIN_INCOMPLETE' │ [build:app ] }