Expose compiler option allowNonTsExtensions

Search Terms

allowNonTsExtensions

Suggestion

Make allowNonTsExtensions from
https://github.com/Microsoft/TypeScript/blob/0010a38660b1eb03c188c9c1758177b4501760b7/src/compiler/types.ts#L4480
public / not-internal

Use Cases

The Monaco Editor requires usage of this compiler option for in-memory TypeScript / JavaScript editors.

Examples

https://github.com/Microsoft/monaco-editor/blob/35f3f99ff251744eabe4dfbff8535288e363933d/test/playground.generated/extending-language-services-configure-javascript-defaults.html#L53

Checklist

My suggestion meets these guidelines:

• [✔️] This wouldn't be a breaking change in existing TypeScript/JavaScript code
• [✔️] This wouldn't change the runtime behavior of existing JavaScript code
• [✔️] This could be implemented without emitting different JS based on the types of the expressions
• [✔️] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
• [?] This feature would agree with the rest of TypeScript's Design Goals.

Start with allowNonTsExtensions in src/compiler/types.ts at the referenced declaration, then compare how the Monaco Editor example consumes the option. Make the option publicly available as requested and verify that the public compiler API exposes it for the in-memory editor use case.