Skip to content
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

⚠️ This library is risky to use ⚠️ #353

Open
wajchelooo opened this issue Jul 7, 2024 · 1 comment
Open

⚠️ This library is risky to use ⚠️ #353

wajchelooo opened this issue Jul 7, 2024 · 1 comment

Comments

@wajchelooo
Copy link

⚠️

Please consider adding a warning on npmjs that this library is risky to use because of number of broken features. This library is not scalable, not flexible, doesnt support RWD, doesnt support various cases and should be used only for very simple scenarios.

And least temporarily until someone handles this library and maintains it. Thank you.

⚠️

@vrinceanuvalentin
Copy link

⚠️

Please consider adding a warning on npmjs that this library is risky to use because of number of broken features. This library is not scalable, not flexible, doesnt support RWD, doesnt support various cases and should be used only for very simple scenarios.

And least temporarily until someone handles this library and maintains it. Thank you.

⚠️

I think some of these things are related to you only. The features it has, they work as expected for me. The flexibility... well, here I think is from use case to use case, maybe you need something more than the package offers, but that is not a reason to mark this with a warning. There are lots of libraries that may offer more. If we would go go after your way on marking npm packages, I think over 90% should be marked with warnings and red flags, because it doesn't meet your standards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants