Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Drop withNoNewKeyword in coming major release
See original GitHub issueThe coming major release gives us the opportunity to drop this complexity and source of issue #1281 (so users can import uncompiled code from the src/ directory again).
This would mean a breaking change as users would need to change their usage from Swal({...options}) to new Swal({...options}), or if nothing is done with the result, and the eslint no-new rule is in effect, Swal.fire({...options}). I think for the sake of simplicity it might be best to only use the latter Swal.fire() in documentation, tests, issue descriptions, etc.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Sorry, I’ve been really busy with work and personal life, so I wouldn’t be able to handle this myself right away. Should be fairly simple though.
🎉 This has been shipped in version 8.0.0 🎉
The release is available on:
Your semantic-release bot 📦🚀