2017 in ClojureScript Web Perf & JS Ecosystem Integration
summary
ClojureScript 2017 makes npm modules first-class: the Google Closure Compiler now parses node_modules so JS packages (including JSX after a Babel preprocess) are visible to the optimizer, enabling dead-code elimination and cross-module code motion across JS and CLJS. The compiler gains first-class code splitting where entry-point namespaces produce automatic chunks, plus a runtime loader namespace and resolve macro to load chunks. Self-hosted tooling (Lumo), CI on Windows/Linux, and a backwards-compatible migration path are in place.
AI-written summary · about
chapters (11)
- 0:00Intro
- 3:39All different kinds of module formats
- 4:432015: Initial Code Splitting Support
- 12:09Code Splitting:before
- 14:10Enhanced Code Splitting & Module Loading
- 17:20Enhanced Module Loading
- 21:46Goals for a modern Interop story
- 23:25How do I consume NPM modules?
- 25:36How do I integrate with JavaScript sources?
- 26:33Preprocessors / JS compilers
- 28:52What can ClojureScript do for you in 2017?
related talks
27mBuilding functional Front-ends with ClojureScript
32mClojureScript: Lisp's Revenge
34mClojureScript: The Essence of Alchemy
11mJavascript Tooling - The Evolution and Future of JS & Front-end Build Tools
38mcljs All The Things: Full Stack Apps with ClojureScript
18mClojureScript Has It All! Except Maybe for Types
32mNavigating ClojureScript's Fire Swamps
29mExtending JavaScript Libraries from ClojureScript