Testing Self-hosted ClojureScript

[lread]

Currently...

We use planck to test that rewrite-clj works as expected in self-hosted ClojureScript.

But...

Planck is not actively maintained these days.
It can be a bit of a chore to get planck working on current OS versions.
(Case in point, I've moved to MX Linux 25 and don't have a working version of planck).

Option 0: Carry on Old Chaps

Continue to get planck working on current OS versions.

Pros:

• no changes to tests

Cons:

• Planck uses an older version of ClojureScript
• maintenance burden

Option 1: Drop Self-Hosted ClojureScript testing

Do folks really use self-hosted CloureScript?
Do we really need to test for that?

Pros:

• Less to maintain

Cons:

• Loss of test coverage for a ClojureScript variant

Option 2: Maintain Planck

Step up and offer help to get Planck working on modern OSes with current ClojureScript release.

Cons:

• Significant effort.
• Is Planck still relevant today?

Pros:

• no changes to tests

Option 3: Test Self-Hosted ClojureScript differently

Don't use Planck to test self-hosted ClojureScript.
Figure out how to test self-hosted ClojureScript with ClojureScript.
Maybe this is easy? Or at least, simple?

Pros:

• learn something new
• could also test on Windows (Planck does not run on Windows)

Cons:

• not sure yet.

Thoughts

I think I'll take a crack at option 3 first.

[borkdude]

Has there ever been a bug that only occurred with self-hosted but not with regular CLJS? Does rewrite-clj contain any self-hosted specific code? If not, then it might not be worth it to test self-hosted TBH

[lread]

I don't think there were any tweaks for self-hosted cljs, but honestly, I don't remember.
A search through the git logs isn't showing anything obvious.

I'll sleep on it.

[lread]

I'll start with option 1b: disable planck testing.

This will allow me to run tests locally on my dev box.

I can consider other options later.