That was similar to my failed attempt to make an app with Meteor. Not having much free time I seem to have started at the wrong time so that halfway into learning the framework and applying it to my own project, Meteor got an update. Being still in the learning phase I updated to be working with the latest stable version, something which broke the app, so I spent time fixing that, then the free hosting tier was dropped and for a hobbyist who was making an app that was guaranteed to never generate revenue ever ever, it became too expensive to host in comparison to a traditional $10 host with a mySql DB. And what was I doing anyways? Meteor Blaze? Was that the correct choice? Or was Meteor & Angular a better choice? Or was Meteor React the way to go? Or if I'm using Angular or React why am I using Meteor? Ended up with so many questions about whether or not I was using the right stack for me, and as I said, not much time to work on it so looking for something that wasn't going to be abandoned in 6 months time, in the end I just gave up on that project.
It doesn't help either that these js communities are splintered around every tiny issue and forked every other week (mean.js! is where I started the whole process). The feeling that there is zero permanence one week into a project does not inspire confidence either in my own project or the tools I have chosen.
It doesn't help either that these js communities are splintered around every tiny issue and forked every other week (mean.js! is where I started the whole process). The feeling that there is zero permanence one week into a project does not inspire confidence either in my own project or the tools I have chosen.