Skip to content

Refine signal tracking explanation in intro-to-reactivity #1316

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 26, 2025
+2 −2
Merged

Refine signal tracking explanation in intro-to-reactivity #1316

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions src/routes/concepts/intro-to-reactivity.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -127,9 +127,9 @@ setCount(1);
// `count` is not being tracked, so the console log will not update when `count` changes.
```

Since initialization is a **one-time event**, if a signal is accessed _outside of a tracking scope_, it will not be tracked.
Initialization, or creation is a **one-time event** that doesn't cause tracking.
To track a signal, it must be accessed within the scope of a subscriber.
Reactive primitives, such as [effects](/concepts/effects), can be used to create subscribers.
Reactive primitives, such as [memos](/concepts/derived-values/memos) can be used to create derived values from signals or other memos, and [effects](/concepts/effects) to create subscribers that use the reactive graph output once it's settled.

```jsx
const [count, setCount] = createSignal(0);
Expand Down