This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # 100-days-of-code (5)
- # announcements (13)
- # beginners (98)
- # boot (19)
- # cider (10)
- # cljdoc (32)
- # clojure (142)
- # clojure-dev (37)
- # clojure-italy (3)
- # clojure-nl (2)
- # clojure-spec (30)
- # clojure-uk (18)
- # clojurescript (28)
- # cursive (8)
- # datomic (25)
- # duct (18)
- # editors (5)
- # emacs (39)
- # events (4)
- # figwheel (7)
- # figwheel-main (5)
- # fulcro (38)
- # graphql (19)
- # jobs-discuss (1)
- # jobs-rus (7)
- # keechma (1)
- # lumo (47)
- # off-topic (28)
- # om-next (3)
- # parinfer (3)
- # re-frame (18)
- # reagent (37)
- # reitit (8)
- # shadow-cljs (101)
- # specter (7)
- # tools-deps (8)
- # vim (1)
@avichalp @rodolfo I invited you to the cljdoc GitHub team, please accept so I can bug you for code reviews 😄 https://github.com/orgs/cljdoc/teams/cljdoc-community
@martinklepsch feel like discussing the JUXT tooling is off topic for #boot, but I'm happy to help you out with combining kick and pack to do what you want 😊
btw, this might be a good thing to do for pack as well (required for Java9+): https://github.com/martinklepsch/clj-http-lite/commit/3f41fc53a1b692549c88a8602e753cfb887330ae
@martinklepsch ties together figwheel/cljs/shadow/sass into a config, with reloading and minimal touching. Successor to krei.
do you just use
-Spom for that? I tried and it needs some manual adjustments because some directories get skipped making it a bit cumbersome
The directories probably aren't important for uploading to Clojars, if you use pack.
Sorry if I'm being a diva here, I just can't believe that this isn't dead easy yet 😄
But I guess that's mostly due to people using it for apps and using other tools.deps stuff that's incompatible with jars (git checkouts etc.)
My current approach looks something like this:
Then in prod untar, cd, clj -m ...
./script/parcel build git archive HEAD -o /tmp/cljdoc.tar tar -rvf /tmp/cljdoc.tar resources
the additional tar append is to include the compiled JS files (which potentially should go into a different directory than regular resources)
I just trigged the build for instaparse (https://circleci.com/gh/martinklepsch/cljdoc-builder/5739#tests/containers/0) and it succeeded, but https://cljdoc.xyz/d/instaparse/instaparse/1.4.9 is still empty. What went wrong there?
In this case the error occurred on the cljdoc server while processing the Git repo or importing the data into the database. There's an issue to store these issues in the database so that the stacktrace can be shown on the builds page: https://github.com/cljdoc/cljdoc/issues/111
@U44SHEP4N the issue with instaparse is that it uses https://github.com/aengelberg/cljsee and always has
.cljc files for each namespace. The analyzer then duplicates those namespaces in the analysis result because it discovers namespaces via files...
@martinklepsch Ah thanks for the explanation. Should I create an issue for this? I'm just scanning through one of my projects and try to create the docs for all the deps. I think only instaprase, timbre and specter are not working (when semantic-csv is working).
unfortunately source links for Clojure are broken because the Clojure sources aren't on GitHub
Looks good 🙂. Btw. cljdoc is awesome and your handling/encouragement of new contributors fantastic!