fix: replace hardcoded 5s metadata timeout with dynamic file-size-awa…

[Amitverma0509]

Description

Replaced the hardcoded 5000ms timeout in extractMetadata with a file-size-aware helper getMetadataTimeout(fileSizeBytes) that scales the wait time based on how large the file is.

// before
}, 5000);
// after

const timeoutMs = getMetadataTimeout(file.size);

}, timeoutMs);

File size	Timeout
0 – 100 MB	10 s
100 – 200 MB	20 s
200 – 300 MB	30 s
≥ 500 MB	60 s (cap)

The helper is exported so it can be unit tested independently.

Related Issue

Closes #1163

Type of Contribution

• Bug fix
• New feature
• Documentation update
• Refactor
• GSSoC contribution

Participant Info

• Contribution level (Beginner/Intermediate/Advanced): Intermediate

Screen Recording

No UI changes — pure logic fix. To verify manually:

1. bun run dev → open http://localhost:3000
2. Drop in a video > 200 MB — loads without timeout error
3. Drop in a small file — still works fine
4. Drop in a corrupt file — still rejected via onerror

Recording / Loom link: N/A

Checklist

• I have read the contribution guidelines
• My changes follow the project structure
• I have tested my changes in Chrome, Firefox, and Safari
• bun run lint passes (no ESLint errors)
• bunx tsc --noEmit passes (no TypeScript errors)
• New interactive elements have aria-label / accessible names — N/A
• No console.log statements left in
• This PR is related to a valid issue
• Screen recording attached above — N/A (no UI change)

[vercel]

@Amitverma0509 is attempting to deploy a commit to the magic-peach1's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

👋 Thanks for your PR, @Amitverma0509!

Welcome to Reframe — a browser-based video editor built for everyone 🎬

🟠 GSSoC'26 PR detected — thanks for contributing under GirlScript Summer of Code 2026!

What happens next

1. 🤖 Automated checks — build & TypeScript typecheck will run automatically
2. ✅ Vercel preview — a preview deployment will be created (requires maintainer authorization for fork PRs)
3. 👀 Code review — a maintainer will review your changes
4. 🚀 Merge — once approved, your PR will be merged!

Quick checklist

• PR title follows Conventional Commits (e.g. feat: add dark mode)
• Linked the issue this PR closes (e.g. Closes #123)
• Tested the changes locally (bun run dev)
• Build passes (bun run build)

Useful links

• 📖 CONTRIBUTING.md
• 🐛 Open Issues
• ⭐ Star the repo to support the project!

Happy coding! 🎉

[github-actions]

✅ PR Format Check Passed — @Amitverma0509

Basic format checks passed. A maintainer will review your code changes.

This does not mean the PR is approved — it just means the format is correct.