This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-04-14
Channels
- # announcements (2)
- # beginners (88)
- # calva (17)
- # cider (25)
- # cljdoc (22)
- # cljs-dev (10)
- # clojure (194)
- # clojure-italy (1)
- # clojure-nl (8)
- # clojurescript (24)
- # data-science (11)
- # datomic (1)
- # fulcro (6)
- # jobs (1)
- # leiningen (4)
- # nyc (1)
- # off-topic (70)
- # pedestal (6)
- # quil (4)
- # shadow-cljs (59)
- # vim (8)
hey ya’ll. really impressed with cljdoc. having some issues with a lib I’d like to have on here
I literally just saw the failing build 🙂
Unfortunately I don't have a good answer to this problem currently. cljdoc's analysis builds on the jar/pom only.
I could maybe include cljsjs/react
. I’d prefer to allow the consumer to include React however they see fit
Maybe there's a way we can tell the CLJS analyzer to silently ignore string requires, I think that should work (those always refer to npm stuff right?)
Hope somebody gets what I'm trying to say 😄
It looks at node_modules
and creates some input for the analyzer based on that.
But we don't know what node_modules
should look like since we only look at the pom.xml
In a sense a library like clinch doesn't perfectly declare it's dependencies because react is sort of coming out of another package manager
Would be interesting to see how this problem could be solved in general but I guess it hasn't been too much of an issue so far
@martinklepsch I created an example not too long ago that showed how to deal with string requires easily. I can't remember where I put it though.
Now that you say it this rings a bell! I’ll try do look that up in the logs next weekend after Clojure/north. @lilactown if you want to open an issue against cljdoc that would be great, then we can’t forget (as I apparently did before :D)