---
url: >-
  https://canary.warp-drive.io/api/@warp-drive/core/configure/functions/setupSignals.md
description: >-
  Registers the signal hooks WarpDrive uses for reactivity, built by a callback
  that receives `HooksOptions`.
---

# &#x20;setupSignals()

```ts
function setupSignals<T>(buildConfig: (options: HooksOptions) => SignalHooks<T>): void;
```

Defined in: [warp-drive-packages/core/src/signals/reactivity/configure.ts:192](https://github.com/warp-drive-data/warp-drive/blob/48dc0d277b98008082669dadc6a52e5c5682ef8e/warp-drive-packages/core/src/signals/reactivity/configure.ts#L192)

Configures the signals implementation to use, replacing any configured
before. To add a framework's hooks alongside those of other frameworks, use
[registerSignals](registerSignals.md) instead.

See [HooksOptions](../types/HooksOptions.md) for the options passed to the provided function
when called.

See [SignalHooks](../types/SignalHooks.md) for the implementation the callback function should
return.

## Type Parameters

### T

`T`

## Parameters

### buildConfig

(`options`: [`HooksOptions`](../types/HooksOptions.md)) => [`SignalHooks`](../types/SignalHooks.md)<`T`>

a function that takes options and returns a configuration object

## Returns

`void`
