-
-
Notifications
You must be signed in to change notification settings - Fork 398
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Angular – standalone component compatibility with LucideAngularModule.pick #1288
Comments
Thanks for the bug report, @R-Bower, I'm a bit busy at the moment, but I will get to this as soon as my time allows. |
hey, @karsa-mistmere has anything come up on this ticket yet? I want to use the Lucide icons in any case and also just in the combination with angular 16 and standalone components :) |
@R-Bower, @Bonus2712: This should now be resolved in the latest release https://github.com/lucide-icons/lucide/releases/tag/0.269.0 Sorry this took so long (especially seeing how simple the fix was). Let me know if you run into anything else. |
Hi @karsa-mistmere. I appreciate your work on this bug. I am currently trying to get lucide-angular to work with standalone components as well. I have followed the steps to reproduce and I am still seeing errors in my project. I am using version I am receiving these errors while running my app:
and
Please let me know if there is any other information that will help with your investigation. I would love to use standalone components and lucid-angular! |
Hey @seangolob, As a workaround you can do either of the following:
(My preferred modus operandi is 1B) |
@karsa-mistmere Thank you for your guidance. I am new to the angular space and I am still getting my bearings straight. Thank you! |
Prerequisites
Step to reproduce
Follow the installation guide on the npm page for lucide-angular.
Try to use with a standalone component.
Actual behavior
The code does not compile.
Compilation error:
TS2322:
Type 'ModuleWithProviders ' is not assignable to type 'readonly any[] | Type '
Notes
The current import strategy is not compatible with Angular's standalone components.
The text was updated successfully, but these errors were encountered: