@juhoteperi: holy cow! That's sweet!

Any comments about naming or the API?

The naming seems pretty good to me. This is new ground so it's tough to know.

Overall I think it's perfect for now.

@juhoteperi: thanks!!

@dnolen I get a bunch of closure warnings with 456. I assume that is why you disable the type checking?

https://github.com/clojure/clojurescript/commit/367e2fb600c54d3b04a1d85ccf9bc659b7f05151

WARNING: CLJS/cljs/spec/impl/gen.js:2103: WARNING - Function cljs.core.array_seq: called with 2 argument(s). Function requires at least 1 argument(s) and no more than 1 argument(s).
return cljs.spec.impl.gen.elements.cljs$core$IFn$_invoke$arity$variadic(cljs.core.array_seq([pred], 0));
                                                                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

did you think about how we can teach variadic fns to closure?

(before I start to dive into the type checking stuff myself)

Looks like Closure can't currently resolve Common JS modules from classpath and there seems to be problems even using relative paths

@thheller: only seemed to happen under code splitting but yes

@juhoteperi: Closure doesn't use the classpath for resolution at all

Okay. I'm interested in supporting that as I want to package npm packages into Cljsjs.

Well, I'll have to investigate if this is something that could be changed in Closure or if it can be worked around in Cljs or tooling side.

Btw. @dnolen Did you see https://github.com/cljsjs/packages/tree/master/babel-standalone ? Should the module guide on Cljs site be updated to use or mention this?

@juhoteperi: if you have new instructions happy to review a PR.

Okay, I'll create a PR. I'll also start thinking about providing Nodejs and other missing externs in Cljsjs.

As all externs provided by a package are always enabled, I wonder if it is better to package each Nodejs extern separately or provide single Nodejs externs package.

Hmm, Closure-compiler itself also provides set of Nodejs externs: https://github.com/google/closure-compiler/tree/master/contrib/nodejs

@juhoteperi: been thinking about babel-standalone. If the presets key uses the full namespace tooling can try to resolve/require it dynamically.

I'm sorry I didn't think of this yesterday

Yeah I thought about something like that

I guess it is something that Cljs shouldn't do but boot-cljs or figwheel could do

I should either rename the namespace to cljsjs.babel or the key to :cljsjs/babel-standalone

or hmm, the keyword namespace should be cljsjs.babel-standalone

so key could be :cljsjs.babel-standalone/babel