refactor: use angular signals, standalone component

[lekhmanrus]

Please check if the PR fulfills these requirements

• The commit messages follow these guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x")

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Other. Please describe:

If it is a Bugfix, please describe the root cause and what could have been done to prevent it…

What is the current behavior? (You can link to an open issue here, add screenshots…)
Regular @Inputs used as well as OnChanges hook.

What is the new behavior?
Angular Signals with build-in validation; refactored to standalone components.

Does this PR introduce a breaking change? (check one with "x")

• Yes
• No

If this PR contains a breaking change, please describe the impact and migration
path for existing applications: …

Other information (if applicable):
close #158

I would suggest using versions consistent with major Angular versions. Let's say ngx-skeleton-loader v18 for Angular v18, etc.

Please @mention @people to review this PR…
@willmendesneto

[willmendesneto]

🚀 Thanks for your contribution. 🚀

In regards of your question of Angular deps, this package (along all angular modules in general) should cover the actively supported versions. More details in these links:

• https://angular.dev/reference/versions#actively-supported-versions
• https://angular.dev/reference/releases#actively-supported-versions

In summary, nicely done! I'm adding some comments since some checks were removed when they shouldn't and the pull request is dealing with 2 different issues at the same time, which increases the level of validation.

Feel free to ping if you need more info

[TomLBarden]

Hi! The issue this PR resolves is currently blocking my upgrade to Angular 19. Any chance of some movement on this in the near future?

[willmendesneto]

@lekhmanrus Could you solve the conflicts on the package-lock.json, please? I can solve that by EOD, if I didn't get any replies from your side

[lekhmanrus]

@willmendesneto, Absolutely! Done. Thanks! 😊

[willmendesneto]

Thanks for the contribution, @lekhmanrus ! Massive kudos!

[willmendesneto]

And I'm more than happy to announce that: it's alive!

Please upgrade your projects to use ngx-skeleton-loader@10.0.0 and enjoy these changes in your app!

Once again, thanks @lekhmanrus for that! cc/ @TomLBarden @chimurai @yharaskrik