@ng-icons/ionicons 29.10.0 → 30.1.0

package/README.md

@@ -9,7 +9,7 @@
 # Ng Icons
 
 The all-in-one icon library for Angular. This allows you to use icons from multiple icon sets with a single icon component.
-Containing over 61,000 icons for you to use in your projects.
+Containing over 66,000 icons for you to use in your projects.
 
 Currently, we support the following libraries:
 
@@ -40,6 +40,7 @@ Currently, we support the following libraries:
 - [Huge Icons](https://hugeicons.com/)
 - [Devicon](https://github.com/devicons/devicon/)
 - [Game Icons](https://game-icons.net/)
+- [Flag Icons](https://flagicons.lipis.dev/)
 
 Got suggestions for additional iconsets? Create an issue and we can consider adding them!
 
@@ -61,6 +62,7 @@ Ng Icons is an MIT-licensed open source project with its ongoing development mad
 | 16.x.x          | 25.x.x          |
 | 17.x.x          | 26.x.x - 27.x.x |
 | 18.x.x          | 28.x.x - 29.x.x |
+| 19.x.x          | 30.x.x          |
 
 > **Note**: Ng Icons relies on modern browser features and is designed to work on evergreen browsers. We do not support older browsers such as IE11.
 
@@ -150,16 +152,16 @@ You can then use the icon in your templates:
 As of version 18.0.0 Ng Icons nows supports standalone components. You can import icons using the `provideIcons` function which can be placed anywhere you can register providers. The optimal location
 would be in the `@Component` providers array.
 
-You can also import the component directly by importing `NgIconComponent` or the `NG_ICON_DIRECTIVES` constant.
+You can also import the component directly by importing `NgIcon` or the `NG_ICON_DIRECTIVES` constant.
 
 ```ts
-import { NgIconComponent, provideIcons } from '@ng-icons/core';
+import { NgIcon, provideIcons } from '@ng-icons/core';
 import { featherAirplay } from '@ng-icons/feather-icons';
 import { heroUsers } from '@ng-icons/heroicons/outline';
 
 @Component({
   standalone: true,
-  imports: [NgIconComponent],
+  imports: [NgIcon],
   providers: [provideIcons({ featherAirplay, heroUsers })],
 })
 export class AppComponent {}
@@ -183,12 +185,12 @@ export class ParentComponent {
 }
 
 // child.component.ts
-import { NgIconComponent } from '@ng-icons/core';
+import { NgIcon } from '@ng-icons/core';
 
 @Component({
   standalone: true,
   selector: 'app-child',
-  imports: [NgIconComponent],
+  imports: [NgIcon],
   template: '<ng-icon [svg]="icon" />',
 })
 export class ChildComponent {
@@ -221,7 +223,7 @@ export class AppModule {}
 #### Standalone
 
 ```ts
-import { NgIconComponent, provideIcons, provideNgIconsConfig } from '@ng-icons/core';
+import { NgIcon, provideIcons, provideNgIconsConfig } from '@ng-icons/core';
 
 bootstrapApplication(AppComponent, {
   providers: [
@@ -237,7 +239,7 @@ bootstrapApplication(AppComponent, {
 If your application has a strict Content Security Policy (CSP) you may need to add the following to your global configuration to ensure you do not get any errors.
 
 ```ts
-import { NgIconComponent, provideIcons, provideNgIconsConfig, withContentSecurityPolicy } from '@ng-icons/core';
+import { NgIcon, provideIcons, provideNgIconsConfig, withContentSecurityPolicy } from '@ng-icons/core';
 
 bootstrapApplication(AppComponent, {
   providers: [provideNgIconsConfig({}, withContentSecurityPolicy())],
@@ -252,7 +254,7 @@ Should you want stricter checks you can enable the `ExceptionLogger` which will
 You can enable this by providing the `withExceptionLogger` function to the `provideNgIconsConfig` function.
 
 ```ts
-import { NgIconComponent, provideIcons, provideNgIconsConfig, withExceptionLogger } from '@ng-icons/core';
+import { NgIcon, provideIcons, provideNgIconsConfig, withExceptionLogger } from '@ng-icons/core';
 
 bootstrapApplication(AppComponent, {
   providers: [provideNgIconsConfig({}, withExceptionLogger())],