Skip to content

Starlight overrides the defaultNS type definition of i18next so it conflicts with other i18next type definitions. #2742

Open
@lhr0909

Description

@lhr0909

What version of starlight are you using?

0.30.0

What version of astro are you using?

5.1.1

What package manager are you using?

pnpm

What operating system are you using?

Mac

What browser are you using?

Chrome

Describe the Bug

I was integrating i18next into my Astro site with Starlight and found that the TypeScript compiler will force the defaultNS field for any i18next instance to be 'starlight', which will make the t function type errors if the keys don't match.

Link to Minimal Reproducible Example

https://stackblitz.com/edit/github-ytqftcmh?file=src%2Fpages%2Ftest.astro

Participation

  • I am willing to submit a pull request for this issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions