I’m working with a group on an OSS project. Our Meter app is one component among others (+ Chrome Extension, Electron app). We’re noticing slower + slower build times. The typical dev flow: Make a JS or SCSS change, wait a few seconds for HCP to kick in… switch to the browser, wait 20-30 seconds until our app is fully loaded.
This is making UI development slow and tedious. I dont have a new machine, but certainly not an unusable one, Core i5 Macbook Pro, and I’ve been resorting to doing as much code as I can in Codepens to try to move faster on the UI design side.
I’ve also tried to disable HCP, but node still kicks off under the hood to compile the templates(?) on every file save. This is not helpful for refactoring - often I’ll [want] to make lots of changes to many files, but every tiny change causes a CPU spike, a slow+unresponsive computer.
I read a little bit about the streaming build system in the Meteor 1.2 blog update (I cant post it here, 2 link limit for new users?) Glad to hear Meteor is tackling this problem.
I’ve heard about Gulp and its lightning fast build, but havent tried it.
Is Meteor going to incorporate these kinds of improvements? What can we expect?
Are there guidelines or documentation regarding how to improve/optimize build times - is it a linear thing, or are certain folders, modules, packages taking a disproportionately longer time than others?
Can we configure which parts of our app, maybe via a config file, that would be “hot”?
Would we only benefit from these updates if we’re using React (that update isnt clear)
In the short term - can I prevent node from watching files, unless I explicitly ask it to build?
I feel I’m missing something - how are folks who are running production apps maintaining a smooth workflow?