@brankoiliccc have you been doing 'npm' install on your windows box successfully in other projects? I think it's pretty common to install the linux commands (cygwin) when installing git on windows, which should take care of the 'cp' problem. It's a general npm / command line on windows problem though, not one with this seed project.
if you google your 'cp' error, you should be able to find a few workarounds
I would say that if your production app has a fairly short release schedule, though, angular 2 would be kind of risky, as so much is still changing.
For a short-term production app I would suggest Angular 1.x or React.
@ollwenjones Well i havent had problems with npm install before. Anyways i am gonna give it a try on another machine with Linux on it. Release schedule is not the problem. Problem is Angular2/typescript/react/weback are all new concepts for me so i wanted to make it as simple as possible. Bundle everything with webpack, reference from my spring boot template and have everything run all together with mvn spring-boot:run command. Keep it as simple as possible. I must admit my angular2 knowledge is limited so at every step of the way i need to check is everything still working or did i make a mistake, even for the simplest things.
I had added lodash and open layers to a previous version of this seed, but it was for a proof of concept and seemed kind of hackneyed: var _ = require('../../../node_modules/lodash'); var ol = require('../../../node_modules/openlayers');