Add error.tsx and loading.tsx pages for improved UX

[lak7]

Description

Add Next.js App Router error.tsx and loading.tsx files to key route segments for better user experience during navigation and error scenarios.

Current Behavior

• No custom error boundaries exist - users see default Next.js error pages
• No loading states during route transitions - content appears abruptly
• Poor UX when API calls fail or routes take time to load

Expected Behavior

• Graceful error pages that match DevilDev's design aesthetic
• Skeleton loaders or spinners during page transitions
• Users can recover from errors without manually refreshing

Routes to Cover

Priority routes:

• src/app/error.tsx (root error boundary)
• src/app/loading.tsx (root loading state)
• src/app/project/error.tsx
• src/app/project/loading.tsx
• src/app/project/[projectId]/error.tsx
• src/app/project/[projectId]/loading.tsx

Optional/bonus:

• src/app/pricing/loading.tsx
• src/app/settings/loading.tsx
• src/app/not-found.tsx (custom 404)

Helpful Resources

• Next.js Error Handling Docs
• Next.js Loading UI Docs
• Existing skeleton: src/components/ui/project-skeleton.tsx

[anshsahu01]

Hi @lak7 I'd love to take this on. I’m very familiar with Next.js App Router and the error.tsx/loading.tsx patterns. I noticed there's already a project-skeleton.tsx in the UI folder—I'll make sure to utilize that to keep the loading states consistent with the current design.

[lak7]

Sure @anshsahu01, I will assign you this issue. Just fork the repo and read CONTRIBUTING.md
You can raise the PR once done!

[lak7]

@anshsahu01 are you still working on this issue?

[Konarksharma13]

Hi @lak7. I’m new to this project but really excited to contribute and learn more about the codebase. Improving the user experience around loading and error states sounds like a meaningful task, and I’d love to work on adding proper error.tsx and loading.tsx files for the key App Router segments.

I’ll do my best to follow the existing design patterns and match DevilDev’s aesthetic, using the current skeleton components where appropriate. Looking forward to learning from the maintainers and feedback along the way.

Thanks for the opportunity!

[lak7]

Sure @Konarksharma13 just read the CONTRIBUTING.md and you can take on this issue. Thanks!

[lak7]

@Konarksharma13 are you workin on this issue?

[Konarksharma13]

Yes, I'm working on it. Trying to figure it out since it's my first time contributing.

[lak7]

Ok, let me know if you have any question. Here is the discord link