I’m regularly hitting kondo linting noise in cljs/cljc files that use js-await (or I guess the upcoming await !) as well. Seems like I can solve it on a case by case using something like {:linters {:unresolved-symbol {:exclude [js-await await]}}} in a clj-kondo local setting. Would it be worth a PR to squint to pop that in resources/…/config.edn for users of squint/cherry, or would you prefer to just have people handle it locally?
merged in clj-kondo
thank you!
Did this make it into clj-kondo? Or do I need to delete a cache or something?
$ clj-kondo --lint testing/main.cljs
testing/main.cljs:12:12: error: Unresolved symbol: await
linting took 10ms, errors: 1, warnings: 0
$ clj-kondo --version
clj-kondo v2026.04.15Sorry if I am jumping the gun here, just excited about the new await!
Still gotta do this. Little time in this bb conf weekend :)
I think I'll fix this in clj-kondo now that async/await will soon be published in CLJS (either this or next week)
or better yet, it'll fix itself when I bump the built-in CLJS analysis in clj-kondo :)
Even better!
a PR makes sense, but keep it minimal and targeted
I’d lean toward adding this to squint/cherry’s shipped clj-kondo config. js-await/`await!` are effectively part of the user-facing surface area, so requiring every consumer to locally suppress :unresolved-symbol just creates repetitive noise and friction
Enjoy the conf! 🎉