-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
Support for nextjs 13.4 Turbopack #20
Comments
We are waiting until Turbopack supports plugins! Otherwise, we can't implement it... |
@aralroca looks like they currently do :) https://turbo.build/pack/docs/features/customizing-turbopack |
great news @edwinveldhuizen ! |
Any new updates regarding this issue? |
@aralroca more and more projects works without any issues with turbo. Maybe it's good time to make next-translate work with turbo? 😃 |
Any new updates? 👀 |
It is planned for version 3.0 which will be the next version. |
Hi guys, any update on this ? 👀 |
Hi, same question ! any date or timeline for version 3.0 ? |
hey there, just been here to drop that i definitely love your plugin. it does an amazing work in Nextjs.
I was currently investigating the new turbopack feature that you can now try with
next dev --turbo
ornext build --turbo
(it's currently in beta as you can see here https://nextjs.org/blog/next-13-4#turbopack-beta) and then i realize that this might not be very compatible with the current next-translate plugin.I tried to remove theses value to test, etc but i suspect the main issue to be the
next-translate-plugin
that is something made for webpack.So i was wondering, do you guys plan to work on a future integration with turbopack? Do you think it will require a radical change of the plugin or is there a way to make it work both for webpack and turbopack?
The text was updated successfully, but these errors were encountered: