We created a new boilerplate for Angular2-meteor applications.
It includes all the required dependencies for Angular2 and Angular2-Meteor, along with full examples for Component, Service and Unit tests.
The boilerplate works out-of-the-box (just npm install) and you don’t need to do anything to make it work.
You can find it here (more details about the contents of this boilerplate is inside the README file):
Our goal is to provide it using “meteor create angular2” command, so we created a PR for this:
It’s not instead of your boilerplate because you have more features than this, it’s more simple and for a starting point purpose, to prevent the many issues people have when they start and to shorten the first bootstrapping chapter a lot.
But there are some small differences and we can be aligned and collaborate on it
Looks good. The problem I had with Angular 2 and Meteor while I was writing the boiler plate was getting all the dependencies and base structure done right. It was not as simple as Angular 1 that’s for sure and this seems to have more people working on it which is good. My boilerplate is solo and is dependent on my free time.
In addition, there’s big one baggage that I have with my boiler plate that is different from the base. That is having an to make it work with an existing angular1 app. So my boilerplate is more of a starting point for a hybrid app which other people can pick off from to help migrate their Angular1 app to support Angular2. As such even I to this day still have issues with the static-html-templates but I haven’t figured out which part is the culprit (the pbastowski:angular-babel or the static-templates), I used the require workaround to get it working.
Anyway I digress, I did post one suggestion to their base to reduce their code base a bit. I really like that it’s typescript down to the server side. However, I still don’t like this