Skip to content

chore: rename npm scope @silk-effect to @silk-lang - #270

Merged
julia-script merged 2 commits into
mainfrom
julia/rename-silk-effect-scope-5d7e8c
Aug 27, 2026
Merged

chore: rename npm scope @silk-effect to @silk-lang#270
julia-script merged 2 commits into
mainfrom
julia/rename-silk-effect-scope-5d7e8c

Conversation

@julia-script

Copy link
Copy Markdown
Owner

What

Renames the npm scope from @silk-effect to @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 pack tarball prefixes in release-candidate/validate.test.ts (silk-effect-*silk-lang-*)
  • the tarball path in examples/tiny-language/README.md
  • the private workspace root package name (silk-effectsilk-lang)

Deliberately left as-is

  • GitHub repo URLs (github.com/julia-script/silk...) — repo identity, not the npm scope
  • Product-identity strings (producer: "silk-effect" in packages/llvm/src/Bitcode.ts, bootstrap shim comments, cache/tmpdir prefixes) — these are baked into binary .bc.hex golden fixtures; renaming them would churn fixtures for no packaging benefit
  • packages/vscode marketplace publisher: "silk-effect" — separate marketplace identity

Notes for review

  • packages/compiler-cli/src/Workflow.ts contains 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.
  • Verified: pnpm install clean, full turbo run build green (15/15).

@julia-script
julia-script merged commit 4b3c421 into main Aug 27, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant