As a dev, completely get the need. Yes, most of my day-to-day job is making a small change or reproducing a bug locally, testing, and then deploying. Setting up that loop has been harder than I want to admit and is the reason I know maven, ant, chef AND puppet, Jenkins, and gradle as well as I do. In many ways I wish I didn't have to!

That said, my friendly advice would be to pick one framework and environment combination and solve this problem end to end. Node would be a perfect start. Show me how to use your project to make node dev shorter and easier. If I believe you I will use you and node for new projects. I'm not going to switch an existing project to jumpstart because I've already set up the flow. Maybe I'm weird, but I demand single-command builds and deploys. All my projects already have it. But I'm willing to learn new techs to avoid the pain.

I see your landing page and take away you have lofty goals and are trying to be all things to all people. Don't. Pick one. Focus. Be the best at it. Make a YouTube video that shows me how you get 1-second whatever. It's especially puzzling when you don't have a demo video but you have a produced ad on "flow." It's hard to believe your product has substance during this launch.

I'm willing to switch to angular and node (or hipster.js and kitkat.io -- whatever, it doesn't really matter) to get what you advertise. For new projects. I won't touch existing stuff. It means I have to test and am likely to break something by moving to your project in prod. Nobody ever changes their build scripts!