4 ms·
I'd be careful about introducing more caching to the ClojureScript build process - I've been getting some really strange errors occasionally, the kind that leav
by reitzensteinm 12y ago
I'd be careful about introducing more caching to the ClojureScript build process - I've been getting some really strange errors occasionally, the kind that leave garbled errors in the js that the source maps can't decypher, that disappear after a full clean & rebuild.
I just released a site based on Clojure + Clojurescript, with the front end written in Reagent, and it was a pretty good experience overall. The above was my main issue with the setup.
I've written more about the experience here (it seems there's not much interest in the site here, but at least the writeup should be interesting to those reading this post):
https://news.ycombinator.com/item?id=8791129 https://news.ycombinator.com/item?id=8791129
(Edit: it has since got a few upvotes, only to be killed by I guess the voting ring detection. C'est la vie.)
- swannodette 12y agoThe issues you encountered likely arise from not recompiling dependent namespaces when you change a source file. It's something we'll probably address soon.
- reitzensteinm 12y agoAh, interesting. This was both with the advanced and no optimisations, if that matters? My overall impression was that ClojureScript was already 90% the way there, so you've done a damn fine job of maintaining and pushing the project forward. Thank you very much for that!