This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-01-10
Channels
- # announcements (4)
- # babashka (40)
- # beginners (39)
- # calva (16)
- # cljdoc (1)
- # cljs-dev (8)
- # clojure (72)
- # clojure-europe (10)
- # clojure-losangeles (1)
- # clojure-nl (4)
- # clojure-spec (9)
- # clojure-uk (12)
- # clojurescript (16)
- # community-development (15)
- # conjure (5)
- # cursive (5)
- # datomic (26)
- # eastwood (1)
- # emacs (7)
- # events (1)
- # figwheel-main (15)
- # fulcro (27)
- # graphql (7)
- # gratitude (4)
- # introduce-yourself (1)
- # malli (4)
- # meander (4)
- # off-topic (2)
- # other-languages (13)
- # polylith (7)
- # reagent (5)
- # reitit (5)
- # shadow-cljs (27)
- # spacemacs (4)
- # sql (3)
- # tools-deps (6)
- # xtdb (13)
👋 So some time ago, I finally took some time to figure out what was happening with an exception thrown by cursive. Context is: sometimes I work on JS projects where there is no clojure code. The node_modules still get parsed by cursive. And I get errors like that:
It took me some time to realise that cursive was not really at fault. It’s just that the JS library in question is malformed and has most certainly a bug
The way i “solve” (= make sure cursive does not throws an exception anymore) is by overriding the file type to plain text:
Works for me because i don’t care that this nested node_module dependency is not analyzed by Intellij.
I think a note in the troubleshooting section of cursive’s user guide would be helpful to others 😉