Gathering detailed insights and metrics for @uirouter/sticky-states
Gathering detailed insights and metrics for @uirouter/sticky-states
Installations
npm install @uirouter/sticky-statesDeveloper Guide
BETA
Typescript
No
Module System
CommonJS
Min. Node Version
>=4.0.0
Node Version
10.16.0
NPM Version
6.9.0
Releases
7
Languages
2
TypeScript
JavaScript
TypeScript (93.95%)
JavaScript (6.05%)
Developer
ui-router
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
MIT License
42 Stars
615 Commits
15 Forks
11 Watchers
18 Branches
10 Contributors
Updated on Jul 15, 2024
Maintainers
4
Package Meta Information
Latest Version
1.5.1
Package Id
@uirouter/sticky-states@1.5.1
Unpacked Size
125.77 kB
Size
29.92 kB
File Count
51
NPM Version
6.9.0
Node Version
10.16.0
Total Downloads
Cumulative downloads
Total Downloads
NaN
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
Weekly Downloads
Monthly Downloads
Yearly Downloads
Peer Dependencies
1
Dev Dependencies
25
@types/jasmine@types/lodash@uirouter/core@uirouter/publish-scriptshuskyjasmine-corekarmakarma-chrome-launcherkarma-jasminekarma-mocha-reporterkarma-sourcemap-loaderkarma-super-dots-reporterkarma-webpacklodashprettierpretty-quickrolluprollup-plugin-node-resolverollup-plugin-sourcemapsrollup-plugin-uglifyts-loadertslinttslint-eslint-rulestypescriptwebpack
Sticky States
Sticky States for UI-Router 1.0 
Overview and Use Case
Sticky States allows two or more trees of states to run concurrently along side each other.
The initial use case for this functionality is to implement "tabs" for application modules. Using Sticky States, a single app can implement one state tree for each tab, and have them operate at the same time, in parallel to each other. Each tab is implemented as its own UI-Router state tree. While one tab is active, the other tab is inactivated, but can be reactivated without losing any work in progress.
For the tabs use case, Sticky States work best along with Deep State Redirect
Sticky State Lifecycle
A Sticky State is the root of a UI-Router state tree which can continue running even after it is "exited". The sticky state (and its children) have a different lifecycle than normal states. The views of a Sticky State (and all activated substates) are retained until one of two things happen:
- The parent of the sticky state is exited
- The parent of the sticky state is directly activated
If a sibling of the sticky state (or a child of a sibling) is activated, the sticky state tree will "inactivate". A transition back to the inactivate state will reactivate it.
Using
Sticky states works requires ui-router-core 2.0.0 or above.
Run npm ls to check the version of ui-router-core included with the UI-Router distribution for your framework
1) Add Plugin
ng1
In Angular 1, register a plugin by injecting $uiRouterProvider in a config() block.
1import {StickyStatesPlugin} from "@uirouter/sticky-states"; 2 3angular.module('myapp', ['ui.router']).config(function($uiRouterProvider) { 4 $uiRouterProvider.plugin(StickyStatesPlugin); 5});
ng2
In Angular 2, register a plugin in your UIRouterConfig class
1import {StickyStatesPlugin} from "@uirouter/sticky-states"; 2 3export class MyConfig { 4 configure(uiRouter: UIRouter) { 5 uiRouter.plugin(StickyStatesPlugin); 6 } 7}
react
In React, register a plugin after creating your UIRouterReact instance.
1import {StickyStatesPlugin} from "@uirouter/sticky-states"; 2 3let router = new UIRouterReact(); 4router.plugin(StickyStatesPlugin);
Or, if using component bootstrapping, add the plugin in your routerConfig function.
1let routerConfig = (router) => router.plugin(StickyStatesPlugin); 2 3return <UIRouterReact config={routerConfig}/>;
2) Mark a state as sticky
The sticky state's view must target a named ui-view.
The named ui-view must not be shared with other states.
Create and target a named ui-view.
1 <ui-view name="admin"></ui-view>
1let adminModule = { 2 name: 'admin', 3 sticky: true, 4 views: { 5 admin: { component: AdminComponent } 6 } 7}
The AdminComponent should remain active in the ui-view named admin, even if a sibling state is activated.
3) Show/Hide the sticky component
When a sticky state is inactive, it's often desired to hide the contents from the UI.
This can be achieved using StateService.includes.
In some cases, ui-sref-active may also be used to toggle a class on the named ui-view.
Example
These minimal examples show how to get started with sticky states in:
More
This project was ported from the UI-Router Extras project for legacy UI-Router. For more information, see the ui-router extras documentation: http://christopherthielen.github.io/ui-router-extras/#/sticky
TODO: Rewrite docs
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
dependency not pinned by hash detected -- score normalized to 3
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:29: update your workflow using https://app.stepsecurity.io/secureworkflow/ui-router/sticky-states/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/update_dependencies.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/ui-router/sticky-states/update_dependencies.yml/master?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/update_dependencies.yml:27: update your workflow using https://app.stepsecurity.io/secureworkflow/ui-router/sticky-states/update_dependencies.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/update_dependencies.yml:55: update your workflow using https://app.stepsecurity.io/secureworkflow/ui-router/sticky-states/update_dependencies.yml/master?enable=pin
- Info: 0 out of 3 GitHub-owned GitHubAction dependencies pinned
- Info: 1 out of 2 third-party GitHubAction dependencies pinned
Reason
Found 1/19 approved changesets -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/ci.yml:1
- Warn: no topLevel permission defined: .github/workflows/update_dependencies.yml:1
- Info: no jobLevel write permissions found
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'master'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 23 are checked with a SAST tool
Reason
60 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-93q8-gq69-wqmw
- Warn: Project is vulnerable to: GHSA-qwcr-r2fm-qrc7
- Warn: Project is vulnerable to: GHSA-v6h2-p8h4-qcjw
- Warn: Project is vulnerable to: GHSA-grv7-fg5c-xmjg
- Warn: Project is vulnerable to: GHSA-pxg6-pf52-xh8x
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-gxpj-cx7g-858c
- Warn: Project is vulnerable to: GHSA-w573-4hg7-7wgq
- Warn: Project is vulnerable to: GHSA-ff7x-qrg7-qggm
- Warn: Project is vulnerable to: GHSA-j4f2-536g-r55m
- Warn: Project is vulnerable to: GHSA-r7qp-cfhv-p84w
- Warn: Project is vulnerable to: GHSA-74fj-2j2h-c42q
- Warn: Project is vulnerable to: GHSA-pw2r-vq6v-hr8c
- Warn: Project is vulnerable to: GHSA-jchw-25xp-jwwc
- Warn: Project is vulnerable to: GHSA-cxjh-pqwp-8mfp
- Warn: Project is vulnerable to: GHSA-ww39-953v-wcq6
- Warn: Project is vulnerable to: GHSA-765h-qjxv-5f44
- Warn: Project is vulnerable to: GHSA-f2jv-r9rf-7988
- Warn: Project is vulnerable to: GHSA-43f8-2h32-f4cj
- Warn: Project is vulnerable to: GHSA-qqgx-2p2h-9c37
- Warn: Project is vulnerable to: GHSA-9c47-m6qq-7p4h
- Warn: Project is vulnerable to: GHSA-7x7c-qm48-pq9c
- Warn: Project is vulnerable to: GHSA-rc3x-jf5g-xvc5
- Warn: Project is vulnerable to: GHSA-76p3-8jx3-jpfq
- Warn: Project is vulnerable to: GHSA-3rfm-jhwj-7488
- Warn: Project is vulnerable to: GHSA-hhq3-ff78-jv3g
- Warn: Project is vulnerable to: GHSA-29mw-wpgm-hmr9
- Warn: Project is vulnerable to: GHSA-35jh-r3h4-6jhm
- Warn: Project is vulnerable to: GHSA-82v2-mx6x-wq7q
- Warn: Project is vulnerable to: GHSA-952p-6rrq-rcjv
- Warn: Project is vulnerable to: GHSA-f8q6-p94x-37v3
- Warn: Project is vulnerable to: GHSA-xvch-5gv4-984h
- Warn: Project is vulnerable to: GHSA-6fx8-h7jm-663j
- Warn: Project is vulnerable to: GHSA-hj48-42vr-x3v9
- Warn: Project is vulnerable to: GHSA-hrpp-h998-j3pp
- Warn: Project is vulnerable to: GHSA-gcx4-mw62-g8wm
- Warn: Project is vulnerable to: GHSA-c2qf-rxjj-qqgw
- Warn: Project is vulnerable to: GHSA-44c6-4v22-4mhx
- Warn: Project is vulnerable to: GHSA-4x5v-gmq8-25ch
- Warn: Project is vulnerable to: GHSA-hxcc-f52p-wc94
- Warn: Project is vulnerable to: GHSA-g4rg-993r-mgx7
- Warn: Project is vulnerable to: GHSA-4rq4-32rv-6wp6
- Warn: Project is vulnerable to: GHSA-64g7-mvw6-v9qj
- Warn: Project is vulnerable to: GHSA-fxwf-4rqh-v8g3
- Warn: Project is vulnerable to: GHSA-25hc-qcg6-38wj
- Warn: Project is vulnerable to: GHSA-xfhh-g9f5-x4m4
- Warn: Project is vulnerable to: GHSA-qm95-pgcg-qqfq
- Warn: Project is vulnerable to: GHSA-cqmj-92xf-r6r9
- Warn: Project is vulnerable to: GHSA-7p7h-4mm5-852v
- Warn: Project is vulnerable to: GHSA-38fc-wpqx-33j7
- Warn: Project is vulnerable to: GHSA-662x-fhqg-9p8v
- Warn: Project is vulnerable to: GHSA-394c-5j6w-4xmx
- Warn: Project is vulnerable to: GHSA-78cj-fxph-m83p
- Warn: Project is vulnerable to: GHSA-fhg7-m89q-25r3
- Warn: Project is vulnerable to: GHSA-4vvj-4cpr-p986
- Warn: Project is vulnerable to: GHSA-6fc8-4gx4-v693
- Warn: Project is vulnerable to: GHSA-3h5v-q93c-6h6q
- Warn: Project is vulnerable to: GHSA-72mh-269x-7mh5
- Warn: Project is vulnerable to: GHSA-h4j5-c7cj-74xg
- Warn: Project is vulnerable to: GHSA-c4w7-xm78-47vh
Score
2.7
/10
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More