@ng-icons/ionicons 18.0.1 → 18.0.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +3 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -112,16 +112,16 @@ You can then use the icon in your templates:
|
|
|
112
112
|
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
|
|
113
113
|
would be in the `@Component` providers array.
|
|
114
114
|
|
|
115
|
-
You can also import the component directly by importing `
|
|
115
|
+
You can also import the component directly by importing `NgIconComponent` or the `NG_ICON_DIRECTIVES` constant.
|
|
116
116
|
|
|
117
117
|
```ts
|
|
118
|
-
import {
|
|
118
|
+
import { NgIconComponent, provideIcons } from '@ng-icons/core';
|
|
119
119
|
import { FeatherAirplay } from '@ng-icons/feather-icons';
|
|
120
120
|
import { HeroUsers } from '@ng-icons/heroicons/outline';
|
|
121
121
|
|
|
122
122
|
@Component({
|
|
123
123
|
standalone: true,
|
|
124
|
-
imports: [
|
|
124
|
+
imports: [NgIconComponent],
|
|
125
125
|
providers: [provideIcons({ FeatherAirplay, HeroUsers })],
|
|
126
126
|
})
|
|
127
127
|
export class AppComponent {}
|