squint

wcohen 2026-04-28T00:27:44.592909Z

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?

borkdude 2026-05-11T12:50:41.281789Z

merged in clj-kondo

1
wcohen 2026-05-11T13:35:29.441339Z

thank you!

Chris McCormick 2026-05-08T12:46:18.184729Z

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.15

Chris McCormick 2026-05-08T12:49:44.875599Z

Sorry if I am jumping the gun here, just excited about the new await!

borkdude 2026-05-08T15:18:47.947219Z

Still gotta do this. Little time in this bb conf weekend :)

borkdude 2026-04-28T10:16:11.764019Z

I think I'll fix this in clj-kondo now that async/await will soon be published in CLJS (either this or next week)

borkdude 2026-04-28T10:16:38.146519Z

or better yet, it'll fix itself when I bump the built-in CLJS analysis in clj-kondo :)

wcohen 2026-04-28T10:55:03.397029Z

Even better!

Miguel Munoz 2026-04-28T00:31:36.931969Z

a PR makes sense, but keep it minimal and targeted

Miguel Munoz 2026-04-28T00:32:02.399179Z

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

wcohen 2026-04-28T00:55:42.579389Z

Done: https://github.com/squint-cljs/squint/pull/814

🙌 1
✅ 1
Chris McCormick 2026-05-10T03:47:43.115759Z

Enjoy the conf! 🎉