chore: rename npm scope @silk-effect to @silk-lang - #270
Merged
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
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.
What
Renames the npm scope from
@silk-effectto@silk-lang(already owned on npm) across the whole repo: package names, workspace dependencies, imports, turbo task ids, changesets, docs, launch config, and the lockfile.Also updated names mechanically derived from package names:
pnpm packtarball prefixes inrelease-candidate/validate.test.ts(silk-effect-*→silk-lang-*)examples/tiny-language/README.mdsilk-effect→silk-lang)Deliberately left as-is
github.com/julia-script/silk...) — repo identity, not the npm scopeproducer: "silk-effect"inpackages/llvm/src/Bitcode.ts, bootstrap shim comments, cache/tmpdir prefixes) — these are baked into binary.bc.hexgolden fixtures; renaming them would churn fixtures for no packaging benefitpackages/vscodemarketplacepublisher: "silk-effect"— separate marketplace identityNotes for review
packages/compiler-cli/src/Workflow.tscontains literal NUL bytes (committed on main), so text tools treating it as binary can silently skip it — it was patched with a binary-safe replace and verified byte-identical to HEAD apart from the scope strings.pnpm installclean, fullturbo run buildgreen (15/15).