feat: add sidebar scroll position persistence

[ubay1]

• Add useScroll hook with debounced scroll event handling
• Add useScrollToElement hook to save/restore scroll position via localStorage and in-memory NavigationStateContext
• Add NavigationStateProvider context for session-level state
• Update Sidebar component to use useScrollToElement with a useLayoutEffect workaround (SideBar lacks forwardRef support)

#74 fix sidebar scroll position persistence

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
nodejs-learn	Ready	Preview	May 21, 2026 2:06am

[cursor]

PR Summary

Medium Risk
Moderate risk because it introduces new client-side context/provider wrapping the layout plus DOM querying and localStorage reads/writes that can impact hydration and runtime behavior in the sidebar.

Overview
Adds sidebar scroll-position persistence by introducing NavigationStateProvider (session in-memory state) and new hooks useScroll (debounced scroll listener) and useScrollToElement (save/restore via context + localStorage).

Updates Layout to wrap the app in the provider and updates Sidebar to restore/save its <aside> scroll position, including a useLayoutEffect workaround to obtain the real DOM element because the upstream SideBar component doesn’t forward refs.

^{Reviewed by Cursor Bugbot for commit 93020dd. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

👋 Codeowner Review Request

The following codeowners have been identified for the changed files:

Team reviewers: @nodejs/nodejs-website

Please review the changes when you have a chance. Thank you! 🙏

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 305c7d0. Configure here.}

[RushilJalal]

Kindly merge asap, this is something which is actively causing problems for me while reading docs.

[AugustinMauroy]

I didn't recall correctly @nodejs/nodejs-website but don't we solve that on ui component ?