Stuck on an issue?
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.
bower error - export default sweetAlert
See original GitHub issueAfter updating to the latest version of sweetalert2 via bower, chrome gives me the following error:
Uncaught SyntaxError: Unexpected token export at the line export default sweetAlert. I have not received this error with previous versions.
Issue Analytics
- State:
- Created 7 years ago
- Comments:17 (9 by maintainers)
Top Results From Across the Web
Error: export 'default' (imported as 'Swal') was not found in ' ...
I had this exact same error, problem was that I was exporting the component as: const Component = () => { Swal.fire({ //configs....
Read more >Class constructor SweetAlert cannot be invoked without ...
Hi, After updating meteor version, I can not use the sweetalert2 npm package. import swal from 'sweetalert2'; import { TAPi18n } from ...
Read more >react-sweetalert2
Start using react-sweetalert2 in your project by running `npm i ... export default withSwal((props, ref) => { const { swal, ...
Read more >SweetAlert
What does it do? Here's a comparison of a standard error message. The first one uses the built-in alert-function, while the second is...
Read more >SweetAlert2 in Vue component on Laravel 5.4
I have installed using npm, tried to import the node module folder into my ... It still gave me the same error ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thank you @limonte! Rails Assets is including the correct file now.
According to this github issue it’s possible to manually choose the file. The way this projects bower.json is setup (as per the official bower docs) it references the source file which is what’s causing the issue. You actually want a specific build.