🐛 Bug: Homepage crashes when calendar fetch fails

[tusharv01]

Describe the bug

The homepage crashes when the external Google Calendar fetch fails.

When the calendar request fails (e.g., due to network/DNS issues), the datesInfo value becomes undefined. This causes:

• A serialization error in getStaticProps
• A runtime error when the UI attempts to call .map() on null/undefined

This results in the homepage failing to load.

Steps To Reproduce

1. Clone and run the project locally
2. Run yarn dev
3. Simulate failure of the external calendar API (e.g., disconnect internet or block access to calendar.google.com)
4. This issue occurs when the external calendar API is unavailable (e.g., DNS failure, firewall blocking, or network issues).
5. Open http://localhost:3000
6. Observe that the homepage crashes

Expected Behavior

The website should load successfully even if the calendar fetch fails.

The application should gracefully handle the failure and fallback to a safe value (e.g., null or empty list) instead of crashing.

Screenshots

Homepage error showing "Error serializing .datesInfo" and map crash

Device Information [optional]

- OS:
- Browser:
- version:

Are you working on this issue?

Yes

Do you think this work might require an [Architectural Decision Record (ADR)]? (significant or noteworthy)

No

[Siddhartha20242]

Hi, @tusharv01, Even though I am not a maintainer, It's really good that you found such a good bug but in this org you are required to get your issue assigned before you make a pull request. Our maintainers are pretty busy this days and it would be helpful if you could tag only one maintainer and tell thim to assign the issue and they will be assigning you and you can make a pull request.

I am saying this because it will be easy to maintain this repository issues and pull request after getting assigned. And again our maintainers are busy so they would get ample time if you do so. Thank you:)

[tusharv01]

Hi @Siddhartha20242 , thanks for pointing this out!

I’ll make sure to get the issue assigned before submitting a PR next time. Appreciate the guidance 🙂
Please review this pr.