Optimize Imports cljs require sorting should match clj-kondo

[cmf]

A user reports that Cursive's Optimize Imports action appears to disagree with clj-kondo about require ordering for certain ClojureScript namespaces.

Example

Given these cljs requires:

[goog.crypt.Sha1]
[goog.crypt.base64 :as b64]

Cursive's Optimize Imports command and clj-kondo appear to prefer different ordering.

Expected result

Cursive should sort cljs requires in the same order as clj-kondo, so running Optimize Imports does not create churn or warnings/disagreements with kondo.

Notes

User wording:

Does Cursive do anything to interact with IntelliJ's 'Optimize Imports' command? It seems to work very nicely, except that it and clj-kondo seem to disagree about the ordering of the following cljs requires: [goog.crypt.Sha1] and [goog.crypt.base64 :as b64].

[cmf]

Fix released in 2026.2-eap1 on 2026-05-22.