This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-03-28
Channels
- # aws (1)
- # beginners (30)
- # boot (7)
- # cider (52)
- # clara (91)
- # cljs-dev (33)
- # cljsjs (1)
- # clojure (447)
- # clojure-brasil (3)
- # clojure-dev (16)
- # clojure-dusseldorf (5)
- # clojure-filipino (1)
- # clojure-italy (29)
- # clojure-sanfrancisco (5)
- # clojure-spec (62)
- # clojure-uk (37)
- # clojurescript (145)
- # clojurewerkz (1)
- # code-reviews (12)
- # community-development (157)
- # cursive (5)
- # datascript (1)
- # datomic (27)
- # editors (42)
- # emacs (5)
- # fulcro (31)
- # hoplon (2)
- # jobs (2)
- # keechma (1)
- # lumo (31)
- # off-topic (2)
- # om (1)
- # onyx (13)
- # parinfer (8)
- # re-frame (13)
- # reagent (32)
- # remote-jobs (4)
- # shadow-cljs (103)
- # spacemacs (15)
- # specter (10)
- # sql (1)
- # tools-deps (35)
- # unrepl (13)
FWIW, I'm nearing getting the Windows unit test situation cleaned up. https://dev.clojure.org/jira/browse/CLJS-2711 (ready) https://dev.clojure.org/jira/browse/CLJS-2669 (ready) https://dev.clojure.org/jira/browse/CLJS-2712 (assigned to me) Once that last one is done, we'll be in good shape with not regressing on Windows.
^ Solved, now down to just two Windows test failures 🙂 https://dev.clojure.org/jira/browse/CLJS-2713 https://dev.clojure.org/jira/browse/CLJS-2714
Oh, it is Wed, so we can post the Shared AOT Cache news post if nobody sees anything wrong with it https://github.com/mfikes/clojurescript-site/blob/issue-183/content/news/2018-03-28-shared-aot-cache.adoc
It sorta feels like it's almost big enough to break out into sections. Any smaller and it seems it should go into its parent doc context... Definitely reads cogent though
News post is live now https://clojurescript.org/news/2018-03-28-shared-aot-cache
I think we said we are cool with updating the original news post to point to this article. This PR would do that https://github.com/clojure/clojurescript-site/pull/213
https://unpkg.com/[email protected]/package.json main/module points to a file here
@juhoteperi so it’s same problem yes?
Problem with pg was that main points to a directory (with index file inside), not file
not totally related but I do think we should take the approach of Closure Compiler and support testing w/o going to the file system
It would indeed be good to find another npm package to replace pg/pg-native with in the test. There must be more packages that do the same (point their main entry to a directory).
goog-define
is not often used directly in a REPL, but if :def-emits-var
is set, it might be nice for the macro to return the var being defined.
I wonder if it will be easier to create dummy npm package with main entry folder than to search for one
I'll be out-of-town starting tomorrow, probably not returning online until sometime Monday.
enjoy!