What issue are you seeing?
Installing the latest Codext release on Windows succeeds, but the CLI immediately fails to start because the required Windows platform package is missing.
Environment
OS: Windows 10 Pro 22H2
Node.js: v24.13.0
npm: 10.9.8 and 11.13.0
Package: @loongphy/codext
Version: 0.141.0-811b278
What steps can reproduce the bug?
npm install -g @loongphy/codext
codext --version
Actual Result
Error: Missing optional dependency @loongphy/codext-win32-x64. Reinstall Codext: npm install -g @loongphy/codext@latest
Stack trace originates from:
bin/codex.js:96
Investigation
The published package contains:
"optionalDependencies": {
"@loongphy/codext-win32-x64": "npm:@loongphy/codext@0.141.0-811b278-win32-x64"
}
However, the corresponding Windows package version does not appear to exist in npm.
Available versions include:
0.138.0-898cfa8-win32-x64
but for the current release only:
0.141.0-811b278
0.141.0-811b278-darwin-arm64
0.141.0-811b278-darwin-x64
No matching:
0.141.0-811b278-win32-x64
is published.
As a result, installation succeeds but runtime fails because require.resolve("@loongphy/codext-win32-x64/package.json") cannot find the package.
What is the expected behavior?
Either:
Publish 0.141.0-811b278-win32-x64, or
Do not publish the main package version until all platform packages are available, or
Fail installation with a clear error instead of failing at runtime.
Additional information
No response
What issue are you seeing?
Installing the latest Codext release on Windows succeeds, but the CLI immediately fails to start because the required Windows platform package is missing.
Environment
OS: Windows 10 Pro 22H2
Node.js: v24.13.0
npm: 10.9.8 and 11.13.0
Package: @loongphy/codext
Version: 0.141.0-811b278
What steps can reproduce the bug?
npm install -g @loongphy/codext
codext --version
Actual Result
Error: Missing optional dependency @loongphy/codext-win32-x64. Reinstall Codext: npm install -g @loongphy/codext@latest
Stack trace originates from:
bin/codex.js:96
Investigation
The published package contains:
"optionalDependencies": {
"@loongphy/codext-win32-x64": "npm:@loongphy/codext@0.141.0-811b278-win32-x64"
}
However, the corresponding Windows package version does not appear to exist in npm.
Available versions include:
0.138.0-898cfa8-win32-x64
but for the current release only:
0.141.0-811b278
0.141.0-811b278-darwin-arm64
0.141.0-811b278-darwin-x64
No matching:
0.141.0-811b278-win32-x64
is published.
As a result, installation succeeds but runtime fails because require.resolve("@loongphy/codext-win32-x64/package.json") cannot find the package.
What is the expected behavior?
Either:
Publish 0.141.0-811b278-win32-x64, or
Do not publish the main package version until all platform packages are available, or
Fail installation with a clear error instead of failing at runtime.
Additional information
No response