Bug 512101 - TypeScript language server 5.1 does not work with Kate
Summary: TypeScript language server 5.1 does not work with Kate
Status: RESOLVED DUPLICATE of bug 511669
Alias: None
Product: kate
Classification: Applications
Component: part (other bugs)
Version First Reported In: 25.08.3
Platform: CachyOS Linux
: NOR major
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-11-14 22:00 UTC by Karmo Rosental
Modified: 2025-11-20 17:04 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Karmo Rosental 2025-11-14 22:00:24 UTC 
SUMMARY
TypeScript Language Server 5.1 has no type info and no autocomplete in Kate. TypeScript language server 5.0 is working perfectly.

STEPS TO REPRODUCE
1. Install TypeScript Language Server 5.1
2. Enable LSP Client plugin in Kate settings
3. Open some TypeScript project in Kate

OBSERVED RESULT
There is no type info when hovering over variables, functions etc. Autocomplete does not work anywhere in the code.

EXPECTED RESULT
Type info is displayed when hovering over variables is displayed. Autocomplete works when typing code.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 6.5.2
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0

ADDITIONAL INFORMATION
When I downgrade TypeScript Language Server to 5.0 then mentioned problems disappear.
Comment 1 Christoph Cullmann 2025-11-20 16:42:35 UTC 
Could you report that upstream to the TypeScript language server?
If the old version works but the new is broken that might be an issue on their side.

You can get more info what happens if you first export the env var LSPCLIENT_DEBUG with 1 and the start kate with -b

export LSPCLIENT_DEBUG=1
kate -b
Comment 2 Waqar Ahmed 2025-11-20 17:04:00 UTC 
This is already fixed https://invent.kde.org/utilities/kate/-/commit/4446f148d340176aeda2ac3980f7b04a0b9ec7a8

*** This bug has been marked as a duplicate of bug 511669 ***