41–50 of 189 posts
Has anyone had success using the AOT tools to build a package of reusable angular components? I was able to use AOT pretty easily for a stand-alone app, but keep running into issues when trying to create a shareable component, and there is not a lot of documentation around this.
Earlier quoted context omitted.
It's not just Angular. To me it feels like everything in the JS world releases way faster than it's reasonable to keep up with these days.
People say this a lot. But the React you write in 2017 is pretty close to the React you'd have written the year the framework was released.
Earlier quoted context omitted.
This is part of what v5 is fixing by enabling AOT by default in development (and production). AOT compilation converts an Angular template to TypeScript that is then type-checked. So on v4+, an `ng build --aot` performs type-checking. But since that's not great developer ergonomics, v5 has included enough performance improvements on AOT that it's reasonable to enable in development (see "TypeScript Transforms"). And…
That's an improvement, but what about syntax coloring, intellisense suggestions and instant squiggly-lines when you make a typo? These are all important for productivity. You get all this when you use .tsx templates (which by the way, are not limited to React, see https://github.com/wisercoder/uibuilder )
Lack of compile-time checks for the template (and embedded expressions) is a major limitation of Angular. This may be OK for small projects. For large projects with many developers this is a huge problem. Here's what happens: a developer modifies code he's not familiar with. He introduces a bug due to a typo. He builds the code without errors, and runs the application, and everything seems to be OK. The bug is not fo…
While I agree that this is very annoying it will not compile using command below so your story about developer who introduces new bug does not check out.
ng build --prod --aot # ErrorThis rapid pace of major releases is a little scary. We're stuck running Angular 1.x because there's no reasonable upgrade path for us. We're a .NET shop and really like Angular, but after the 2.x cluster fuck, we're now thinking about going with something else entirely.
Vue.js can be a good option for shops coming from Angular 1.x.
Earlier quoted context omitted.
It's not just Angular. To me it feels like everything in the JS world releases way faster than it's reasonable to keep up with these days.
People say this a lot. But the React you write in 2017 is pretty close to the React you'd have written the year the framework was released.
It feels a lot more stable than before, where every project had homegrown framework stuff on top of backbone.js or jquery, or then using ember.js. There was just an awful lot of difficult discussion on how to design event-bus abstractions, global state management and general architecture
To me it feels like the frontend ecosystem has stabilized a lot, since the react paradigm is very robust and versatile. For most difficult problems, the solution is somewhat clear. Sometimes more, sometimes less elegant, but at least the timeconsuming disussions have become less frequent within a team
5.0.0? - such precision in versioning for a library or framework seems both too quick and too precise at the same time.
They are following semver: http://semver.org/ So the major version changes whenever they make a backwards-incompatible change. However, I clicked in their upgrade calculator (linked from the post) and at a glance it appears the incompatible changes are fairly minor.
So much semver adoption seems to be based entirely on wishful thinking.
Step 1: hey, perfect drop-in compatibility would be so cool
Step 2: we can do it, with semver!
Step 3: we use semver! Yay us!
Step 4: oh, turns out adopting semver did not make perfect drop in compatibility any easier
Step 5: don't ever touch that zero between major and bugfixHave recently moved system from TS + Angular 1 to Angular 1.5 and then to Angular 2 (took us solid 1 year and you can still see some traces of older code), by time we finished move to 2, Angular 4 was released! And now this! This is WTF moment of my life.
thanks... please fix: https://github.com/angular/angular-cli/issues/6742 before..