chore(release): 0.39.1#664
Merged
Merged
Conversation
Hotfix for 0.39.0 install failure: the `postinstall: patch-package` hook + missing `patch-package` runtime dep + missing `patches/` in the files array meant fresh `npm install` / `npx reasonix@latest` runs crashed before the binary was usable. 0.39.0 has been deprecated on npm and `latest` rolled back to 0.38.0. Removes the patch-package machinery entirely — it can't work for a published library since npm hoists `ink` out of reasonix's own `node_modules`. The ink alt-screen render fix (#639) will return via a forked ink + `npm:` alias (#663) in a later release. Piggybacks three PRs that landed since 0.39.0: - #632 fix(web): actionable web_search / web_fetch errors - #661 feat(composer): Ctrl+X opens \$EDITOR - #662 feat(composer): Ctrl+P / Ctrl+N picker navigation
ChasLui
pushed a commit
to ChasLui/DeepSeek-Reasonix
that referenced
this pull request
May 23, 2026
Hotfix for 0.39.0 install failure: the `postinstall: patch-package` hook + missing `patch-package` runtime dep + missing `patches/` in the files array meant fresh `npm install` / `npx reasonix@latest` runs crashed before the binary was usable. 0.39.0 has been deprecated on npm and `latest` rolled back to 0.38.0. Removes the patch-package machinery entirely — it can't work for a published library since npm hoists `ink` out of reasonix's own `node_modules`. The ink alt-screen render fix (esengine#639) will return via a forked ink + `npm:` alias (esengine#663) in a later release. Piggybacks three PRs that landed since 0.39.0: - esengine#632 fix(web): actionable web_search / web_fetch errors - esengine#661 feat(composer): Ctrl+X opens \$EDITOR - esengine#662 feat(composer): Ctrl+P / Ctrl+N picker navigation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Hotfix for 0.39.0 install regression that broke fresh
npm install/npx reasonix@latestfor every user. 0.39.0 has been deprecated on npm andlatestdist-tag rolled back to 0.38.0 — this PR ships the replacement.Root cause (0.39.0)
package.jsonadded"postinstall": "patch-package"to apply an ink alt-screen render patch for #639. But:patch-packagewas indevDependenciesonly, so it didn't ship to end-users —'patch-package' is not recognized as an internal or external command.patches/was missing from thefilesarray, so the patch wasn't even in the published tarball.patch-packageis designed for consumer projects to patch their own deps — it looks at./node_modules/<dep>, but npm hoistsinkto the consumer's top-levelnode_modules/ink, wherepatch-packagerunning from insidenode_modules/reasonix/can't find it. Even if (1) and (2) had been fixed, the patch would never have applied.Fix
Remove the entire patch-package machinery:
postinstallscript,patches/directory, and thepatch-packagedependency. The ink alt-screen fix (#639) returns via a forked ink +npm:alias in a later release — tracked at #663. Until then alt-screen ghosting on CJK terminals matches 0.38.0 behavior (i.e., still present but not regressed).Piggyback changes
Three PRs that were in flight land in 0.39.1:
— try: ...tails)$EDITORwith the current inputTest plan
npm run verify— 2616 tests pass on the rebased branchnpm pack— verified tarball has nopatches/, nopostinstall, nopatch-packagein deps/devDepsnpm install ./reasonix-0.39.1.tgzinto a fresh empty dir succeeds (added 101 packages in 9s, no postinstall warnings)reasonix --version→0.39.1reasonix --helprenders all commandsreasonix doctor --json→ 9/9 okPost-merge
v0.39.1, push tagnpm publishnpm dist-tag add reasonix@0.39.1 latest