fix: resolve next.js production build compilation errors and worker type mismatches#1509
Conversation
|
@thakurakanksha288 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. |
|
👋 Thanks for your PR, @thakurakanksha288!Welcome to Reframe — a browser-based video editor built for everyone 🎬 What happens next
Quick checklist
Useful links
Happy coding! 🎉 |
|
Hi @magic-peach, Thank you for reviewing my PR. I noticed that the checks are currently showing "5 workflows awaiting approval" and the build status is still pending, while Vercel deployment requires authorization. Since external contributor workflows require maintainer approval, could you please approve the pending GitHub Actions workflows so the remaining checks can run? Thank you for your time and support. |
Description
This PR resolves several critical TypeScript compiler errors, ESLint accessibility blocks, and Webpack caching issues that were preventing the production build (
npm run build) from completing successfully.Changes Made
VideoPreview.tsx: Addressed ESLintjsx-a11yrules for interactive element tracking and matched the framing check to the correct strict"fill" | "fit"types.ffmpeg.worker.ts: Implemented a fallbackWorkerContextinline interface to bypass missing globalDedicatedWorkerGlobalScopetypes without modifying global configuration scopes.constants.ts&frame-export.ts: Unified the recipe data layer by updating legacyrotateproperty references to the typedrotationfield.textOverlay.ts: Addressed an optional fallback block by casting the overlay reference dynamically, and mathematically aligned the FFmpeg drawtext coordinates (tw/2,th/2) with the UI's center-origin layout.Verification
npm run buildwith zero compilation errors.