cherry
cherry copied to clipboard
Experimental ClojureScript to ES6 module compiler
What approaches would be feasible, while also allowing for tree-shaking by ES6 tooling?
When using only one function from cherry/cljs.core.js, e.g. `js-keys`, and then processing this with a treeshaker like esbuild or ncc, it seems that it's still pulling in the entire package....
Should we transpile this one with cherry or pre-create using the Closure compiler?
Questions: is splice supported everywhere now? What do we gain, what risk do we take by optimizing this?
I think we could make ES6 output vs .cjs or whatever else output configurable, so the compiler API gives you some options, for e.g. when you want to integrate the...
I've got this from running the tests: ``` Testing cherry.compiler-test FAIL in (return-test) (Error:NaN:NaN) Uncaught exception, not in assertion. expected: nil actual: #object[Error Error: vector is not ISeqable] FAIL in...
- https://github.com/clavascript/clavascript/commit/f05d3b75f2682376858c9fa216e7f7d84b8641d8 - https://github.com/clavascript/clavascript/commit/c321878163d096eeabe56c3071cef9a4dd4ae152 - https://github.com/clavascript/clavascript/commit/73e0ae5a0363468d33f1afe97c7b44d568f187cb - https://github.com/clavascript/clavascript/commit/1eae6ae9d59c0f05b96917d5dc08e7ac243d0d6c
How do you turn on source map support for debugging?