You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understood my problem, in the current version they restricted access to internal package files via package.json, I didn't know it was even possible. I thought I could get any object if it was exported from a file.
My problem is solved by a normal export:
import { FFmpeg } from "@ffmpeg/ffmpeg";
But I still think this is a bug. If not, what is the point of dist folder if I can't export anything from it? Plus, the current import references the ESM version of the library. And I need the UMD version of the library because otherwise I get a warning: #522 (comment)
Describe the bug
Module '"@ffmpeg/ffmpeg"' has no exported member 'FFmpeg' after installing the base package.
To Reproduce
Simple next.js v15 codebase
Expected behavior
Import works like the documentation shows it.
Screenshots

Desktop (please complete the following information):
Additional context
Using Cursor/VSCode
The text was updated successfully, but these errors were encountered: