Docs + DX: zero-runtime-first positioning and scopeId collision guardrails (P3.5.1, P3.5.2)#102
Merged
dbanksdesign merged 2 commits intoJun 17, 2026
Conversation
…P3.5.1, P3.5.2) Restructure docs to lead with build extraction as the primary production story, and add dev-mode warnings for unscoped namespace collisions. P3.5.1 — Getting-started now installs the Vite plugin by default, shows the convention entry setup, and explains the dev/prod split. Landing page hero uses createTypeStyles with scopeId. Navigation promotes zero-runtime and Vite plugin into the Getting Started section. Next steps table leads with zero-runtime extraction. P3.5.2 — warnUnscopedCollision() in registry.ts emits a one-time console.warn when styles.component() registers the same namespace twice without a scopeId. Best-practices adds a scope isolation section with guidance for apps, packages, and per-file isolation. Component-library guide now requires scopeId for published packages. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Merged
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.
Summary
console.warnwhenstyles.component()registers the same namespace twice without ascopeId. Documents scope isolation best practices for apps, published packages, and per-file isolation.Docs changes (P3.5.1)
@typestyles/viteby default, shows Vite plugin setup and convention entry before the first style example, explains the dev/prod runtime splitcreateTypeStyles({ scopeId }), benefit card chore: version packages #3 rewritten from "lean output" to "static CSS in production"fileScopeIdscopeIdsection for published packagesCode changes (P3.5.2)
registry.ts: NewwarnUnscopedCollision()emits once per namespace when the same unscoped namespace is registered more than oncecomponent.ts: CallswarnUnscopedCollisioninclaimComponentNamespacewhen noscopeIdis setTest plan
pnpm --filter typestyles test— 334 tests pass (including 3 new)pnpm --filter typestyles typecheck— clean🤖 Generated with Claude Code