phoenixframework/phoenix_live_view
This system is a comprehensive testing and upgrade infrastructure for the Phoenix LiveView framework. It provides a robust testing API that simulates browser interactions, DOM manipulation, and event handling for both server-side LiveViews and client-side JavaScript hooks. Additionally, it includes automated upgrade paths and build configuration tools to facilitate migration to newer versions of the framework.
56.9
Adequate · 5 August 2026
64k
lines of production code
JavaScript
with Elixir, TypeScript
3
bus factor · 611 authors in all
3
measurements over time
How it got here
2018–2019 · Function components and testing infrastructure
This period focused on introducing function components and async operations, alongside a comprehensive testing infrastructure. The release added support for serializing JS commands, colocated CSS, and stateless function components, while also establishing a robust test suite for LiveView and component interactions.
12 changes
2020–2024 · Comprehensive test coverage and macro component support
This period focused on expanding test coverage across LiveView and Phoenix components, introducing end-to-end testing infrastructure with Playwright, and adding comprehensive test suites for uploads, forms, and edge cases. Simultaneously, the project implemented macro components for compile-time template transformation and migrated the JavaScript client to TypeScript for improved type safety and modularity.
12 changes
2025–2026 · LiveView 1.1 upgrade and test coverage
This period focused on preparing the codebase for the Phoenix LiveView 1.1 release by introducing an automated upgrade path and comprehensive test coverage. Key changes include refactoring the HEEx template compilation into a modular TagEngine and adding extensive integration and unit tests for both the upgrade process and core LiveView behaviors.
7 changes
Survey your own repository
phoenixframework/phoenix_live_view 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.
About this page
- The description of this project is derived from its own commit history, not from its README.
- The score is its highest published measurement, taken on 5 August 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 6ba6f4e696 — the exact code this score is about.
- Scored under rubric rubric-2026.08.19. Score the same commit under that rubric and you get the same number.