Wesley Luyten
Wesley Luyten
Thanks for reporting. Strange I didn't run into this with the other functions, in dev mode it might be fine. I see Next.js itself sometimes uses string file paths in...
@fain182 we just released v1.3.0 with a separate next-video config that should solve this serialization issue. docs can be found here: https://github.com/muxinc/next-video#asset-metadata-storage-hooks-callbacks let me know how it goes!
thanks for the contribution! this looks great. the question will be if we want to introduce this level of abstraction in the project, I will run this by the team....
That sounds reasonable to me. Happy to review a PR if you have the appetite for adding this. Cheers
@fain182 in your use case do you have any local video files that are processed by next-video? because the symlink is still needed to show raw local video files in...
Thanks for reporting! yes, for now turbopack doesn't support inline webpack loaders which next-video uses for the video type. we might need to export this as a separate package to...
I did some digging again and the blocker is Turbopack requires support for importing binaries (raw) files (mp4's). https://github.com/vercel/next.js/discussions/72147
yes, thanks for digging in! Turbopack is trying to convert the imported file to a string I believe which is not we want. it should stay raw (binary)
@okerx my old comment is not correct. the fix in next-video will require this change in Next.js in Turbopack https://github.com/vercel/next.js/pull/75056
This blocked by the Next.js v15.4.0 release. When it's released we can fix this issue.