The ‘const’ keyword is extraneous in the ParseKeys type definition.

[aimidy]

🐛 Bug Report

'const' modifier can only appear on a type parameter of a function, method or class

const Context extends TOpt['context'] = TOpt['context'],

To Reproduce

node_modules\i18next\typescript\t.d.ts

export type ParseKeys<
  Ns extends Namespace = DefaultNamespace,
  TOpt extends TOptions = {},
  KPrefix = undefined,
  Keys extends $Dictionary = KeysByTOptions<TOpt>,
  ActualNS extends Namespace = NsByTOptions<Ns, TOpt>,
  const Context extends TOpt['context'] = TOpt['context'],
> = $IsResourcesDefined extends true
  ? FilterKeysByContext<
      | ParseKeysByKeyPrefix<Keys[$FirstNamespace<ActualNS>], KPrefix>
      | ParseKeysByNamespaces<ActualNS, Keys>
      | ParseKeysByFallbackNs<Keys>,
      Context
    >
  : string;

Expected behavior

export type ParseKeys<
  Ns extends Namespace = DefaultNamespace,
  TOpt extends TOptions = {},
  KPrefix = undefined,
  Keys extends $Dictionary = KeysByTOptions<TOpt>,
  ActualNS extends Namespace = NsByTOptions<Ns, TOpt>,
  Context extends TOpt['context'] = TOpt['context'],
> = $IsResourcesDefined extends true
  ? FilterKeysByContext<
      | ParseKeysByKeyPrefix<Keys[$FirstNamespace<ActualNS>], KPrefix>
      | ParseKeysByNamespaces<ActualNS, Keys>
      | ParseKeysByFallbackNs<Keys>,
      Context
    >
  : string;

Your Environment

• runtime version: i.e. node v20
• i18next version: i.e. 23.11.0
• os: Windows

[ing-chiba]

same here

[marcalexiei]

I'll take a look at this issue later.

I think that the issue is present when compilerOptions.skipLibCheck is false.
Right it is set to true, so that's why test haven't catch it:

i18next/tsconfig.json

Line 15 in e8efbf0

"skipLibCheck": true