# sweetalert

**Repository Path**: caixiang22/sweetalert

## Basic Information

- **Project Name**: sweetalert
- **Description**: No description available
- **Primary Language**: Unknown
- **License**: MIT
- **Default Branch**: master
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 0
- **Created**: 2026-03-03
- **Last Updated**: 2026-03-03

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

> If you are looking for the non-Bootstrap version refer to the original
> [SweetAlert project](https://github.com/t4t5/sweetalert).

# SweetAlert for Bootstrap

[![npm version](https://badge.fury.io/js/bootstrap-sweetalert.svg)](https://badge.fury.io/js/bootstrap-sweetalert)
[![Bower version](https://badge.fury.io/bo/bootstrap-sweetalert.svg)](https://badge.fury.io/bo/bootstrap-sweetalert)
[![Code Shelter](https://www.codeshelter.co/static/badges/badge-flat.svg)](https://www.codeshelter.co/)

An awesome _replacement_ for JavaScript's `alert()` made for Bootstrap.


## Usage

On how to use these alerts, read the docs from the original
[SweetAlert](http://t4t5.github.io/sweetalert) project.

The main difference here is that instead of using the `confirmButtonColor` you
should use the `confirmButtonClass`. It can take any of the default Bootstrap
classes for buttons like: `btn-danger`, `btn-success`, etc. The rest of the API
remains exactly the same.

Also if you are using Less in your project, then instead of including the
`*.css` files include the
[`sweet-alert.less`](https://github.com/lipis/bootstrap-sweetalert/blob/master/lib/sweet-alert.less)
in your building process. That way it will use the Bootstrap's variables to
match your theme perfectly.


## Development

```shell
$ npm install
$ grunt
```

### Run tests
```shell
$ npm install
$ bower install
$ grunt test
```