Clojurians Log v2

that is usually a sign that Cursive can't see your dependencies, or those dependencies are missing clojure/clojurescript

make sure to enable any given aliases in Cursive when using deps.edn with aliases

Hmm, I've found the cause... It's in the clj/cljs switch on the right, for some reason, the language server doesn't switch to cljs mode after typing shadow/repl... Probably a bug? If I set the mode to cljs and then restart the REPL, the clj mode is back, but it stays that way.

But the REPL works, it just doesn't resolve anything from clojurescript...

@cfleming Can I get your view on this?

> integrating TypeScript language server into clojure-lsp Can you elaborate @roman01la? Would it mean being able to use type information from TS classes in ClojureScript?

@grav Yes, this will require a mapping layer to generate JS from a sexp under cursor + turn ns requires into js imports. Once all of that is sent to TS server it will respond with a list of completion tokens

(.| js/document) -> document.|

(ns :require [react]) -> import * as react from "react"
(react/|) -> react.|

type information can be also used to enrich inference in cljs code, this can be done in cljs compiler as well btw, not only in the editor

I see, you'd convert before calling LSP, interesting. I know a couple of plugin devs who are right down the LSP rabbit hole, I'll ask them for advice.

Correct. This should work for simple cases like the above, but more complex code where one location references the other one could be less straightforward

(let [x js/obj]
  (.| x))

Yes, I know this is a pain point and I'm planning to make another round of improvements here soon. The issue with LSP is that I don't think it exposes the functionality that Cursive needs, but I can look at it again. The same is true of the built-in IntelliJ JS functionality, it all relies on having source files that look roughly like JS/TS, so it works ok for something like Coffeescript but not for ClojureScript.