Skip to content

Fix Windows npm install regression from dist-tag packaging change#11768

Open
etraut-openai wants to merge 1 commit intomainfrom
etraut/fix_latest_npm
Open

Fix Windows npm install regression from dist-tag packaging change#11768
etraut-openai wants to merge 1 commit intomainfrom
etraut/fix_latest_npm

Conversation

@etraut-openai
Copy link
Collaborator

@etraut-openai etraut-openai commented Feb 13, 2026

The recent packaging migration in #11339 switched platform artifacts to be published as @openai/codex with platform-specific versions and wired the meta package via npm alias optional dependencies (for example @openai/codex-win32-x64 -> npm:@openai/codex@0.101.0-win32-x64).

This caused runtime failures on Windows where codex reports: Missing optional dependency @openai/codex-win32-x64.

What changed

  • Updated codex-cli/scripts/build_npm_package.py to publish platform artifacts under their concrete package names:
    • @openai/codex-win32-x64
    • @openai/codex-win32-arm64
    • @openai/codex-linux-x64
    • @openai/codex-linux-arm64
    • @openai/codex-darwin-x64
    • @openai/codex-darwin-arm64
  • Updated meta package optionalDependencies to use plain version references (e.g. 0.101.0-win32-x64) instead of npm alias syntax to @openai/codex.
  • Updated codex-cli/scripts/README.md to reflect that platform-native artifacts are separate optional dependency packages.

Why

bin/codex.js resolves platform packages by name (@openai/codex-win32-x64, etc). Publishing platform tarballs under @openai/codex introduces alias indirection that can fail to materialize these package names at install time, especially on Windows. Publishing under the concrete names restores direct name alignment and reliable resolution.

Addresses #11744

The recent packaging migration in #11339 switched platform artifacts to be published as `@openai/codex` with platform-specific versions and wired the meta package via npm alias optional dependencies (for example `@openai/codex-win32-x64 -> npm:@openai/codex@0.101.0-win32-x64`).

This caused runtime failures on Windows where `codex` reports:
`Missing optional dependency @openai/codex-win32-x64`.

### What changed
- Updated `codex-cli/scripts/build_npm_package.py` to publish platform artifacts under their concrete package names:
  - `@openai/codex-win32-x64`
  - `@openai/codex-win32-arm64`
  - `@openai/codex-linux-x64`
  - `@openai/codex-linux-arm64`
  - `@openai/codex-darwin-x64`
  - `@openai/codex-darwin-arm64`
- Updated meta package `optionalDependencies` to use plain version references (e.g. `0.101.0-win32-x64`) instead of npm alias syntax to `@openai/codex`.
- Updated `codex-cli/scripts/README.md` to reflect that platform-native artifacts are separate optional dependency packages.

### Why
`bin/codex.js` resolves platform packages by name (`@openai/codex-win32-x64`, etc). Publishing platform tarballs under `@openai/codex` introduces alias indirection that can fail to materialize these package names at install time, especially on Windows. Publishing under the concrete names restores direct name alignment and reliable resolution.
@etraut-openai
Copy link
Collaborator Author

@codex review

@chatgpt-codex-connector
Copy link
Contributor

Codex Review: Didn't find any major issues. Swish!

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant