Focused follow-up work for @knighted/develop.
-
Style isolation behavior docs
- Document ShadowRoot on/off behavior and how style isolation changes in light DOM mode.
- Clarify that light DOM preview can inherit shell styles and include recommendations for scoping.
-
Preview UX polish
- Keep tooltip affordances for mode-specific behavior.
- Continue tightening panel control alignment and spacing without introducing extra markup.
-
In-browser component/style linting
- Explore running lint checks for component and style sources directly in the playground.
- Prefer CDN-delivered tooling where possible and preserve graceful fallback behavior when unavailable.
-
In-browser component type checking
- Explore TypeScript/JSX type checking for component source in-browser using CDN-delivered tooling.
- Keep diagnostics responsive and surface clear inline/editor feedback without blocking the preview loop.
-
In-browser component testing
- Explore authoring and running component-focused tests in-browser (for example, a Vitest-compatible flow) using CDN-delivered tooling.
- Define a lightweight test UX that supports writing tests, running them on demand, and displaying results in-app.
-
App runtime modularization
- Plan a refactor that splits
src/app.jsinto scoped modules organized by functionality (for example: diagnostics, render pipeline, editor integration, UI controls, and persistence). - Preserve
src/app.jsas the main runtime orchestration entrypoint while moving implementation details into focused modules. - Split stylesheet concerns into focused files (for example: layout/shell, panel controls, diagnostics, editor overrides, dialogs/overlays) while keeping
src/styles.cssas the single entrypoint via ordered@importdirectives. - Define clear module boundaries and shared interfaces so behavior stays stable while maintainability and readability improve.
- Plan a refactor that splits