schultek/jaspr

This system is a full-stack web framework called Jaspr, designed for building interactive web applications with a clear separation between client-side and server-side rendering. It provides a component-based architecture that supports state management, routing, and dynamic UI updates, while also enabling server-side rendering and static site generation. The framework includes tooling for development, testing, and deployment, along with integrations for popular Dart packages like Riverpod and Serverpod.

This period focused on a major architectural shift, separating client and server entry points and introducing a new component-based rendering engine. The team expanded the ecosystem by adding a dedicated router, a testing framework, and improved state management integration with Riverpod 3. Additionally, the JasprPad application was significantly enhanced with new UI components, server-side analysis capabilities, and automated deployment pipelines.

44 changes

This period focused on establishing a robust CLI tooling infrastructure and expanding the framework's capabilities for server-side rendering, routing, and Flutter integration. Key developments included the introduction of a modular command system, async component support, and declarative CSS generation, alongside numerous examples demonstrating these new features.

74 changes

This period focused on the launch of a new Jaspr-based website and the architectural shift towards explicit client-server separation. The team introduced distinct entrypoints for client and server environments across the framework, CLI, and examples, while also adding server-side state synchronization for Riverpod and comprehensive DOM utilities.

47 changes

This period focused on expanding test coverage for the Jaspr CLI and the website application. The work included adding unit and integration tests for CLI commands, lint rules, and the pad application, alongside implementing new layout components for the website.

6 changes

schultek/jaspr was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.