Skip to content

Commit 8218198

Browse files
authored
Signals debug docs (#1374)
* Signals debug docs * Make discoverable through debugging.md
1 parent 2aec9d7 commit 8218198

File tree

4 files changed

+37
-1
lines changed

4 files changed

+37
-1
lines changed

content/en/guide/v10/debugging.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -60,6 +60,15 @@ render(<App />, document.getElementById('root'));
6060

6161
Make sure to set the `NODE_ENV` variable to the correct value in your build tool.
6262

63+
## Debugging Signals
64+
65+
If you're using Preact Signals in your application, there are specialized debugging tools available:
66+
67+
- **[Signals Debug](https://github.com/preactjs/signals/blob/main/packages/debug)** - A development tool that provides detailed console output about signal updates, effect executions, and computed value recalculations.
68+
- **[Signals DevTools](https://github.com/preactjs/signals/blob/main/packages/devtools-ui)** - Visual DevTools UI for debugging and visualizing Preact Signals in real-time. You can embed it directly in your page for demos, or integrate it into custom tooling.
69+
70+
> **Note:** These are framework-agnostic tools from the Signals library. While they work great with Preact, they're not Preact-specific.
71+
6372
## Debug Warnings and Errors
6473

6574
Sometimes you may get warnings or errors when Preact detects invalid code. These should be fixed to ensure that your app works flawlessly.

content/en/guide/v10/signals.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -693,3 +693,12 @@ function Component() {
693693
);
694694
}
695695
```
696+
697+
## Debugging
698+
699+
If you're using Preact Signals in your application, there are specialized debugging tools available:
700+
701+
- **[Signals Debug](https://github.com/preactjs/signals/blob/main/packages/debug)** - A development tool that provides detailed console output about signal updates, effect executions, and computed value recalculations.
702+
- **[Signals DevTools](https://github.com/preactjs/signals/blob/main/packages/devtools-ui)** - Visual DevTools UI for debugging and visualizing Preact Signals in real-time. You can embed it directly in your page for demos, or integrate it into custom tooling.
703+
704+
> **Note:** These are framework-agnostic tools from the Signals library. While they work great with Preact, they're not Preact-specific.

content/en/guide/v11/debugging.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -60,6 +60,15 @@ render(<App />, document.getElementById('root'));
6060

6161
Make sure to set the `NODE_ENV` variable to the correct value in your build tool.
6262

63+
## Debugging Signals
64+
65+
If you're using Preact Signals in your application, there are specialized debugging tools available:
66+
67+
- **[Signals Debug](https://github.com/preactjs/signals/blob/main/packages/debug)** - A development tool that provides detailed console output about signal updates, effect executions, and computed value recalculations.
68+
- **[Signals DevTools](https://github.com/preactjs/signals/blob/main/packages/devtools-ui)** - Visual DevTools UI for debugging and visualizing Preact Signals in real-time. You can embed it directly in your page for demos, or integrate it into custom tooling.
69+
70+
> **Note:** These are framework-agnostic tools from the Signals library. While they work great with Preact, they're not Preact-specific.
71+
6372
## Debug Warnings and Errors
6473

6574
Sometimes you may get warnings or errors when Preact detects invalid code. These should be fixed to ensure that your app works flawlessly.

content/en/guide/v11/signals.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -182,7 +182,7 @@ function removeTodo(todo) {
182182

183183
## Building the UI
184184

185-
Now that we've modeled our application's state, it's time to wire in up to a nice UI that users can interact with.
185+
Now that we've modeled our application's state, it's time to wire it up to a nice UI that users can interact with.
186186

187187
```jsx
188188
function TodoList() {
@@ -693,3 +693,12 @@ function Component() {
693693
);
694694
}
695695
```
696+
697+
## Debugging
698+
699+
If you're using Preact Signals in your application, there are specialized debugging tools available:
700+
701+
- **[Signals Debug](https://github.com/preactjs/signals/blob/main/packages/debug)** - A development tool that provides detailed console output about signal updates, effect executions, and computed value recalculations.
702+
- **[Signals DevTools](https://github.com/preactjs/signals/blob/main/packages/devtools-ui)** - Visual DevTools UI for debugging and visualizing Preact Signals in real-time. You can embed it directly in your page for demos, or integrate it into custom tooling.
703+
704+
> **Note:** These are framework-agnostic tools from the Signals library. While they work great with Preact, they're not Preact-specific.

0 commit comments

Comments
 (0)