chore: move to mattermix/shaders - #133
Merged
Merged
Conversation
Contributor
|
React Doctor found no new issues. 🎉 Reviewed by React Doctor for commit |
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.
Why
This finishes the Shaders rebrand. Package names and repo URLs already moved in the prior two commits, but user-facing prose (READMEs, AGENTS.md, the docs site, CLI strings) still called the library Matter.
What changes
npm scope rename
The published scope moves from
@lovo/matter*to@mattermix/shaders*, and the internal build-only scope from@matter/*to@shaders/*(the docs, docs-tests, and editor apps, none of which publish). Everypackage.json, import, changeset config, and repo URL across the monorepo was updated to match.Directory and CLI rename
packages/matter,matter-react, andmatter-clibecomepackages/shaders,shaders-react, andshaders-cli, git-tracked as renames so history follows.MatterErrorbecomesShadersErrorin the React package's error module. The CLI's published bin moves frommatter-clitoshaders-cli, and the config file it reads and writes moves frommatter.config.jsontoshaders.config.json.Docs site and package prose
Every README, AGENTS.md, the docs site title and wordmark, and the MDX guides now say Shaders instead of Matter. The CLI's default
componentsDirmoves fromsrc/components/mattertosrc/components/shaders, with the docs examples, tests, and the smoke test updated to match.Stale reference cleanup
apps/docs/content/docs/reference/matter.mdxis nowshaders.mdx, since its route shouldn't carry the old brand either. The rename changed a heading's slug (@lovo/matter/colorbecame@mattermix/shaders/color), so the color guide's anchor link needed a matching update, computed from github-slugger's rules rather than guessed.Dead migration notes
The engine and React package READMEs both carried a "Migration from 0.3.x" section that called a set of deprecated aliases,
MatterScene,MatterMonitor,MatterScheduler, and others, "still work, remove at your leisure before 0.5.0." None of those aliases exist anywhere in the current source, and the stated deadline passed several versions ago, so the sections were pure noise. Removed rather than rebranded.Leftover identifiers
A few internal-only names survived the prior identifier pass and are now
Shaders-flavored too:__MATTER_EXPORT_NAME, the shader-monitor'sdata-testid="matter-monitor",__matterTestReadyin the visual-test harness,MATTER_E2Ein the poster e2e test, and the code emitter'ssortedMatterlocals.Known limitations
Two "Matter" references stay on purpose: the fake
@matter-internal/libimport alias used only to test the CLI's import rewriter, and Linear's actual team name indocs/agents/issue-tracker.md, which this branch doesn't control. PackageCHANGELOG.mdfiles and.changeset/entries keep the old brand until the follow-up PR.