> For the complete documentation index, see [llms.txt](https://docs.nestjstools.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nestjstools.com/clock/readme.md).

# Introduction

### @nestjstools/clock

**Time abstraction for NestJS**

In most applications, time is everywhere:

* timestamps
* expiration logic
* domain rules
* logging
* validations
* comparisons

But calling `new Date()` directly inside your business logic makes your system:

* Hard to test
* Non-deterministic
* Infrastructure-coupled
* Difficult to reason about

`@nestjstools/clock` solves this by introducing a clean abstraction over time.

### Why use Clock?

Instead of:

```
const now = new Date();
```

You write:

```
const now = this.clock.now();
```

And now:

* You can inject time
* You can freeze time in tests
* You remove infrastructure concerns from your domain layer

### The Problem with `new Date()`

Direct system time usage:

```
if (new Date() > expirationDate) { ... }
```

Creates:

* Hidden side effects
* Hard-to-test services
* Unpredictable unit tests
* Tight coupling to system clock

Time is infrastructure — it should be abstracted.

***

### The Solution: IClock

Clock introduces a simple interface:

```
interface IClock {
  now(): Date
  today(): CalendarDate
}
```

This allows you to:

* Inject system time
* Replace time in tests


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nestjstools.com/clock/readme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.