loadTranslations fallback leads to infinite loop: "ERR_INVALID_TYPESCRIPT_SYNTAX"

[dupasj]

Search terms

loadTranslations, ERR_INVALID_TYPESCRIPT_SYNTAX, infinite recursion, Windows, locales, require, en.cjs

Expected Behavior

• loadTranslations("en") should load the English translation file and fallback gracefully if a locale is missing.
• IDE should not flag i18n strings like i18n.file_0_changed_restarting() as unresolved.

Actual Behavior

• pnpm build works and doesn't throw errors.
• All the i18n values are flagged as unresolved but my IDE (IntelliJ)
• If I run pnpm test, I have a recursive loop in loadTranslation in src/lib/internationalization/internationalization.ts:69:16:

/**
 * Load TypeDoc's translations for a specified language
 */
export function loadTranslations(lang: string): Record<string, string> {
    // Make sure this isn't abused to load some random file by mistake
    ok(
        /^[A-Za-z-]+$/.test(lang),
        "Locale names may only contain letters and dashes",
    );
    try {
        return req(`./locales/${lang}.cjs`);
    } catch {
        return loadTranslations("en"); // <-- HERE
    }
}

Debug

I edited the try/catch to get the error details:

/**
 * Load TypeDoc's translations for a specified language
 */
export function loadTranslations(lang: string): Record<string, string> {
    // Make sure this isn't abused to load some random file by mistake
    ok(
        /^[A-Za-z-]+$/.test(lang),
        "Locale names may only contain letters and dashes",
    );
    try {
        return req(`./locales/${lang}.cjs`);
    } catch (e) {
        console.log(e)// SyntaxError [ERR_INVALID_TYPESCRIPT_SYNTAX]
        return loadTranslations("en");
    }
}

Environment

• Typedoc version: f60f0a4
• TypeScript version: 5.8.3 (from the project typescript version inthe package)
• Node.js version: 23.6.0
• OS: Windows 11 (french)

[Gerrit0]

This is because you are using Node 23.6.0; which enabled the experimental strip types option by default... while its still experimental... for some reason...

I recommend disabling it. TypeDoc uses tsx to transpile TS syntax, and for some reason tsx doesn't (can't?) happen before Node's incomplete support.

export NODE_OPTIONS="--no-experimental-strip-types"

[Gerrit0]

All the i18n values are flagged as unresolved but my IDE (IntelliJ)

It works in VSCode -- frankly I blame intellij's custom TS intellisense wrapper thing... not something I'm going to spend time fixing as I don't use their products

[Gerrit0]

I was curious how much of a pain it would be for TypeDoc to turn on the erasableSyntaxOnly flag, which would make Node 23 just work with it... it turns out... entirely too much. TypeDoc heavily relies on a ReflectionKind enumeration. As enum is banned, this would require a complete rework to replace it. microsoft/TypeScript#60790 would make this less painful; but still not quite trivial, and would introduce breaking changes.

[dupasj]

I was curious how much of a pain it would be for TypeDoc to turn on the erasableSyntaxOnly flag, which would make Node 23 just work with it... it turns out... entirely too much. TypeDoc heavily relies on a ReflectionKind enumeration. As enum is banned, this would require a complete rework to replace it. microsoft/TypeScript#60790 would make this less painful; but still not quite trivial, and would introduce breaking changes.

I am not sure to understand the question/problematic here. Are you talking about typedoc usage? If yes, I didn't have any issue by using the your built project.

I am not sure to understand the expectation of this issue (feel really specific for me)
Does the expectation is: convert all the literal object who has the assertion 'as enum' into an enum? If yes, I can try to take a look!

[Gerrit0]

I wasn't intending to ask a question/solicit work, just reporting on one attempt I made in finding a way around needing to do export NODE_OPTIONS="--no-experimental-strip-types" on Node 23 to develop TypeDoc.

At this point, I don't have any easy ways of doing this that don't cause other obnoxious symptoms, so am probably just going to put off dealing with it for now.