mirror of
https://github.com/hanzoai/dev.git
synced 2026-10-17 15:34:54 +00:00
zeekay
b31cb86dad
`codex-cli/` published `@hanzo/dev`, so the directory carrying our npm package was named after someone else's product. It is `npm/`. `patches/codex.json` is `patches/upstream.json` — it anchors edits against upstream, and the file should say so rather than name one of them. Deleted outright: `justfile`, whose first line was `set working-directory := "codex-rs"` for a directory this repository has never had; `announcement_tip.toml`, an example file for a TUI we do not ship; and `.codex/` and `.code/`, which held upstream's own process skills — babysit-pr, codex-bug, pushing-ci-changes — that were never ours. Three branding leaks a real run turned up, none of which the help text showed: `dev exec` announced "OpenAI Codex v0.7.0-dev.1" as its first line, the status card was missed when the session header was anchored, and both bubblewrap warnings said "Codex's Linux sandbox". README: say what ships. It claimed the agent drives a browser, which is the port that has not landed, and showed a screenshot of it doing so. Both are gone until the bridge is back. The model count is "hundreds" — `/v1/models` answers 458 today, an earlier line here said "over 500", and hanzo.ai derives its own count precisely because typed ones drift. Document the npm install beside the curl one; both give the same build.
15 lines
518 B
JavaScript
15 lines
518 B
JavaScript
import { test } from 'node:test';
|
|
import assert from 'node:assert/strict';
|
|
|
|
test('runPostinstall resolves in dry-run mode', async () => {
|
|
const { runPostinstall } = await import('../postinstall.js');
|
|
process.env.CODE_POSTINSTALL_DRY_RUN = '1';
|
|
try {
|
|
const result = await runPostinstall({ invokedByRuntime: true, skipGlobalAlias: true });
|
|
assert.ok(result && result.skipped === true);
|
|
} finally {
|
|
delete process.env.CODE_POSTINSTALL_DRY_RUN;
|
|
delete process.env.CODE_RUNTIME_POSTINSTALL;
|
|
}
|
|
});
|