Repository navigation
Release v4.80.0
Summary
The default blueprint now works out of the box with React Aria through @cratis/components. PrimeReact is used only when a UI profile lists it, and then it wins any component name it shares with the default library.
Added
hostProfilePackages(TypeScript) andPackageResolver.HostPackages(C#) give hosts one deterministic package order: core, then Cratis.Components, then the component libraries the profile lists, then blueprints. A deliberately chosen library such as PrimeReact therefore always wins shared names likedataTable, and the blueprint keeps its own shell components. (#250)
Changed
- The default blueprint shell (sidebar, topbar, user menu and configuration panel) is built on
@cratis/componentsand React Aria, and no longer installs or loads PrimeReact. (#250) @cratis/scene.blueprint.defaultand@cratis/scene.componentsno longer depend on PrimeReact or primeicons. Apps that use PrimeReact list it in their UI profile (packages→PrimeReact). (#250)@cratis/scene.blueprint.defaulttakes@cratis/components(^4.34.0),@cratis/arc,@cratis/arc.react,@cratis/fundamentalsandreflect-metadataas peer dependencies that the app provides, so an app gets a single copy of the component library. (#250)- A template that needs a package its own package does not depend on, such as the PrimeReact-based gallery templates, is offered only when the profile includes that package. Otherwise a diagnostic explains how to add it. (#250)