Angular Clock Component
Use the right package manager
Fake JavaScript timers
An analog clock for your React app.
Get the current time in microseconds
A simple clock/ticker implementation to track elapsed/delta time.
React Live Clock
A 3D animated countdown component for React.
Exponentially Weighted Moving Average
Cross platform children list of a PID
A simple clock/ticker implementation to track elapsed/delta time.
a mock clock for tests involving timing
Jest plugin to mock dates, times, and datetimes.
Timing Events tied to @colyseus/clock
Lightweight and type-safe High-Order Components (HOCs) library for React, leveraging high-order types from [`hotscript`](https://github.com/gvergnaud/hotscript) and JavaScript Proxies for zero VDOM overhead.
Add the power of events to your (TypeScript) projects!
Add the power of Simple Events to your projects. Every event has an argument with its data.
Angular components for the NI Nimble Design System
Yjs encoding protocols
Styled web components for the NI Nimble Design System
NI's JavaScript ESLint Shareable Config
Node.JS Argon2 password hashing algorithm following the PHC string format
Node.JS Argon2 password hashing algorithm following the PHC string format
NI's TypeScript ESLint Shareable Config
This is the Rust version of https://gitlab.in2p3.fr/CTA-LAPP/PHOENIX_LIBS2/PhoenixClock project. This project aims to ease the use of clock in complex environments, especially distributed environments where latencies measurement has to be precise and reproductible when running unit tests. **PhoenixClock** provide **PGenericClock**, a template classe which takes two arguments : - The main clock backend (could be **clock**, **PClockNs** for nanoseconds, etc) - A mock of a clock, **PClockMock**, which can play, register and replay a sequence of clock calls These clocks are activated with a mode `PClockMode::PClockMode` which can be : - `PClockMode::NO_MOCK` : for a normal usage - `PClockMode::MOCK` : when the mock the desired clock is played - `PClockMode::MOCK_RECORD` : when the real clock backend is used but the clock mock is recording (could be usefull for debugging or to desing new unit tests quickly)
This is the Rust version of https://gitlab.in2p3.fr/CTA-LAPP/PHOENIX_LIBS2/PhoenixClock project. This project aims to ease the use of clock in complex environments, especially distributed environments where latencies measurement has to be precise and reproductible when running unit tests. **PhoenixClock** provide **PGenericClock**, a template classe which takes two arguments : - The main clock backend (could be **clock**, **PClockNs** for nanoseconds, etc) - A mock of a clock, **PClockMock**, which can play, register and replay a sequence of clock calls These clocks are activated with a mode `PClockMode::PClockMode` which can be : - `PClockMode::NO_MOCK` : for a normal usage - `PClockMode::MOCK` : when the mock the desired clock is played - `PClockMode::MOCK_RECORD` : when the real clock backend is used but the clock mock is recording (could be usefull for debugging or to desing new unit tests quickly)