Haven't used cljsbuild for a while, so I cannot say with 100% confidence.
2) output-to should be a single target file, output-dir for for everything
else which you may need if you compile with source-maps for example. The
individual files are also for caching to allow incremental compiles. You
Thanks Max!
I pointed this out on Jira as well:
http://dev.clojure.org/jira/browse/CLJS-993
Not a major issue, of course...
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You received this message because you are subscribed to the Google
We are excited to announce the first release of Cuttle:
https://github.com/oakmac/cuttle/
Cuttle is a standalone application for Linux, Mac, and Windows that aims to be
the simplest way to use ClojureScript.
We look forward to your feedback :)
Thanks,
Chris Shaun
--
Note that posts from
Awesome, especially the choice of Atom Shell! Will log any issues on the
repo.
On Fri, Jan 30, 2015 at 10:25 AM, Chris Oakman chris.oak...@gmail.com
wrote:
We are excited to announce the first release of Cuttle:
https://github.com/oakmac/cuttle/
Cuttle is a standalone application for Linux,
I talked to the Relay / GraphQL devs at React conf and conveyed my ideas.
Currently the described approach is a bit JS-centric. Neither are open
source yet and hopefully some of my suggestions eventually find their way
into a release.
David
On Fri, Jan 30, 2015 at 11:08 AM, stephanos
The query language is currently pretty tied to their backend
infrastructure. It's not yet clear what they are going to supply with wrt.
the server component, a reference implementation in Node.js? The
transmitted information is particularly form of JSON, not ideal for
ClojureScript where we'd
There doesn't need to be a ClojureScript answer to Flux. Flux is just one
possible design. This was common point expressed at the conference.
David
On Fri, Jan 30, 2015 at 6:18 PM, gvim gvi...@gmail.com wrote:
On 30/01/2015 20:04, David Nolen wrote:
I talked to the Relay / GraphQL devs at
David - care to share those ideas with us? I for one would be interested in
hearing the feedback you gave them.
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You received this message because you are subscribed to the Google Groups
Hi David and Dan,
I edited Om's Basic Tutorial
(https://github.com/swannodette/om/wiki/Basic-Tutorial) to be used with
Chestnut. Most of the work (not much!) was changing evaluate in
LightTable to save in your text editor. I don't know what the procedure
is for updating a Wiki and having this
I would prefer just Figwheel. Relying only on Figwheel also means you could
probably go out with an updated tutorial much sooner.
Thanks,
David
On Fri, Jan 30, 2015 at 4:10 PM, Sebastian Bensusan sbe...@gmail.com
wrote:
Hi David and Dan,
I edited Om's Basic Tutorial (
On 30/01/2015 20:04, David Nolen wrote:
I talked to the Relay / GraphQL devs at React conf and conveyed my
ideas. Currently the described approach is a bit JS-centric. Neither are
open source yet and hopefully some of my suggestions eventually find
their way into a release.
David
What is
There are 3 third-party JS files on which I depend. I added them to my externs.
Upon doing so, there is no end to the stream of warnings that look like this:
https://www.refheap.com/96690
There is an old thread on this list about maybe using the non-minified version
of the JS file in the
Many thanks to the kind folks on #clojurescript for pointing me in this
direction, which solved this particular problem:
http://swannodette.github.io/2014/03/14/externs-got-you-down/
Cheers.
Andrew
--
Note that posts from new members are moderated - please be patient with your
first post.
1) The main js file is empty because of the closure compiler error. The
circular dependency is somewhere in your code, usually :none should detect it
as well but difficult to tell without the source.
2) I do not think the cljsbuild config should be in a profile.
https://www.refheap.com/96682
Thanks Thomas. I tried your version of the project.clj. Should the
output directory be the same in both dev and prod? Because when I set
them the same, I get this when trying the prod build:
Error encountered performing task 'cljsbuild' with profile(s): 'prod'
java.lang.Exception: All [:compiler
Am Donnerstag, 29. Januar 2015 11:32:31 UTC+1 schrieb Mokhtar Al-Shubei:
Hello all,
My big concern here is about documentation! Why don't I find a centric place
where I know what Om version is actual, stable etc with what ClojureScript,
react.js etc..?
If you hate me already, please
I need another set of eyes on this to see what I'm doing wrong. This is my
project.clj:
https://www.refheap.com/96680
At the command line, I do this:
lein with-profile prod cljsbuild once
It does a number of things that are apparently not right:
1) It spits out the main js file that only has
Ok, I've gotten a bit further and have the following question:
1) Thomas, I was able to get the compile to complete using my original
refheap, which incidentally follows the chestnut template so I think
the structure of those options is ok.
2) I don't understand why there are still individual js
Chestnut depends on Om 0.8.0-rc1 and Clojurescript 0.0-2727 by default.
The handling of Javascript dependencies has improved a lot with 0.0-2727
and newer versions of Om make use of these changes.
Therefore if you want to use the most recent version of Om you'll also need
to use Clojurescript
19 matches
Mail list logo
