refactor(ranview): publish under the @alixex scope - #410
Merged
Merged
Conversation
`@chaxus/ranview` → `@alixex/ranview`. The scope is empty on npm, so the name is free. The directory stays `packages/ranview`, so `packages/manifest.json` and `bin/verify-packages.mjs` — which match on directory names — need no change, and `pnpm -F ranview` still resolves. `test/readme.test.ts` gives up the last hard-coded copy of the name. It was already reading the specifier from package.json for its parser, after that regex silently matched nothing across an earlier rename; the assertion message still spelled the package out, which is the same drift one line later. It asks the package what it is called now, and the only remaining mention is a comment recording why. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019pjSL6jGCw2wmBLhCAW35d
Deploying ran with
|
| Latest commit: |
5c8c455
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://b41b9c8d.ran-4ty.pages.dev |
| Branch Preview URL: | https://refactor-scope-alixex.ran-4ty.pages.dev |
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.
@chaxus/ranview→@alixex/ranview. The scope is empty on npm, so the name is free.Scope of the change
The directory stays
packages/ranview, sopackages/manifest.jsonandbin/verify-packages.mjs— which match on directory names — need no change, andpnpm -F ranviewstill resolves (pnpm matches the unscoped half of a scoped name).Ten files: the package manifest and README, ranui's dependency, its re-export shim and three deep imports, the lockfile, and the README guard.
The guard gave up its last hard-coded name
test/readme.test.tsparses the README forimport … from '<pkg>'and checks every name against the real exports. It had the specifier baked into its regex — so after an earlier rename it matched nothing, verified an empty set, and passed. Only the "names enough imports to be worth checking" assertion noticed.That was fixed by reading the specifier from
package.json, but the assertion message one line later still spelled the package out, which is the same drift waiting to happen. The test asks the package what it is called now; the only remaining mention is a comment recording why.Verification
3,145 tests,
tscacross 8 packages,verify:designacross 3, prettier, the dead-link check, and aranuirebuild — the ES build externalises this dependency by name, so a rename that skips the rebuild leaves stale bundles importing the old one.🤖 Generated with Claude Code
https://claude.ai/code/session_019pjSL6jGCw2wmBLhCAW35d