Move angular support to 14

Move angular support to 14

v3.x.x -> Angular 9.x.x - 10.x.x

Updated:

intl-tel-input to 17.0.3
ngx-bootstrap to 6.0.0

This introduces breaking changes:

• Make sure to update your packages.json file with new deps:

"intl-tel-input": "^17.0.3",
"ngx-bootstrap": "^6.0.0"

• the CSS classes of intl-tel-input have changed, make sure to update your CSS styles if you have overridden any styles.

v2.x.x -> Angular 8.x.x - 9.1.x

Updated:
intl-tel-input to 17.0.3

This introduces breaking changes:

• Make sure to update your packages.json file with new deps:

"intl-tel-input": "^17.0.3"

• the CSS classes of intl-tel-input have changed, make sure to update your CSS styles if you have overridden any styles.

Fixes: Cannot read property 'querySelector' of undefined

Merge pull request #294 from pasevin/master

Fixes #293

ReadMe update to reflect Angular 9 support.

Merge pull request #287 from pasevin/master

Version bump 2.4.1 with new ReadMe

[id] name change and support for Angular 9

I changed the way we get the id of the <input> inside validator. Previously it was passed with the FormControl value, which is not technically a part of input value which should be validated. So instead now I inject nativeElement into each control passed to the validator, where I can find and access input we're checking and get its id. This will allow in the future to get other nativeElement values we want to access.

While refactoring, I noticed another issue with [id] property which is that when used, it will create a duplicate id on ngx-intl-tel-input and child <input>. This ended up in invalid HTML and could create some other issues.

To avoid the above issue, I've renamed [id] property to [inputId].

!!! This version will break your implementation if you're already using [id] to identify your elements. !!!
To fix this just replace your [id] with [inputId]

Bonus:

• Added support for Angular 9.