Skip to content

Support current Codex selector bundles#1

Closed
skavinski-lab wants to merge 1 commit into
Mirochill:mainfrom
skavinski-lab:fix/current-codex-bundles
Closed

Support current Codex selector bundles#1
skavinski-lab wants to merge 1 commit into
Mirochill:mainfrom
skavinski-lab:fix/current-codex-bundles

Conversation

@skavinski-lab

Copy link
Copy Markdown

Summary

  • discover hashed model-selector and React DOM assets instead of hardcoding filenames
  • add complete compatibility profiles for legacy bundles and Codex 26.707
  • map current icon, hook, predicate, and slider symbols safely and reject unknown or ambiguous bundles
  • fix the Windows PowerShell 5 default destination calculation
  • document post-update React error 130 troubleshooting

Root cause

Codex Desktop 26.707 changed both hashed asset filenames and minified identifiers. The old patch rendered Qe/tt (now JSX runtime objects) as icons and ye (now a lazy-loader cache object) as the slider, producing React error 130. The current renderable symbols are $e/nt and be.

Verification

  • npm run check (6 tests)
  • git diff --check
  • successful portable build from installed Codex 26.707.6957.0 app.asar
  • fresh application startup without React/error-boundary breadcrumbs

@skavinski-lab skavinski-lab force-pushed the fix/current-codex-bundles branch from af4fa58 to f74bd93 Compare July 13, 2026 19:29
@skavinski-lab

skavinski-lab commented Jul 13, 2026

Copy link
Copy Markdown
Author

Superseded by #2 from Eric Skavinski.

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