Skip to main content

Utilize 3rd party Javascript libraries in your Angular 2+ application with CLI

Not everything is available as a native Typescript library.

Due to that sometimes you might need to use 3rd party libraries. After creating a new project with Angular CLI you will experience that VS Code does not know any libraries you have imported in the header tag and the compiler complains when you try to use this libraries.

The reason is: You are missing the typings.

The typings describe the functionality of the libary and make that available in your project through intellisense and for the compiler.

But before you start creating your own typings do the following checks:

1. Does the vendor of the library provide the typings? If yes, install through npm
2. Are the typings available on definitely typed? If yes, then take it from there.

If this is not the case then you can do your own typings. If you want to do that properly, then you should write the complete set of typings for the library and upload to definitely typed to provide it for the community. OK, this might be difficult and time consuming, so what should you do then?
Yes, there is an easy way for your project. (Not the clean way)
To describe how to do that let's try to use particles.js in our application.

To include the particles.js library to your project you have two possibilities.

A) install the npm package 
npm install particles.js
That also means that you have to register the package in the .angular-cli.json file like that
"scripts": [
    "../node_modules/particles.js/.../...js"
  ]
Then CLI puts it into your bundles.

B) just import it in your index.html
<script src="https://cdn.jsdelivr.net/particles.js/2.0.0/particles.min.js"></script>

Let's choose B), so our bundles keep slim.

The next step is to put the 'div' that hosts the particles to your index.html, the component template or somewhere else in your project.
<div id="particles-js"></div>
Now we come to the big trick to utilize the library in the project.
To do that we add a typing in the typings.d.ts file or in the component where you want to use the library.
declare var particlesJS: any;
This makes the library visible in your project. The trick is the 'any' type. By that you can use particleJS.someFunction in your project without the compiler or the code editor complaining.
To run the particles we just add the following code:
particlesJS.load('particles-js', 'particles.json', null);
That's it. You can use this solution for any 3rd party library that does not provide typings.
If you want to see that working just open the plunker example I have made.

Comments

Popular posts from this blog

Download a file with Angular2+ and FileSaver.js

Why should your Angular code download a file? Of course your webserver can deliver files and you can just add a simple link to your website but what if the file is delivered by a webservice and the webservice requests authentication (i.e. OAuth) to protect the file from unauthorized access? In this case you might have the requirement to download the file in your code and then tell the browser to save it to the hard disk. How to do that?   First of all you need to add filesaver.js to your project.  npm install file-saver --save ..and add the typings npm install @types/file-saver --save-dev More information about filesaver you can find on the filesaver github pages . To download the file via http you need to implement a service. The following imports are required: import  {  Injectable  }  from   '@angular/core' ; import  {  Http ,  Response ,  RequestOptions ,  ResponseContentType  }  from   ...

Nested Component - Passing Data to a Parent Component

In my previous article  Nested Component - Passing Data to a Child Component , I explained how to pass data from a parent component to a child component.  In this article I will describe how you do the other way, passing data from a child to a parent component. As you know, there is a decorator called @Input for passing data to the child, and of course there is another decorator to passing the data to the parent. This decorator is called @Output. Very obvious. So we have to import this decorator to your parent component import  {  Output  }  from   '@angular/core' ; Now we can use this decorator. The property type of the decorator must be an event. The data to pass becomes the event payload. So we have to import the EventEmitter, too, because in Angular an event is defined with an EventEmitter object. import  {  Output ,  EventEmitter  }  from   '@angular/core' ; Next step is to create a new instance of th...