codex cli has been out for 5 months with 170k weekly downloads - it's definitely 'ready for primetime' if you can get past your bug. I don't have that issue.
Re:GPT-5-Codex
by king_magic on Tuesday September 16, 2025 @03:36AM
(#45259196)
The install errors out after following two basic install commands. This is poor code hygiene on the part of the authors. That's "not ready for primetime" in my book.
npm ERR! code 1
npm ERR! path /usr/local/lib/node_modules/@openai/codex/node_modules/@vscode/ripgrep
npm ERR! command failed
npm ERR! command sh -c node ./lib/postinstall.js
npm ERR! /usr/local/lib/node_modules/@openai/codex/node_modules/@vscode/ripgrep/lib/download.js:199
npm ERR! zipFile?.close();
npm ERR! ^
npm ERR!
npm ERR! SyntaxError: Unexpected token '.'
Re:GPT-5-Codex
by SyrupThinker on Tuesday September 16, 2025 @06:06AM
(#45260252)
Please tell me you are not running a NodeJS release that hasn't been supported for at least 3 years...
Optional chaining was added in v14 (2020), and it sure looks like that is the issue here.
Re:GPT-5-Codex
by king_magic on Tuesday September 16, 2025 @12:48PM
(#45264695)
Brand new, clean install of npm.
Poor code + doc hygiene is the problem here.
The question is which version of node, not npm.
Re:GPT-5-Codex
by king_magic on Wednesday September 17, 2025 @04:07PM
(#45280762)
[delayed]
It does matter.
Re:GPT-5-Codex
by king_magic on Monday September 22, 2025 @04:56AM
(#45330774)
Why yes, you're right, poor code hygiene and poor documentation hygiene does matter. We finally agree.
npm ERR! code 1 npm ERR! path /usr/local/lib/node_modules/@openai/codex/node_modules/@vscode/ripgrep npm ERR! command failed npm ERR! command sh -c node ./lib/postinstall.js npm ERR! /usr/local/lib/node_modules/@openai/codex/node_modules/@vscode/ripgrep/lib/download.js:199 npm ERR! zipFile?.close();