Fork me on GitHub

it turns out that lein correctly reports some compiler fail, but boot-cljs doesn't. i made a minimal poc at:


@juhoteperi you seemed interested, maybe you want to have a look it


is there any way to get a list of the namespaces required by a namespace? it’s possible to get those whose require clause uses :as or :refers, but i don’t see how to detect e.g. (:require []).


never mind, it looks like ns-map will do the trick for my purposes.


Has anybody built a Mr. Anderson equivalent for boot?


mmm...not that I know of


@alandipert and @micha would you be interested in having a boot-maintained version of cemerick/pomegranate? I have upgraded aether in there but I don't know if things have been merged lately.


I am using in another project as well, but I thought I might ask here as well before deploying my own fork


@richiardiandrea are there tings we need in the new aether version?


@micha there is a substantial changelog yes, but I haven't investigated implications in boot. But I will. In general the whole redesign of Aether might have sped up things (or not), it is worth having a look for sure. Link ->


btw my patch upgrades to 1.1.0 quite painlessly, I am using it in a maven plugin that resolves clojure dependencies


was 1.1.0 the version where they changed a bunch of names?


@micha no they changed names before 1.1.0, which now has new name and many fixes


there is a nice fix: DefaultRepositorySystem.resolveDependencies() fails with NPE when dependency collection fails early and yields not even a root node


we could triage it, I will probably need to deploy it to clojars anyways, if they don't merge it in cemerick/pomegranate


I also understand the "it is another thing maintain" counter-argument though 😄


This is also nice > Currently, the checksums retrieved during artifact resolution are stored locally next to the actual data file. I doubt that many applications have use for those files so it would be nice to have an option to not persist the checkums locally, thereby saving a few inodes/blocks (I personally have ~27,000 checksum files in my local repository, occupying > 100 MB of disk space for what's actually just 1 MB of real data)


or > Cyclic dependencies indicate a flaw in the project setup of the affected artifacts that should be communicated to the end user to enable him to fix the problem. Whether cycles are generally tolerated and only cause warnings or denote errors is up to the application to decide but Aether needs to report cycles while building a dependency graph.


Ok I'll stop spamming 😄


Last one: "Version ranges with non-snapshot bounds should not resolve snapshot versions"


hey all, I'm trying to follow using boot, but am running into WARNING: Unsupported preprocess value :jsx for foreign library src/js/hello.js. null


@skynet I am not 100% of what I am about to say and I would ping Juho for confirming it, but boot-cljs might run in a pod, which means that it does not "see" the defmethod you have in boot.user


A quick test you could try is to add it to some namespace in your src


that would explain it, I'll try to find how to add it to the pod, thanks


yeah it looks to me like boot-cljs creates a pod for the compiler, so it may be impossible to add a preprocessor without modifying it