What is this?
UI-Router is a client-side routing framework for Single Page Applications, originally built for AngularJS, that models an app as a hierarchical tree of states instead of flat URL-to-view mappings.
UI-Router is a client-side routing framework for Single Page Applications, originally built for AngularJS, that models an app as a hierarchical tree of states instead of flat URL-to-view mappings.Is it a replacement for Angular's built-in router, or something else?Yes, it's an alternative routing framework: instead of mapping URLs directly to views, it uses a state machine where states can be nested, and each state manages its own view, data, and transitions.
Yes, it's an alternative routing framework: instead of mapping URLs directly to views, it uses a state machine where states can be nested, and each state manages its own view, data, and transitions.How do I add it to my project?Grab the stable build (or minified version) and follow the framework-specific getting-started guide, since there are separate packages for Angular 1, Angular 2+, and React.
Grab the stable build (or minified version) and follow the framework-specific getting-started guide, since there are separate packages for Angular 1, Angular 2+, and React.Does this work with modern Angular, or only AngularJS?There are separate editions: this repo is the Angular 1.x (AngularJS) source, with distinct versions/packages available for Angular 2+ and for React.
There are separate editions: this repo is the Angular 1.x (AngularJS) source, with distinct versions/packages available for Angular 2+ and for React.Is this still actively evolving, or mostly legacy at this point?The README points to an older 0.x legacy line with its own 'Extras/Addons' package, suggesting long-standing versioning history; it's a mature, long-running project rather than a fast-moving new tool.
The README points to an older 0.x legacy line with its own 'Extras/Addons' package, suggesting long-standing versioning history; it's a mature, long-running project rather than a fast-moving new tool.Why use nested states instead of plain routes?Nested states let each level of the UI (e.g. a layout, a tab, a sub-tab) own its own view, data, and URL segment, so navigating deep into the app updates only the relevant nested views instead of re-rendering everything.
Nested states let each level of the UI (e.g. a layout, a tab, a sub-tab) own its own view, data, and URL segment, so navigating deep into the app updates only the relevant nested views instead of re-rendering everything.Can I bookmark a deep location inside the app?Yes, because state transitions drive the browser URL (and vice versa), users can bookmark or share a link to any specific state deep within the single-page app.
Yes, because state transitions drive the browser URL (and vice versa), users can bookmark or share a link to any specific state deep within the single-page app.What are similar projects?angular.js, ember.js, mithril.js, dva, riot, framework, react-router, svelte
angular.js, ember.js, mithril.js, dva, riot, framework, react-router, svelteWhich topics is it in?state-machine, angularjs, javascript-framework, routing, router, frontend-framework, web-framework, web-development, framework, frontend, library, typescript
state-machine, angularjs, javascript-framework, routing, router, frontend-framework, web-framework, web-development, framework, frontend, library, typescript