21–30 of 42 posts
But all npm package.json dependencies are still anchored on the same ^5.0.0 dependencies that ng v1.5.0 had and still depends on typescript "~2.4.2", basically ignoring the 5.1 announcement.
How can we create a new Angular 5.1 App using ng? Are we meant to manually change all dependencies to ^5.1.0
I created a new project using @angular/cli 1.6 which the release says is tied to Angular 5.1: https://github.com/angular/angular-cli/releases/tag/v1.6.0 But all npm package.json dependencies are still anchored on the same ^5.0.0 dependencies that ng v1.5.0 had and still depends on typescript "~2.4.2", basically ignoring the 5.1 announcement. How can we create a new Angular 5.1 App using ng? Are we meant to manually c…
Can anyone speak to their successes with Angular post 2.0? I feel like any time it comes up, it's mostly horror stories about the transition or how shops have just moved on to Vue, etc. Is it worth still considering / where does Angular shine where React and Vue come up short?
So I don't think there will be horror stories with Angular 5 for new projects, unless you just don't like Angular/TypeScript. It's definitely not like "going the wrong direction" from Angular 1.x, although I don't personally have any read on how it compares to Vue, or React, or Aurelia or what have you.
I also haven't gone through a 1.x→modern transition (yet), so I can't really speak to that, but in preparation for doing it I've read everything I can, on this forum, various blogs, etc.
I'm not looking forward to it, but on the other hand part of me thinks of course it's easier, or at least more fun, to move to something like Vue, because it's like a rewrite, or half-greenfield project.
It's almost always more fun to rewrite something, although usually not advisable from any other business perspective.
We don't see as many people talking/blogging about Angular anymore, but I think that's mostly because it's gotten boring. Which can be a good thing.
I created a new project using @angular/cli 1.6 which the release says is tied to Angular 5.1: https://github.com/angular/angular-cli/releases/tag/v1.6.0 But all npm package.json dependencies are still anchored on the same ^5.0.0 dependencies that ng v1.5.0 had and still depends on typescript "~2.4.2", basically ignoring the 5.1 announcement. How can we create a new Angular 5.1 App using ng? Are we meant to manually c…
See https://github.com/angular/angular-cli/pull/8766
I also don't get the point of upgrading to the latest angular-cli v1.6 and using it to create the same 5.0.0 app that v1.5 did.
Is the way to create a v5.1 ng app is for everyone to manually update all dependencies to ^5.1.0?
Earlier quoted context omitted.
See https://github.com/angular/angular-cli/pull/8766
I manually updated the typescript dependency which breaks the build, even when manually upgrading the compiler-cli to ^5.1.0, so basically 5.1 doesn't work with typescript 2.5.3 as indicated in the announcement. I also don't get the point of upgrading to the latest angular-cli v1.6 and using it to create the same 5.0.0 app that v1.5 did. Is the way to create a v5.1 ng app is for everyone to manually update all depend…
[1] https://bytearcher.com/articles/semver-explained-why-theres-...
Earlier quoted context omitted.
I manually updated the typescript dependency which breaks the build, even when manually upgrading the compiler-cli to ^5.1.0, so basically 5.1 doesn't work with typescript 2.5.3 as indicated in the announcement. I also don't get the point of upgrading to the latest angular-cli v1.6 and using it to create the same 5.0.0 app that v1.5 did. Is the way to create a v5.1 ng app is for everyone to manually update all depend…
the caret ('^') will update a minor version[1]. So ^5.0.0 will install 5.1.0. [1] https://bytearcher.com/articles/semver-explained-why-theres-...
Can anyone speak to their successes with Angular post 2.0? I feel like any time it comes up, it's mostly horror stories about the transition or how shops have just moved on to Vue, etc. Is it worth still considering / where does Angular shine where React and Vue come up short?
Angular is _fine_, but it's largely a "me too" framework that brings nothing new to the table. On the other hand, it insists on using a non-standard language, which breaks all of the tooling used in the rest of the JS ecosystem. React and Vue are reasonable options, but as someone using Angular in production I'd urge you to stay far away from Angular and TypeScript.
I may not choose Angular for every project, but I would certainly never again use untyped JavaScript over TypeScript, for an app of any size, unless there was some unusual and very compelling reason.
(And it would have to be a really unusual reason; I can't even think of a hypothetical one.)
In my own experience, TypeScript is a huge advance over JavaScript without types, in both productivity (how quickly functionality gets implemented) and reliability (how many bugs ever make it all the way to a customer).
I will spice up that factual statement with a bit of speculation that will perhaps be more controversial: in my experience watching other developers move to TypeScript, I think the productivity and reliability gains generally apply to their work too, whether or not they personally like TypeScript.
Can anyone speak to their successes with Angular post 2.0? I feel like any time it comes up, it's mostly horror stories about the transition or how shops have just moved on to Vue, etc. Is it worth still considering / where does Angular shine where React and Vue come up short?
Getting from 1 to 2 was quite an experience. Much discussed here and elsewhere. Thereafter though, they have been just relentlessly polishing, improving, smoothing rough edges, making bundle smaller, making compilation and execution faster, etc. It is really a model of exactly what you would want, in terms of a joint respect for backward compatibility with forward progress. I don't understand the "haters" in some pee…
On the flip side, I have found I missed some things about Angular that I don't have with libraries like Ember and React - Angular has the superior testing story for ability to control granularity of testing without sacrificing architecture. Complicated pure functions can be tested with ease in Angular due to its injector, but painful in other scenarios because one cannot easily mock out dependencies so easily or requiring some fairly poorly documented/written about tricks. Managing state in Angular isn't really a difficult issue, and yet it becomes exacerbated in other ecosystems due to their delegation of tools to the community and each of the tools not providing good examples/documentation on blessed ways to wire them together, leaving a lot of dev shops with lesser solutions.
At this point, I see the major libraries/frameworks as having a set of more minor tradeoffs for devs to weigh - Angular, React, or whatever will get you where you want to be given the time/resources. With whatever is chosen for the view layer, you will be making time tradeoffs of where you'll spend more time when using Angular, or React, and you will create restrictions as a result. That said, it is perfectly possible to accomplish probably almost everyone's needs with Angular in a timely manner, and probably would be faster to initial market to get a moderately complex app than something like React IMO due to not needing to build certain types of boilerplate/refactoring as much due to lack of foresight about needing a particular system in place in the app.
Note: I have almost 5 years of experience with Angular, and currently have almost a half year of experience leading a very complex React project.
Earlier quoted context omitted.
the caret ('^') will update a minor version[1]. So ^5.0.0 will install 5.1.0. [1] https://bytearcher.com/articles/semver-explained-why-theres-...
The question is what's the best way to create an ng 5.1 app? i.e. what was just announced. I've just manually updated all deps to ^5.1.0.
Can anyone speak to their successes with Angular post 2.0? I feel like any time it comes up, it's mostly horror stories about the transition or how shops have just moved on to Vue, etc. Is it worth still considering / where does Angular shine where React and Vue come up short?
There are certainly some issues with Angular. For example, starting Webpack Dev Server is really slow (a minute or longer). Running a lot of tests with Kharma can be slow. If you know what the issues are and can either live with or work around them, then it is not that bad.