Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clerk in Babashka fails with "Unable to resolve classname: io.methvin.watcher.DirectoryChangeEvent" #589

Closed
neuhalje opened this issue Dec 9, 2023 · 2 comments

Comments

@neuhalje
Copy link

neuhalje commented Dec 9, 2023

Expected Result

When I use clerk in a babashka project, it works.

Observed Result when running with Clj

It works

Observed Result when running with Babashka

As soon as I reference nextjournal.clerk, I get an error "Unable to resolve classname: io.methvin.watcher.DirectoryChangeEvent".

The same code runs, when started with vanilla Clojure

❯ bb --version
babashka v1.3.186

Source

Source File

(ns clerk1.command
  (:require
   [clojure.string :as string]
   [nextjournal.clerk :as clerk]  ;; Removing this line makes it work
   ))

bb.edn

{
 :deps {name.neuhalfen/babashka-example {:local/root "."}}
} 

deps.edn

{:paths ["src"]
 :deps {dev.weavejester/medley {:mvn/version "1.7.0"}
        metosin/malli {:mvn/version "0.13.0"}

        ;; Testing libraries
        lambdaisland/kaocha {:mvn/version "1.87.1366"}
        org.clojure/test.check {:mvn/version "1.1.1"}

        io.github.nextjournal/clerk {:mvn/version "0.15.957"}
        }

 :aliases {:test {:extra-paths ["test"]
                  :extra-deps {lambdaisland/kaocha {:mvn/version "1.87.1366"}
                               com.taoensso/timbre {:mvn/version "5.2.1"}
                               org.clojure/test.check {:mvn/version "1.1.1"}}
                  :main-opts ["-m" "kaocha.runner"]}}}
@mk
Copy link
Member

mk commented Dec 9, 2023

This is expected as Clerk currently doesn't support babashka. #232 is an old experimental PR in which we explored adding babashka support but we never saw much demand for this and decided it wasn't worth the added complexity at the time. Feel free to chime in there as to why you'd want/need Babashka support.

@mk mk closed this as completed Dec 9, 2023
@neuhalje
Copy link
Author

Thank you! That saved me a lot of time!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants