Jan Amann
Jan Amann
I'll close this now in favor of #653. This issue is mentioned there and will be taken care of.
Many thanks to everyone proposing to help so far! 🙌 ❤️❤️ > Is there a PR for this already? Not yet. The current situation is that the docs are still...
Hey @joaopbnogueira, so you're not using `useTranslations` in any Client Components? There's a bit of tree shaking in place that helps when e.g. only navigation APIs are used in Client...
I see! `@formatjs/intl-localematcher` is btw. only used in the middleware, so I think you could keep that. https://github.com/amannn/next-intl/issues/962 should be the proper solution to your use case to handle plain...
I've also added an upstream bug report: https://github.com/mixu/minilog/issues/47
Also, this warning is printed every time traverson is used in Next.js: https://github.com/traverson/traverson/blob/73c7bc095b5a852413f188df3949425262046942/lib/json_adapter.js#L11-L12 Is it possible to just get rid of it?
@basti1302 Any chance this could be addressed?
This might be a duplicate of https://github.com/amannn/action-semantic-pull-request/issues/257
> That library also appears to be 8 years without an update so not much point in trying to fix that. [`conventional-commits-parser`](https://www.npmjs.com/package/conventional-commits-parser)? It looks actively maintained to me, no?
Hmm, interesting. If you'd be interested in analyzing this and potentially setting up a PR, I'd be happy to review it. The only thing we document is that the types...