Hi all,
I'm working on CLJS symbol resolution for Cursive. There are a lot of
corners where it's hard to figure out from the doc how they should work -
I've looked through the code but I'm not sure I've got it all right.
1. I've seen several times in the group here that / should only be used
Another one - I've seen some forms like (goog.typeOf x), which implies that
JS root objects can be used directly? This is something I haven't seen
documented anywhere.
On 8 June 2014 21:55, Colin Fleming colin.mailingl...@gmail.com wrote:
Hi all,
I'm working on CLJS symbol resolution for
I don't think we want cut such a release just yet. I think it would be more
informative to understand what's holding people off of 1.6.0.
David
On Sat, Jun 7, 2014 at 4:42 PM, Joshua Ballanco jball...@circleci.com
wrote:
At the risk of suggesting something completely heretical…
Would it be
1.6.0 branch is ready to be tested
http://github.com/clojure/clojurescript/tree/1.6.0, please give it a try in
your projects. You can install this version of ClojureScript by
* checking out the repo
* git checkout 1.6.0
* ./script/install
Take note of the version number that gets installed into
I will surely have a look...I am also interested in the auto saving...I
guess it's implemented the same way..using this custom file watcher layer
over file systems...
It will be fun, and at the moment I read Java better than Clojure ;)
Thank you for the reply
On Jun 8, 2014 9:51 AM, Colin
Clojurescript libs shouldn't specify a Clojurescript dependency (I think).
You can perhaps separate the clojurescript part of your app into a separate
project or lein profile.
There are other issues that can come about by mixing and matching JVM +
CLJS deps, one nasty one I hit is a tools.reader
If I remove clojurescript from my :dependencies in project.clj, two things
happen:
1) When I run lein cljsbuild, it complains and says:
WARNING: It appears your project does not contain a ClojureScript
dependency. One will be provided for you by lein-cljsbuild ...snip -
lein-cljsbuild seems to
Well, like I mentioned, you can wrap dev-specific dependencies into a :dev
profile.
:profiles {:dev {:dependencies {[[org.clojure/clojurescript Blah]
[hiccups hiccups-version]}}}
they will get merged in when the dev profile is active, but won't end up in
Thanks Gary. That fixed it once I realised that another library, cljs-ajax,
was also pulling in clojurescript. After moving clojurescript, hiccups and
cljs-alax into the :dev dependencies, I can now run the app or create an
uberjar or uberwar and it doesn't pull in Clojurescript's dependencies.
