| HN Mirror

Y	Hacker News new \| ask \| show \| jobs


	by king_magic 269 days ago
	Doesn't seem ready for prime-time. I'll be impressed when it actually installs. 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();

2 comments

drewbitt 269 days ago

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.

link

king_magic 269 days ago

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 '.'

link

SyrupThinker 268 days ago

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.

link

king_magic 268 days ago

Brand new, clean install of npm.

Poor code + doc hygiene is the problem here.

link

hayd 268 days ago

The question is which version of node, not npm.

link