sweetalert2 | Meteor Package for sweetAlert2 : a beautiful replacement | Web Framework library

You've phrased this question as if SweetAlert2 is not respecting your then, but I think it's actually the case that jQuery is not waiting for or respecting your return false; you're issuing it in an async function and jQuery simply doesn't know how to await Promises in event handlers.

Your function passed to on returns a Promise, because all async functions return a Promise in all cases. It seems like you want the return false to cancel the default behavior of the #upload-it button that presumably submits a form, but JavaScript event handlers don't understand when event handlers return Promises, and jQuery doesn't either. This makes it impossible to use return false to cancel the default behavior in an async function event handler.

Instead, make sure to immediately prevent the default behavior and stop propagation before awaiting anything, which you can do by calling methods on the event object. Having prevented the default behavior, you won't be able to "continue" it once the async function completes, but you can still programmatically submit the form.

As Indicated by OP

The issue was resolved by changing the: Base href on his index.html

Incorrect

Correct

In OP's Case the compiler was expecting a forwardSlash / At the end of the href.

This means the base href on Index.html would be as follows:

From the creator of SweetAlert2:

The SweetAlert repo seems to be unmaintained. There's a bunch of Pull Requests without any replies, the last merged pull request was on Nov 9, 2014.

I created SweetAlert2 with HTML support in modal and some other options for customization modal window - width, padding, Esc button behavior, etc.

TLDR: The original SweetAlert hasn't been updated since Apr 29 2019, and has ignored many recent pull requests. The creator of the new SweetAlert2 stated they wanted to add some new features so that's why they created SweetAlerts2.

I forgot to put the value claimtype and claim value and the userId in the [AspNetUserClaims] table of .net Identity. I am using JSON web token jwtToken for the WebAPI and adding the claim from the database to the token and the token is used to check in angular app if user is admin to manipulate the menu.

Okay that was dumb. But yes, to read those error message for other npm newbs out there:

Just using simple HTML CSS would definitely work. Here's a solution to get the required output just with HTML and CSS try the code below,

It looks like you're trying to setup the SweetAlert instance (this.$swal in your components) with initialization options. That could be done when installing the vue-sweetalert plugin. The second argument to Vue.use() is for the plugin options:

After some research and no luck, try and error was the best way to get an apropiate solution.

First, overwrite some css styles from the sweetalert2 library:

Here is a simple integration, try and let me know