2.3.0

Summer release 2.3 ☀️

Where are versions 2.1 and 2.2? Why did we go from 2.0.6 to 2.3? Well, this release we have focused on fixing compatibility bugs with Next.js 13.3, when writing the version it was a mistake to think so much about 3, but now it stays with 2.3! 😸

In this new release:

• You can use the pages directory together with the app directory to facilitate migration.
• We have fixed other issues with Next.js > 13.3 that we could fix on our end.
• You no longer need to use experimental.appDir within next.config.js.

Breaking change from Next.js >= 13.3

The middleware of the appDir that we had in the example and recommended in the documentation stopped working.

As a solution, we have added support for it to be done using the dynamic route /[lang]. The example and README.md have been updated so that you can see how to make it work. We have not stopped supporting the old way, and it is assumed that it will work again when this issue in Next.js is fixed:

• vercel/next.js#49883

If you are affected by this Next.js issue, you can write there or contribute to the solution. In any case, you can use now the dynamic route /[lang] and, without needing the middleware, you can use the redirect within the RSC (see example).

What's Changed in Next-translate

• add hoc to fix client components in next-translate-plugin by @aralroca in #1061
• add tests about flat keys when keySeparator=false by @aralroca in #1065
• update appdir example and upgrade dependencies by @aralroca in #1070
• improve appDir example by @aralroca in #1071

What's Changed in Next-translate-plugin

• use appDir with pagesDir together + remove expermiental.appDir by @aralroca in aralroca/next-translate-plugin#25
• fix error in Next.js 13.4.x by @aralroca in aralroca/next-translate-plugin#26
• fix client components by @aralroca in aralroca/next-translate-plugin#27
• add tests and some improvements by @aralroca in aralroca/next-translate-plugin#29
• improve loadLocaleFrom detection to allow to change it with hotreloading by @aralroca in aralroca/next-translate-plugin#32
• avoid parsing client components inside node_modules by @aralroca in aralroca/next-translate-plugin#34
• support /[lang] dynamic route by @aralroca in aralroca/next-translate-plugin#36
• fix monorepo with appdir by @aralroca in aralroca/next-translate-plugin#37

Full Next-translate Changelog: 2.0.6...2.3.0
Full Changelog Next-translate-plugin: aralroca/next-translate-plugin@2.0.5...2.3.0

2.3.0-canary.3

What's Changed

• add hoc to fix client components in next-translate-plugin by @aralroca in #1061

Full Changelog: 2.0.6...2.3.0-canary.3

2.0.6

What's Changed

• Allow missing translation in Trans component with components by @aovens-quantifi in #1024
• fix: support spaces when matching tags by @MonstraG in #1055

New Contributors

• @aovens-quantifi made their first contribution in #1024
• @MonstraG made their first contribution in #1055

Full Changelog: 2.0.5...2.0.6

2.0.5

What's Changed

• Allow for falsey default values by @SimplyComplexable in #1021

What's Changed in next-translate-plugin

• Improve app dir detection aralroca/next-translate-plugin@7451605

Full Changelog: 2.0.4...2.0.5

2.0.4

What's Changed

• Removes explicit type restriction on Translate generic by @SimplyComplexable in #1013

Full Changelog: 2.0.3...2.0.4

2.0.3

What's Changed

• Query data doesn't update when I use returnObjects by @alziqziq in #953
• Fix/app directory example by @marcelotk15 in #996
• Update default option in Translate type. by @SimplyComplexable in #931

What's Changed in Next-translate-plugin

• Support Next.js 13 app-dir with pagesInDir config option by @awinogrodzki in aralroca/next-translate-plugin#12

New Contributors

• @alziqziq made their first contribution in #953
• @marcelotk15 made their first contribution in #996
• @SimplyComplexable made their first contribution in #931

Full Changelog: 2.0.2...2.0.3

2.0.2

What's Changed

• Fix NODE_DISABLE_COLORS in client to support fallbackNodePolyfills by @aralroca in #990

Full Changelog: 2.0.1...2.0.2

2.0.1

What's Changed

• Correct typos in README by @felixonmars in #897
• Improve Next 13 app directory docs by @aralroca in #986

What's Changed in Next-translate-plugin

• Fix path for monorepos by @jporsay in aralroca/next-translate-plugin#2
• Add postinstall message by @aralroca in aralroca/next-translate-plugin#3

New Contributors

• @felixonmars made their first contribution in #897

Full Changelog: 2.0.0...2.0.1

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 start without 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

2.0.0-canary.3

What's Changed

• Support Next.js 13 app-dir for server/client pages/components by @aralroca in #982

Full Changelog: 2.0.0-canary.2...2.0.0-canary.3