無法運行。

[exsystem]

最新版brew安裝後，在以前從未安裝過npm的情況下根據首頁說明安裝了npm，然後
當運行 hi8命令後直接報異常了，如下：

child_process.js:430
    throw new ERR_INVALID_ARG_TYPE('options.cwd', 'string', options.cwd);
    ^

TypeError [ERR_INVALID_ARG_TYPE]: The "options.cwd" property must be of type string. Received function wrappedCwd
    at normalizeSpawnArguments (child_process.js:430:11)
    at Object.spawn (child_process.js:546:13)
    at Function.module.exports.daemon (/usr/local/lib/node_modules/hi8/node_modules/daemon/index.js:50:31)
    at module.exports (/usr/local/lib/node_modules/hi8/node_modules/daemon/index.js:25:20)
    at Object.<anonymous> (/usr/local/lib/node_modules/hi8/bin.js:8:3)
    at Module._compile (internal/modules/cjs/loader.js:1144:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1164:10)
    at Module.load (internal/modules/cjs/loader.js:993:32)
    at Function.Module._load (internal/modules/cjs/loader.js:892:14)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:71:12) {
  code: 'ERR_INVALID_ARG_TYPE'
}

[ungoldman]

I'm sorry, I cannot read Chinese!

Google translate has translated your message as follows:

After installing the latest version of brew, install npm according to the homepage instructions without installing npm before, then
When running the hi8 command, an exception is reported directly, as follows

I have not encountered this error before, but it's possible a breaking change was introduced into node:

nodejs/node@20fd123

I don't have time to investigate this week but hope this at least helps give you a clue to what the problem might be. Best of luck!

[exsystem]

好的，謝謝。

…

Nate Goldman ***@***.***> 於 2020年01月13日 10:35 寫道： I'm sorry, I cannot read Chinese! Google translate has translated your message as follows: After installing the latest version of brew, install npm according to the homepage instructions without installing npm before, then When running the hi8 command, an exception is reported directly, as follows I have not encountered this error before, but it's possible a breaking change was introduced into node: ***@***.*** <nodejs/node@20fd123> I don't have time to investigate this week but hope this at least helps give you a clue to what the problem might be. Best of luck! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#9?email_source=notifications&email_token=ACZQRMTSAGL6V4AJUMHTG4LQ5PHOLA5CNFSM4KFWIHYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIXL75Y#issuecomment-573489143>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACZQRMW2ERTMQHJXQNQM3HTQ5PHOLANCNFSM4KFWIHYA>.