-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Repo size #557
Comments
Thanks for pointing this out, but does it really matter ? The goal is to try out angular and its ecosystem. If one day, those librairies stop me from uprading, i will remove them, but for now, I don't see any issues with them. |
As someone who always runs out of space, I'd prefer less dependencies especially if they aren't really used. |
Ok I understand. I still prefer to let them right now, because i like playing around with the library and this repo is kind of a playground where I can test and try new features from all librairies. |
This issue is stale because it has been open for 20 days with no activity. |
stale |
The size of the repo has doubled in the past few months. I'd suggest you remove
rx-angular
from dependencies. Unless you have anrx-angular
challenge in progess, I'd remove it.rx-angular
has 4,000 npm downloads a week. Niche dependencies like@ngrx/signals
(7,000 a week) can added per PR. If you remove rx-angular etc, previous PR could break so you'd have to add a warning to the docs when checking out a PR with rx-angular or any removed dependency.The text was updated successfully, but these errors were encountered: