Skip to content

About

Experimental IntelliJ platform plugin for the xemantic-typescript-compiler

Resources

Code of conduct

Contributing

Stars

1 star

Watchers

0 watching

Forks

Repository files navigation

xtsc-intellij-plugin

TypeScript code insight for IntelliJ-based IDEs, backed by xtsc — the TypeScript compiler rewritten from scratch in Kotlin.

Build Version Downloads

license GitHub last commit discord users online Bluesky

Warning

Early development. Error highlighting works; everything else below is still the scaffold generated from the IntelliJ Platform Plugin Template, and the plugin has not been published to JetBrains Marketplace.

What works

Errors reported by xtsc are highlighted in .ts, .tsx, .mts and .cts files that sit under a tsconfig.json, against the editor's buffer rather than what is on disk — so an error appears as you type it, without saving.

The compiler runs in the IDE process. Because it is built against Kotlin 2.4 metadata and kotlinx-coroutines 1.11, the plugin requires IntelliJ IDEA 2026.2 or newer and relocates the compiler's kotlinx packages away from the ones the IDE bundles; see CLAUDE.md for why each of those is load-bearing.

Why?

Every TypeScript-aware editor talks to tsserver: a Node.js process on the other side of a protocol boundary, serializing questions out and answers back.

xtsc is a whole-program TypeScript type checker written in Kotlin, and its API is an ordinary function call — open a project, push unsaved editor buffers into it, ask it questions:

project.updateFile(path, editorBuffer)  // never touches disk
project.quickInfoAt(file, offset)       // hover
project.definitionsAt(file, offset)     // go to definition
project.completionsAt(file, offset)     // completions

Running on the JVM, it can be embedded directly in the IDE process. This plugin is that embedding: no Node.js runtime, no tsserver child process, no language server protocol in between.

Planned capabilities

  • Whole-program type checking driven by tsconfig.json
  • Hover, go to definition, find usages, completion and signature help
  • Rename that is re-checked before it is applied
  • Diagnostics matching those reported by tsc

Installation

Once the plugin is published to JetBrains Marketplace:

  • Using the IDE built-in plugin system:

    Settings/Preferences > Plugins > Marketplace > Search for "xtsc" > Install

  • Using JetBrains Marketplace:

    Go to JetBrains Marketplace and install it by clicking the Install to ... button in case your IDE is running.

    You can also download the latest release from JetBrains Marketplace and install it manually using Settings/Preferences > Plugins > ⚙️ > Install plugin from disk...

  • Manually:

    Download the latest release and install it manually using Settings/Preferences > Plugins > ⚙️ > Install plugin from disk...

Development

./gradlew runIde        # launch a sandbox IDE with the plugin installed
./gradlew check         # compile and run the tests
./gradlew verifyPlugin  # plugin structure checks and the IntelliJ Plugin Verifier
./gradlew buildPlugin   # produce the distributable ZIP in build/distributions

The same three tasks are also available as the Run Plugin, Run Tests and Run Verifications run configurations shipped in .run.

Every change goes through the Build workflow, which builds, tests, verifies, and refreshes a draft GitHub release. Publishing that draft triggers the Release workflow, which signs the plugin, uploads it to JetBrains Marketplace, and opens a pull request moving the Unreleased section of CHANGELOG.md under the released version.

Markdown soft-wrapping in the IDE

Markdown sources here use semantic line breaks and are never hard-wrapped, so long paragraphs read best with soft wrapping enabled:

Settings/Preferences > Editor > General > Soft Wraps > check Soft-wrap these files and make sure the file mask includes *.md.

Before the first Marketplace release

These steps need a human with the relevant accounts, and are not done yet:

  • Review the Legal Agreements.
  • Add a plugin icon at src/main/resources/META-INF/pluginIcon.svg (and a dark variant, pluginIcon_dark.svg).
  • Publish the plugin manually for the first time — Marketplace will not accept an automated upload of a plugin it has never seen.
  • Replace MARKETPLACE_ID in the badges and installation links above with the ID assigned at publication.
  • Set the Plugin Signing secrets — PRIVATE_KEY, PRIVATE_KEY_PASSWORD and CERTIFICATE_CHAIN — in Settings > Secrets and variables > Actions.
  • Set the Deployment Token as the PUBLISH_TOKEN secret.
  • Enable Read and write permissions in Settings > Actions > General > Workflow permissions, so the Release workflow can open the changelog pull request.
  • Click Watch on the IntelliJ Platform Plugin Template to be notified about releases containing new features and fixes.

License

Copyright 2026 Kazimierz Pogoda / Xemantic

Licensed under the Apache License, Version 2.0.


Plugin based on the IntelliJ Platform Plugin Template.

About

Experimental IntelliJ platform plugin for the xemantic-typescript-compiler

Resources

Code of conduct

Contributing

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages