In this section, thought to introduce you the idea of hosting multiple SPAs under PWA. This kind of scenario will be useful, wherein you are having multiple spa scenario and each app can’t be a PWA basically. Hence, to keep all the apps under one roof, we can have root app as PWA and child apps which are individual angular apps can remain like that only. Now, if you don’t know how to get started with PWA, in that case, please refer to my earlier post around the same http://bit.ly/ng-6-pwa.
In this section, we are going to talk about angular elements. Angular elements is extremely helpful in building cross framework components. Consider a case where you are writing any shared library in angular and you would like to use the same in react. Initially, cross framework communication was pain. But with the introduction of angular elements, its fairly simple and easily achievable. In a nutshell it means something like
Web components are based on existing web standards. Features to support web components are currently being added to the HTML and DOM specs, letting web developers easily extend HTML with new elements with encapsulated styling and custom behavior.
Thought to share new .Net Core 2.1 version features. Its announced now. And it has got some cool features. First of all to update the existing one, you need to have updated Visual Studio 2017 with 15.7 Preview 1 or newer. Once those updates, in place then you can install the utility directly from this page https://www.microsoft.com/net/download/dotnet-core/sdk-2.1.300-preview1.
Disclaimer:- This blog is only useful for those whose angular application is still based on old system-js-gulp example.
In this blog, we will continue from the last last post. In last post, we have migrated a normal angular 5 app built on top of webpack to angular 6. That was kind of cake-walk as ng update normally takes care of all the things. Details you can always find in my last post at http://bit.ly/ng-6. Therefore, after the usual steps as covered in the last blog, when I build my app. It gave typescript error and this was expected because I didn’t run Rx-migaration till now. For that first we need to install npm install -g rxjs-tslint. If you are on gulp-systemjs based solution. Then after that, you may get below error.
In this section, we are going to talk about migrating your app to angular 6. Again, there may be extra separate steps while upgrading depending on current stack of angular. Say if you are using systemjs and gulp in your project, then migration would be little different than the usual one. For later approach, I will talk in different post. In this post, let’s start with normal flow.
Recently, I was trying to code online itself. Although, plnkr is there. But, as far as VSCode like experience is concerned, other editors lags heavily. And, let’s suppose you are remote or may be you don’t have access to vscode and wanted to quickly present any demo or prototype any solution. How do you do that?
In this post thought to share one of the tools which I use always for keeping my angular app document ready as well. You must have worked with other frameworks where in it can read your API comments and generate proper documentation out of the box. In case of angular, this feature comes live with the help of https://github.com/compodoc/compodoc. This is open source project with really cool themes to suit your need. Either you can install this tool globally and use the same in the project or you can have the same locally installed.
In this section, thought to talk about HTTP-Client usage in angular and how its different from existing HTTP Module. It has RxJS Observable-based API. It means that the multiple calls to the HTTP module will return an observable, which we need to subscribe.
If we don’t subscribe to these observables, it won’t work.
If we subscribe multiple times to these observables, multiple HTTP requests will be triggered.
If HTTP request is successful, it will emit only one value and then complete
If HTTP request fails, then these observables will emit an error.