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

Consider using SweetAlert2 instead of SweetAlert #120

Closed
limonte opened this issue Mar 18, 2020 · 1 comment
Closed

Consider using SweetAlert2 instead of SweetAlert #120

limonte opened this issue Mar 18, 2020 · 1 comment

Comments

@limonte
Copy link

limonte commented Mar 18, 2020

I would like to propose migrating from SweetAlert to SweetAlert2 - the supported fork of SweetAlert. The original reason for creating SweetAlert2 is the inactivity of SweetAlert: https://stackoverflow.com/a/27842854/1331425

Reasons to switch:

  1. More great features like toasts which were requested in Toast SweetAlert2 #119

  2. Accessibility (WAI-ARIA) - SweetAlert2 is fully WAI-ARIA compatible and supports all popular screen-readers. Accessibility is a must in 2019, there are a lot of explanatory and tech articles, but this one is truly inspirable: Software development 450 words per minute

  3. Better buttons contrast is a huge advantage for all users especially for users with vision disabilities.

  4. Better support, average time to resolve an issue:

    • SweetAlert:
    • SweetAlert2:
  5. SweetAlert2 is twice more popular that SweetAlert: https://www.npmtrends.com/sweetalert-vs-sweetalert2

image


I can contribute with a PR if needed. After migrating, I can add the link to this project to https://github.com/sweetalert2/sweetalert2#related-community-projects so users can discover it

@uxweb
Copy link
Owner

uxweb commented Mar 21, 2020

Awesome, go ahead!

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

No branches or pull requests

2 participants