fix: fix "window is not defined" error in usewindowresize hook (#742)

[Copilot]

• Understand the feedback: Project uses Next.js static export, not SSR
• Remove SSR-related test case from test suite
• Update test descriptions to remove SSR context
• Update hook comment to clarify this is for static build safety
• Verify all tests pass (250 tests total, 4 for this hook)
• Verify lint and format checks pass
• Keep window guards in place (still needed for static export builds)
• Fix prettier formatting (added trailing comma in test file)

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[frano-m]

LGTM! Thanks CP.

[frano-m]

@copilot We do not support SSR in this project.
This is a Next.js static export (output: 'export') using the Pages Router with getStaticProps / getStaticPaths.

Please update this test suite to remove all SSR-related behavior and assumptions.

[Copilot]

@copilot We do not support SSR in this project.
This is a Next.js static export (output: 'export') using the Pages Router with getStaticProps / getStaticPaths.

...

Updated in commit c50fb88. Removed the SSR-related test case and updated comments to reflect that this is a Next.js static export project. The test suite now focuses on client-side behavior (window resize, debouncing, cleanup) without SSR assumptions. The window guards remain in place as they're still needed during static build when window is not available.

[frano-m]

@copilot does the test still need the use of useFakeTimers?

[Copilot]

@copilot does the test still need the use of useFakeTimers?

Yes, useFakeTimers is still needed. The hook uses setTimeout for debouncing resize events (line 25), and two tests ("updates dimensions on window resize" and "debounces resize events with the specified timeout") use jest.advanceTimersByTime() to test the debouncing behavior. Without fake timers, these tests would need to wait for real timeouts, making them slower and potentially flaky.

[Copilot]

Pull request overview

This PR fixes a "window is not defined" error in the useWindowResize hook that occurs during Next.js static export builds. The fix adds window existence checks to prevent errors when the hook is called in environments where the window object is not available.

Key Changes:

• Added window guard in the useEffect hook to skip event listener setup during static builds
• Added window guard in getWindowSize() function to return default dimensions (0,0) when window is unavailable
• Added comprehensive test suite with 4 test cases covering basic functionality, resize events, debouncing, and cleanup

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
src/hooks/useWindowResize.ts	Added window existence checks in both the hook's useEffect and the getWindowSize helper function to prevent errors during static builds
tests/useWindowResize.test.ts	New test file with comprehensive test coverage for window resize functionality, including debouncing and event listener cleanup

[frano-m]

LGTM thanks CP!

[frano-m]

@copilot fix prettier for the test

[Copilot]

@copilot fix prettier for the test

Fixed in commit 9639b29. Added trailing comma to match prettier formatting rules.

[frano-m]

TY CP!