hi I wish I could helo but debugging your machine from here is a little tricky. I recommend following these steps angular.io/cli Sounds like the npm install did not add the cli or your path was not correctly updated

Vetr hard to debug with so little info I recommend trying stack overflow after doing a free install and removing any old versions

i reckon you havent installed nodejs. please do that first

Hi Hard to visualise your issue but I am guessing you need to put your menu outside the router outlet on your app module? If you post a like to a github repo I am happy to look

Hi Very hard to debug remotely. I would suggest trying the following if you do not already have a solution. 1. Make sure you are not installing the project on the root of your machine like your C drive on windows. 2. Uninstall the Angular CLI and reinstall in with npm uninstall @angular/cli Check your global version and npm packages in general to make sure nothing stale is installed with the command npm list -g --depth=0 3. Reinstall Angular CLI 4. Re make the angular project fro scratch in a new folder with ng new YOURAPPNAME

first thank you for taking the time to reply. I am checking in now the good thing is i have the current lts version of node im going to uninstall and update on progress

Kinda fixed but I have to use my build at the moment. The issue might be due to older dependencies on my Mac so I am going delete everything and install again

Great question. Depends on how much code you want to share as there is nothing stopping you doing one per a client. If you do one per a client the build will be simple as it is only three projects but if you will not be able to share code between clients with Nx libs. You would need to make npm packages to share across clients. If you put 150 apps into one workspace then you will have easier code sharing but will have more effort to keep all projects up to date to share dependencies. You will also have more effort on knowing what apps to rebuild and deploy as updating 150 apps will likely need some extra work for the build system. Nx can help with this but it is worth thinking about. As you can see it depends on each situation. What do you think will work for you?

Rohit Bhambhani yes. So the directory where npm is written is basically root, we need to change the owner to the preferred user.

Hi You are right the arrows should point the other way :) It has been almost two years now since this early into to Angular 2. Wow has the framework come a long way.

Hi Thanks for the complement I have been very busy with travel for conferences and Pluralsight and have a bunch of free NDC Videos not listed here if interested in more or on Pluralsight. I will be making more for youtube again soon.

gist.github.com/duncanhunter/90f04c77304971b94d125ba11a46512d

Hi Angular is now very different. Routing is also different but better. Filters are now called pipes and dependency injection is still a primary piece for managing dependencies but the syntax is different with TypesScript. Digest cycle or change detection is also very different. Hard to compare best to just move forward learning the new things and not get to lost trying to find similarities, then after some trying decide if you like it :)

Good point. Thank you, Duncan.

wallabyjs.com/ it is very very good

But is not it licensed?

Yup, you need to buy it. Nothing wrong with the open source tools like Karma and Jasmine but I prefer WallabyJS

Trevor D'souza it means you can reuse the service elswhere, atleast i think? Trying to work it out myself

Seperation of concerns

Adrian Holmes sure ... you can start with angular2 ... its defferent

my pleasure thanks for watching

thanks

Thanks for the feedback I will check for that next time.

lol yes

You only need @Injectable if your service has injected dependencies. Although you are right the Angular team do say to add it as a best practice even if you do not need it as you may later.

Duncan Hunter thanks for the clarification.

Having worked on several Angular and also server side rendered apps with ASP.NET MVC in the last year. They both have their merits. I find the user experience better on a client-side app with Angular without the page refreshes. I also find that it is easier to make a complex UI with Angular versus the spaghetti code of a lot of custom JavaScript/JQuery. That said I do not mind ASP.NET MVC and traditional server-side rendered HTML as they are often faster to make and are less buggy with less state to manage on the client.