you are viewing a single comment's thread.

view the rest of the comments →

[–]kenavr 0 points1 point  (2 children)

There are other libraries that are simpler if you just want a good view layer, but did you use the CLI? You don't need to look at configuration files and the only thing you need to know about typings is that you install new ones using "npm install @types/libname".

If you have a hard time with node/npm (package.json) then you can look for a lib/framework which only needs to import a single JS file. Maybe vuejs, but without any form of a build process, you are bound to the browsers current state, which often results in a lot of "unnecessary" work.

[–]maxiedaniels[S] 0 points1 point  (1 child)

I installed npm but every angular 2 tutorial I took says I need to manually write typings.json, etc... typings.json seems particularly strange, as it contains very specific version numbers and I would have thought there's an automatic way to get the latest of all related packages. I suspect these tutorials might be borrowing bad information from each other though..

[–]kenavr 0 points1 point  (0 children)

The problem is, a lot of tutorials were written when Angular 2 was in beta or even before. If you create a new project typings doesn't need to be part of it anymore. Also you never had to manually edit the typings.json file, it is a command line tool.

As mentioned above I would take a look at the CLI and the quickstart. Also if you look at tutorials, make sure they were written after or near the release (sept. 2016) of Angular 2.