@kylecordes The situation is exactly dire because, it is not actually a technical/physical problem, as much as it is a negligence from core developers to the general public. I’m pretty sure contributing devs themselves do not have these problems because they solved them once for their own rig, with dirty workaround here, dirty workaround there, and once they got their setup working, they just focus on their daily job. But, there are thousands of devs from “general public” (like me), who are just trying to switch to Angular 2, trying to RTFM over and over again, just to taste the Angular 2 as it has been demoed in numerous webcasts, conferences, and blogs, but… there are so many unnecessary barriers to get the base scenario working! Being mostly a backend developer (MS-technology-stack-based) originally, its already challenging for me to wrap my head around so many new concepts, so complicated frontend build scenarios, etc, but I really am intrigued by the power of Angular 2, and eager to make a switch to it (from ASP.NET MVC) no matter the learning curve. I imagine there are thousands of devs just like me. But is it hard for somebody that got it working already, to share the basic steps necessary and write it into the readme with big bold font?

Take the peer dep missing error for example. I’m sure it’s not dependent on my particular system, you should have these warnings on any system right now. Three different versions of typescript are requested by different dependencies. How do you solve them? Should I ignore that?

And then that fatal error that pops with every NG command execution: Cannot find module '@angular-cli/base-href-webpack'. This thing is just so easy to repro! Just npm install the version from HEAD right now and you have that error. If I install the one from npm official registry, it is outdated (not RC6) and there are no instructions how (and whether at all) can we update from it.

Can anybody write a steps required to setup everything on Windows so that I could ng new an RC6 project? No? Maybe later? When? It has been like more than two weeks after RC6 release, and I’ve been visiting this repo every evening and every morning since, but couldn’t find a clear way to make it work with Angular-CLI. There are no milestones, no blog posts, the readme hasn’t been properly updated for ages, the changelog is from August and says “beta.11-webpack.3”, while everybody mentions “beta.11-webpack.8”. There have been 5 releases since? Why don’t you make a version that just updates to RC6 and publish it to npm? Why should we hack with repo directly to get updates? I imagine it should not take more than few hours to proper people involved to update it to RC6 and publish to npm? Well certainly not 15 days (and counting)?? RC6 did NOT bring any breaking functionality changes per se, so what’s the problem?

I see what is the problem. The problem is that you just don’t realize that there are thousands of devs watching and waiting day after day, just to play with latest versions, and “sometimes in the future” is not the proper date to give them, when actually you can waste few hours of yours to write proper instructions and save thousands of hours collectively for those who really can’t hack it themselves. Just please be more responsible to the public…

Wtf. This seems to turn into team bashing. Stop it please.

Yes, it’s hard to use on windows ( no experience with other platforms), Yes it’s hard to understand why.

But keep calm. It’s still beta!

The situation is not quite as dire as it may seem in this issue thread. The current challenge (and actually a challenge over the last couple of months) is that CLI has been shipping with various floating dependencies, into the Node ecosystem where semver is assumed by versioning system, but not given as much attention as it would need by package developers who very frequently ship breaking changes in minor versions.

I imagine the CLI team would like to be able to respond to these breakages with the new CLI versions immediately, but they are also trying to absorb new versions of Angular itself. I’m hoping that between the rapidly settling churn in Angular, and hopefully an increased respect for the tendency of node packages to break, we will end up with a stable CLI in the near future. Where stable means that “ng new” continues to give a working application, on all major platforms, for an extended period of months.

The angular-cli team is juggling a whole heap of fast moving dependencies. So other than keeping the tone civil, it would be preferable to separate out what is platform vs tooling specific. Yes, there have been some opportunities as of late to keep things smoother…

However, developing on a Windows 10 machine, there is not a single issue I had to look into with the webpack.8 version that other platforms had not flagged as well.

If the issue is related to getting it to work with Windows tooling, try VS Code instead of Visual Studio. Maybe some of the sting you seem to experience is resolved that way. Lightweight works & like a charm.

As I commented above I see no merit in the statement that cli does not work on Windows. It is difficult to stay on top of the changes(angular rc7 today!) but the issues in my experience are the same on Windows and Mac. I have had no windows specific issues…

npm i -g angular-cli@1.0.0-beta.11-webpack.2 was the only way to get it work again.

Please fix the windows problems!

And now that Angular itself is updated to RC7, trying to update a working project is a decent into hades. Just update the package.json and reinstall, right? Nope. Errors all up and down.

Not to mention a brand new, blank project, using the master version of the CLI insists on using an old beta of webpack - webpack beta.21 - even though beta.22 is specified in all the package.json files.

Ugh. What holy hell this is turning out to be.

Global package:

npm uninstall -g angular-cli npm cache clean npm install -g angular-cli@webpack

Local project package:

commit any changes you have to git first

rm -rf node_modules dist tmp typings npm install --save-dev angular-cli@webpack