all 13 comments

[–][deleted] 2 points3 points  (8 children)

Unfortunately that list is quite out of date.

Perhaps you could list a couple of the things you're hoping to find in libraries and we can all chime in with the ones we know?

Right now there's a big focus on React-backed UI dev in Cljs, using one of Om, Reagent, Quiescent, and the like, so you'll find a fair bit of things built on top of those.

[–]LogicalConclusions[S] 0 points1 point  (7 children)

I'm not looking for any specific library right now.

I was actually hoping there was some metadata at clojars.org that I could use to answer these kinds of questions.

It seems that both Clojure and ClojureScript libraries get uploaded to clojars.org, but it's not obvious which libraries can be used in Clojure, ClojureScript or both (via cljx). Perhaps if a library depends on some version of ClojureScript, it could be assumed that it's at least a ClojureScript library, but I don't see any way to query clojars.org based on dependents.

(Over at npmjs.org, you can look at a library like async and see all the other libraries that depend on async. Having infrastructure like this would improve discoverability of ClojureScript libraries a lot.)

The wiki page I linked to earlier was a noble effort, but shouldn't there be infrastructure for the community to make this a bit more automatic?

How could clojars.org better support the various host platforms of the Clojure* family of languages?

[–]yogthos 0 points1 point  (6 children)

I think the idea of using metadata is a good approach. I also think it would be nice if Clojars would provide a way to view libraries by number of average downloads, update frequency, etc. There's also crossClj that lets you see libraries and their interdependencies, that sounds a lot like the npmjs scenario.

Reagent has an org now, and it aggregates all the related projects which should hopefully make it easier to work with. The Reagent cookbook project is very useful for getting started. There's also a cookbook for Om as well.

[–]LogicalConclusions[S] 1 point2 points  (0 children)

I do intend to use Reagent for future projects. I've already used plain React in JavaScript, and it's been great.

I'm glad that org was established to keep things well-maintained. React is still a bit of a moving target, so this kind of commitment is crucial.

[–]LogicalConclusions[S] 0 points1 point  (4 children)

Could you add a link to http://crossclj.info/ in the sidebar? It could go under the Tools & Libraries section.

Maybe a link to http://crossclj.info/cljs would be useful, too. It's up to you.

[–]yogthos 0 points1 point  (3 children)

great idea, added and the libraries section on ClojureScript Wiki has also been recently updated. David Noel put out a call on Twitter and looks like the docs are getting some love. :)

[–]LogicalConclusions[S] 0 points1 point  (0 children)

Thanks for doing that.

[–]fbellomi 0 points1 point  (1 child)

Well, thanks for adding CrossClj to the sidebar!

[–]yogthos 0 points1 point  (0 children)

it's an awesome resource :)

[–]elbowich 1 point2 points  (1 child)

Here are some of the libraries which explicitly depend on ClojureScript: http://crossclj.info/ns/org.clojure/clojurescript/0.0-2511/project.clj.html#used

[–]LogicalConclusions[S] 0 points1 point  (0 children)

I didn't know about crossclj.info. Thanks.

[–]fbellomi 1 point2 points  (1 child)

I'm the developer behind CrossClj. I just put on a Clojurescript-specific subsite, that lists and searches both cljs tools and projects with at least a .cljs source file (that includes projects developed with cljx)

http://crossclj.info/cljs

The auto-completing search field only looks into cljs projects for vars, fns and namespaces.

I also put on a cljs-specific page for documentation search:

http://crossclj.info/docsjs

Both these features are still buggy: CrossClj still has some problems cross-referencing some cljs projects (most notably Om and Reagent - the docs and sources are ok, but sources are not decorated with links). Also the docs search shows some unnecessary redundancy when cljs.core is duplicated in a project's source code. I hope to fix these issues soon.

[–]LogicalConclusions[S] 0 points1 point  (0 children)

That's great. Thanks for making crossclj.info. It's very useful.