I'm curious about Clojurescript deployment best practices. Even in advanced compilation mode, I'm finding the size my js to be pretty large. But my application code is quite a small fraction of the total. The rest is the Clojurescript runtime, React, Datascript, Material-UI components, etc.
On a daily/weekly deployment basis, only my application code changes. Yet with the practice of advanced compilation, I have to redeploy a large .js file to the web clients just to update the application code - the majority of the data payload hasn't changed at all. What I'm thinking of doing is compiling two .js files in simple mode, not advanced mode. The first called framework.js would include Clojurescript, React, Datascript, etc. The second called app.js would just be my application code. Now on a daily basis I only have to cache-invalidate a relatively small .js file in order to update the web app. The framework.js file only needs to update every couple months when I want to bump the library versions. I feel the benefits of no longer re-deploying the Clojurescript runtime over and over outway the limitations of not using advanced compilation mode. Am I missing something that makes this a bad idea? Is anyone else doing something similar? Thanks for your help. -- Regards, Scott Klarenbach Invisible Robot Technologies invisiblerobot.io 604-537-1856 sc...@invisiblerobot.io #515 - 207 West Hastings Street Vancouver, BC, V6B1H7 _______________________________________ To iterate is human; to recur, divine -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojurescript+unsubscr...@googlegroups.com. To post to this group, send email to clojurescript@googlegroups.com. Visit this group at https://groups.google.com/group/clojurescript.
