-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
turbopack support #266
Comments
+1 |
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 make this to work. |
I did some digging again and the blocker is Turbopack requires support for importing binaries (raw) files (mp4's). |
Tried this today and managed to get a few steps in but it's still complaining about them when I view one of the pages experimental: {
turbo: {
resolveExtensions: ['.mdx', '.tsx', '.ts', '.jsx', '.js', '.mjs', '.json', '.mp4'],
rules: {
'./videos/*.mp4': {
loaders: ['next-video/webpack/video-raw-loader.js'],
as: '*.json',
},
'./videos/*.mp4.json': {
loaders: ['next-video/webpack/video-json-loader.js'],
as: '*.json',
},
},
},
}, Extension seems to be wrong:
|
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) |
By default, when using turbopack dev it throws an error
The text was updated successfully, but these errors were encountered: