Start Kitchen correctly through the installed npm command - #9
Merged
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013divWd8mkNgyYGuhccAAtU
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
1 participant
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.
Running the packaged kitchen through
npm execcould exit successfully without launching: the entry-point guard compared npm's executable symlink path with the module's real file path. Resolve the executable before comparing so both direct Node invocation and the installed command start the kitchen.The clean-package check now invokes actual
npm execfor help, live repo attachment and Example launch. All 71 tests still pass locally, and the updated packed archive passes the stronger check. Bump the experimental package to alpha.2 and update release instructions; alpha.1 is marked superseded instead of replacing its published archive.