Dalibor Hon

Just to confirm, wanted to post the same issue. First one isn't related to this package, please see https://github.com/yassinedoghri/astro-i18next/issues/20. I guess it could be added to documentation as a note....

I can confirm that the issue is resolved on my end, although imports got duplicated because of my mistake.

That's great! RFC looks good to me. Anyways is there maybe a workaround over this, besides implementing the detection and or the whole i18next myself? I currently don't have any...

> I think that after [beta.13 release](https://github.com/yassinedoghri/astro-i18next/releases/tag/v1.0.0-beta.13), it's safe to say that this can be closed! 🎉 > > `astro-i18next` now loads 2 separate i18next configs: > > * **server-side**...

I could not find any information on this particular issue elsewhere then this issue and this: https://github.com/lokalise/i18n-ally/issues/443 issue. The issue I'm facing is with the namespace delimiter in the auto...

@jlarmstrongiv Please is this still an issue? I'd like to know before I get to work on a blog, I'd like to have this clarified. I'm assuming that it still...

> @jlarmstrongiv Please is this still an issue? I'd like to know before I get to work on a blog, I'd like to have this clarified. I'm assuming that it...

I've now encountered another issue which comes with Astro 5 and this integration. I'm using node adapter and the files are built into `dist` whereas astro with node builds client...

I just want to drop this here, there is a way to fetch remote markdown (probably not officially supported) with the [`@astrojs/markdown-remark`](https://github.com/withastro/astro/tree/main/packages/markdown/remark) package with frontmatter and headings. My only worry...