Aral Roca Gomez
Aral Roca Gomez
@bbolek fixed on [2.3.0-canary.2](https://github.com/aralroca/next-translate-plugin/releases/tag/2.3.0-canary.2), can you verify it? Thanks!
Thanks for the comment, is possible to upload the reproducible failing case in some repo to help to fix It? Thanks!
@bbolek looks fixed in: - `next-translate` version `2.3.0-canary.3` (you also need to update this one) - `next-translate-plugin` version `2.3.0-canary.3`
I realised that is not supported. Feel free to do a PR to support this feature. You need to touch this line of code: https://github.com/aralroca/next-translate-plugin/blob/9ad6592f10cfa90da4f7d0bc20032831a220b6af/src/index.ts#L78 I'm going to move this...
Thanks @rolandjlevy, I recommend you start with the failing test and do "yarn test". In order to try inside a local project, you need to run "yarn build", and in...
Feel free to PR to adapt this config property https://github.com/aralroca/next-translate/blob/master/src/plugin/index.ts#L5
> any updates? Faced with same problem when adding next-translate plugin to next.config > > next-translate plugin overrides nextConfig > > ``` > const nextTranslate = require('next-translate'); > const nextConfig...
Ok, make sense in order to avoid the behavior with HOC. Feel free to PR
Node version `v14.15.5`
Thanks @tomByrer, in Brisa's framework you can try it with a JSX property: https://brisa.build/api-reference/extended-props/renderOn#renderonbuild-or-runtime