GitHub user aglinxinyuan added a comment to the discussion: Proposal: Ditch Angular and Switch to a new frontend framework
Following up on the prototype, I propose migrating Texera one component at a time. Each PR should preserve the current appearance and behavior of the piece it replaces. Angular can host React components while it continues managing routes and sessions. > start with small interactive components (like buttons), and then gradually > keep “moving upwards” until eventually your entire page is built with React. [React’s incremental adoption guide](https://react.dev/learn/add-react-to-an-existing-project) 1. **Verify the build and lifecycle.** [PR #9472](https://github.com/apache/texera/pull/9472) proves that the existing Angular toolchain compiles TSX, and that React can render, handle a click, and unmount when Angular destroys its host. 2. **Port the About content.** Start with an opt-in version of `/about`, using the same copy, images, links, and layout. Verify direct navigation and desktop and narrow layouts before switching the default. 3. **Port the read-only quota summary.** Pass the existing quota values to React and check zero and populated states. 4. **Port one dashboard view or action per PR.** Start with the workflow card display, then rename as a separate change. Repeat with dataset and model views using their existing services and permissions. 5. **Start the workspace with display components.** Port console output, result rows, and result details in separate PRs. Check live output, pagination, and results for each output port. 6. **Port workflow editing in small slices.** Start with one operator property field. Move Form View, Monaco, and the JointJS canvas in separate PRs, splitting the canvas into rendering, editing, and collaboration work. Keep one workspace session for Yjs, autosave, and execution. Before switching the workspace default, test concurrent graph and code edits with one Angular client and one React client, then run the workflow against a real backend. 7. **Port the agent panel in slices.** Start with message display, then move the composer and tool actions in separate PRs using the existing agent connection. 8. **Switch the shell in stages.** Move navigation, routing, guards, and sign-in in separate PRs, then switch the entry point. Check direct links, refresh, back and forward, and permission redirects. 9. **Remove Angular after the last dependent view moves.** Delete unused components and then retire Angular’s build and dependencies. Check the packaged app and license audit. For each visible change, use the same data and viewport for side-by-side screenshots and have a teammate exercise the affected flow in the browser. Use current `main` as the parity baseline. [Draft PR #9389](https://github.com/apache/texera/pull/9389) has reference code and screenshots. The About pilot will give us a first measure of the styling and review effort before we estimate the rest. GitHub link: https://github.com/apache/texera/discussions/9387#discussioncomment-19646651 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
