This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-26
Channels
- # aleph (3)
- # beginners (98)
- # boot (24)
- # cljs-dev (13)
- # cljsrn (16)
- # clojure (97)
- # clojure-dusseldorf (2)
- # clojure-italy (2)
- # clojure-losangeles (2)
- # clojure-russia (48)
- # clojure-spec (28)
- # clojure-uk (79)
- # clojurescript (79)
- # community-development (2)
- # cursive (4)
- # datomic (35)
- # duct (1)
- # events (1)
- # fulcro (43)
- # heroku (1)
- # jobs (1)
- # lein-figwheel (2)
- # luminus (1)
- # lumo (12)
- # nyc (1)
- # off-topic (6)
- # om (1)
- # pedestal (7)
- # portkey (9)
- # proton (1)
- # re-frame (45)
- # reagent (27)
- # rum (2)
- # shadow-cljs (78)
- # spacemacs (3)
- # specter (2)
- # testing (2)
- # vim (41)
and by using CoffeeScript, it first compiles to ES2015+ , and it has to be compiled with Babel for old browsers.
In Shanghai, Caohejing Development Zone
I know CoffeeScript released 2.0 recent, but we have given up using CoffeeScript now ๐
Because of some JavaScript tools have poor support for CoffeeScript
I start use coffee from at least 2012โฆโฆMaybe more earlier, I didn't remember
But my current company start use coffee at 2015 I think...
I convince two company to use coffee ๐, include current company
But they are all startup company, so you have not heard of them is normal
but it did not contribute back to the original project, only got to switch to ES6 when they found coffee pooly maintained
๐ my two company only 10+- people both
I'm current working for Pomotodo/Duohui, I think you didn't heard
never heard
็ช่ๅ่ฑ/ๅคไผ
I have been hesitant to apply for http://ele.me employees 3 years ago, but I heard that they no longer use CoffeeScript, so I gave up
I'm not in WeChat group
@bolasblack sorry for the sketchy release quality, just pushed [email protected]
which should fix your issues
Cool!
one thing Iโm not too sure about is whether or not I should check if a package exists, that seems somewhat limiting
ie. if you (:require ["airtable" :as ...])
the compiler checks whether node_modules/airtable
exists
that really is not required and will break if you installed airtable
to global or some other parent path
I think shadow-cljs needn't check it, because webpack/browserify/(or runtime? user will get an error) will check it ?
the only reason it is checking is because CLJS core allows (:require [react ...])
which is a magical symbol that ONLY works if node_modules/react
exists
but in case of a string I donโt need to check since I already know that it is a JS dependency
all the issues you had were due to the check not properly running on some package.json
files
I even don't know CLJS core support that ๐
I tried alpha10, it works very well!
Thanks for your work, shadow-cljs is much much much much better than lein-cljsbuild or boot-cljs for me ๐
updated the blog post https://code.thheller.com/blog/shadow-cljs/2017/09/15/js-dependencies-going-forward.html
@jiyinyiyong webpack
uses uglifyjs
to minify things correct?
but since it is now able to compile pure JS projects we might need something more generic ๐
updating packages and namespace would be huge work I think
I was suggesting "coleujs" anyway..
do I seriously have to replace process.env.NODE_ENV
? I thought uglify-js
would be able to do that?
not cool
when I was configuring Webpack, I still have to replace that, during bundling for production
Or maybe a name starts with s
, I don't think it's as good as col..
though http://www.southernliving.com/plants/s
well, the name is the most interesting part, actually I don't like the "-" in the name.. we have lein-cljs
boot-cljs
, as a result shadow-cljs
sounds like there's a thing called shadow
. ๐
------ WARNING #1 --------------------------------------------------------------
File: node_modules/react-dom/cjs/react-dom.development.js:1122:2
unreachable code
--------------------------------------------------------------------------------
------ WARNING #2 --------------------------------------------------------------
File: node_modules/react-dom/cjs/react-dom.development.js:1155:2
unreachable code
--------------------------------------------------------------------------------
------ WARNING #3 --------------------------------------------------------------
File: node_modules/react-dom/cjs/react-dom.development.js:2865:2
unreachable code
--------------------------------------------------------------------------------
------ WARNING #4 --------------------------------------------------------------
File: node_modules/react-dom/cjs/react-dom.development.js:12560:4
unreachable code
--------------------------------------------------------------------------------
------ WARNING #5 --------------------------------------------------------------
File: node_modules/react-dom/cjs/react-dom.development.js:16870:4
unreachable code
--------------------------------------------------------------------------------
------ WARNING #6 --------------------------------------------------------------
File: node_modules/react-dom/cjs/react-dom.development.js:16879:4
unreachable code
--------------------------------------------------------------------------------