7 ms·
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_mo
by king_magic 1y 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();
- drewbitt 1y agocodex 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.
- king_magic 1y agoThe 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 '.'
- SyrupThinker 1y agoPlease 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.
- king_magic 1y agoBrand new, clean install of npm. Poor code + doc hygiene is the problem here.
- hayd 1y agoThe question is which version of node, not npm.
- king_magic 1y agoIt doesn't matter. The install was broken as was written. That's poor hygiene.
- drewbitt 1y agoIt does matter.
- king_magic 1y agoWhy yes, you're right, poor code hygiene and poor documentation hygiene does matter. We finally agree.
- sleepnow 1y agothis should resolve that for you: unset GITHUB_TOKEN npm install --global @openai/codex