2.0.0
Release v2.0.0 🚀
We are pleased to announce the latest release of next-translate with several significant changes that improve the user experience and address known issues.
Improved support for Next.js 13 app directory
With this release, we have made it easier for users to use the app directory of Next.js 13 for both server/client pages and components. Refer to the README.md documentation for more information on this feature. If you're interested in the underlying functionality, we also recommend reading this article.
Also, you have an example here: https://github.com/aralroca/next-translate/tree/master/examples/with-app-directory
Replaced regex with parser in Webpack plugin
Previously, we were using regex in the Webpack plugin, which caused a significant number of issues. With the latest release, we have replaced the regex with a parser, which automatically resolves many of the previously open issues. We would like to extend a special thanks to @StLyn4 for their contributions to this effort.
Next-translate-plugin
To reduce the weight of the plugin, which now includes the parser, we have moved it to a separate package called next-translate-plugin. You can now install it as a devDependency, without impacting your pipeline. This move also ensures that we are ready to provide support for when Turbopack is no longer in alpha.
Migrating from v1.0 to v2.0 😊
If you are currently using next-translate v1.0 and want to upgrade to the latest version, please follow the migration steps described in this link. The migration process involves a few changes, including modifying the next.config.js file and updating your translations. Following these steps will ensure a smooth transition to the new version.
What's Changed
- fix: align interpolation type by @boredland in #934
- Allow empty string by @vascosilvaa in #958
- Fix error when running
next startwithout sources by @StLyn4 in #930 - Exposing internal context by @StLyn4 in #969
- Update to Next.js 13 project + examples by @aralroca in #971
- Move plugin to next-translate-plugin package by @aralroca in #975
- Support Next.js 13 app-dir for server/client pages/components by @aralroca in #982
- Improve example app dir by @aralroca in #984
What's Changed on next-translate-plugin
- Support Next.js 13 app-dir for server/client pages and server/client components by @aralroca in aralroca/next-translate-plugin#1
New Contributors
- @boredland made their first contribution in #934
- @vascosilvaa made their first contribution in #958
Thank you for using next-translate! We hope that this release enhances your experience, and please feel free to report any issues you encounter.
Full Changelog: 1.6.0...2.0.0
