Upgrade smithers-orchestrator to smthrs - #1
Open
roninjin10 wants to merge 1 commit into
Open
Conversation
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.
The Smithers package was renamed on npm from
smithers-orchestratortosmthrsas of 0.33.0, with no compatibility alias — the old name no longer receives updates.This PR sweeps the repo for the old package name and updates all import specifiers in
.smithers/main.tsx(smithers-orchestrator,smithers-orchestrator/db,smithers-orchestrator/components→smthrs,smthrs/db,smthrs/components). That was the only breaking-change migration required: the rename itself.Notes:
git grep smithers-orchestratoris clean on this branch.package.jsonor lockfile exists in this repo, so there was no dependency range to bump or lockfile to regenerate;smthrs0.33.0 is confirmed published on npm.🤖 Generated with Claude Code