microsoft/TypeScript

🔎 Search Terms find all references, references, import from keyword, default import, unsaved edit, language server, tsc --lsp, stale results 🕗 Version & Regression Information This changed between versions 6.0.3 and 7.0.2: with 6.0.3 (through typescript-language-server 6.0.0) both cases below return the same single location; with 7.0.2 the result depends on the edit. Tested with TypeScript 7.0.2 (tsc --lsp --stdio from the typescript 7.0.2 npm package), macOS 27 on Apple silicon. 7.0.2 is still the newest TypeScript 7 release (checked 2026-09-28); reproduces on it again in 3 of 3 runs. ⏯ Playground Link No response (needs a repository with several tsconfig projects and the language server) 💻 Code // react-hook-form/react-hook-form at 5fd9ef65290bef2ccaa7ac96dc8d5d55478b5410, dependencies installed with pnpm install // src/__tests__/logic/getValidateError.test.ts, lines 1 and 2 // (find all references is requested on `from` in line 2, column 15) import getValidateError fro

🔎 Search Terms non-module, script, jsx, jsxImportSource 🕗 Version & Regression Information This is the behavior in every version I tried, and I reviewed the FAQ for entries about jsx ⏯ Playground Link No response 💻 Code const x = <><div>hi</div></> 🙁 Actual behavior This JSX tag requires the module path '@solidjs/web/jsx-runtime' to exist, but none could be found. Make sure you have types for the appropriate package installed.ts(2875) JSX element implicitly has type 'any' because no interface 'JSX.IntrinsicElements' exists.ts(7026) 🙂 Expected behavior I do have that package installed. The error message should give the real issue which is that scripts can't import modules. Additional information about the issue workaround: export {}

🔎 Search Terms declarationMap empty mappings, tsgo declaration map default export, d.ts.map mappings empty 🕗 Version & Regression Information This changed between versions 6.0 and 7.0 ⏯ Playground Link Playground Link 💻 Code const b = 1; const d = 2; export default { b, d }; 🙁 Actual behavior main.d.ts.map: {"version":3,"file":"main.d.ts","sourceRoot":"","sources":["main.ts"],"names":[],"mappings":""} mappings is an empty string, so the map can't resolve any position in main.d.ts back to main.ts. 🙂 Expected behavior Same as [email protected] on the same input: {"version":3,"file":"main.d.ts","sourceRoot":"","sources":["main.ts"],"names":[],"mappings":";;;;AAEA,wBAAwB"} main.d.ts is byte-identical between tsgo and [email protected] — only mappings differs. Additional information about the issue Replacing the object-literal default export with a named identifier (const foo = { b, d }; export default foo;) produces correct, non-empty mappings under tsgo. The empty mappi

⚙ Compilation target ESNext ⚙ Library ESNext Missing / Incorrect Definition TypeScript/tsc/internal/bundled/libs/lib.esnext.temporal.d.ts Line 320 in 0b832e1 toLocaleString(locales?: Intl.LocalesArgument, options?: Intl.DateTimeFormatOptions): string; Sample Code TypeScript allows the following code, when it should not. Temporal.Now.zonedDateTimeISO("America/Chicago").toLocaleString(undefined, { timeZone: "Europe/Berlin" }); Result Engine Error JavaScriptCore TypeError: ZonedDateTime.toLocaleString does not accept a timeZone option; the ZonedDateTime's time zone is used SpiderMonkey TypeError: can't set option timeZone when Temporal.ZonedDateTime.toLocaleString is used V8 TypeError: Invalid time zone specified: America/Chicago Documentation Link According to MDN: The timeZone option must not be provided, as it is automatically set to be the date-time's ti

🔎 Search Terms TS2354, "requires an imported helper", tslib private field, importHelpers ES2022, classPrivateFieldGet ES2022, classPrivateFieldSet ES2022, classPrivateFieldIn, ClassAndClassElementDecorators, LanguageFeatureMinimumTarget, private field tslib not needed, importHelpers private field false positive, private field decorator target ESNext 🕗 Version & Regression Information This is the behavior in every version I tried, and I reviewed the FAQ (no entries about tslib, importHelpers, or private fields exist there). Reproduces on every TypeScript version from 4.3.5 (when native #private fields and the ES2022 target were introduced) through the current 7.0.2 and the 7.1.0-dev nightly — i.e. every version able to target ES2022. Not a regression introduced at any specific version, but the mechanism changed once, without changing the observable behavior: TS 4.3.5 through 5.4.5 used a blunt, unconditional if (languageVersion < ScriptTarget.ESNext) guard around the private-fi