The library was missing package description.
With it being added, the lib will be more explicit when searching in npmjs api, and will be displayed correctly in this report:
https://github.com/GoncharIgor/libs-inspector
* docs: Fix simple typo, globaly -> globally
There is a small typo in docsSource/sections/01-usage.md, docsSource/sections/02-utilities.md.
Should read `globally` rather than `globaly`.
* Rebuild docs
* Add community discord server
* Add favicon and meta tags
* Fix for Issue #1102
* Update build
* Remove community
Co-authored-by: Waren Gonzaga <warengonzaga.dev@gmail.com>
Adding `{once : true}` to `node.addEventListener` causes the event trigger to be removed after first use. This built-in method cleans up the requirement to remove event within event handler.
* New animations added
* Update
* Update
* Update
* Update
* kill bower
* Turn off animations for print media query (#856)
* Add a feature to turn off animations for printing as requested.
* Add print media type
* Update the builds
* Moved away from gulp to npx + postcss
This PR changes the build system for a simpler one, using only npx as runner and postcss to process all the files.
* Solves #618
* Solves #836
* Also solves #758 just for fun ;P
* Updated travis and removed animate-config.json
* Removed strayed gulpfile and trimmed the header
* Moved prefix config to package.json and updated the tasks
* Updated travis
* Updated dependencies and postcss config
* Now using CSS custom properties
* Add css module file - solves #933
* Updated README for the new build
* Rebulit files
* Updated dependencies + added browserlist
* Fixed small typo on README
* Added imports to Back animations
* Added FadeInTopLeft.css file
Fade in the animation diagonally
* Added fadeInTopRight.css file
Fade in the animation diagonally
* Added fadeInBottomLeft.css
* Added fadeInBottomRight.css
* Added fadeOutTopLeft.css
* Added fadeOutTopRight.css
* Added fadeOutBottomRight.css
* Added fadeOutBottomLeft.css
* Added imports to diagonal fadings
* Aditional formatting
* Added diagonal fadings to README
* Fixes#966
* Animate.css v4 Updates (#1029)
* Update to v4
* Add Iteration-Count CSS utility classes solves #998
* Updated builds
* Update lightSpeed animations
* Update builds
* Fix Invalid CSS Media Query Syntax
* Update build
* Add gitpod support
* Add newline in gitpod file
* Update README
* Revert
* Declare variable
* Update builds
* Remove Gitpod support
Co-authored-by: Waren Gonzaga <warengonzaga.dev@gmail.com>
* Improves building process and package.json tidy up
* Improved animations (#901)
* Improved bounce
* Improved pulse
* Improved bounceInDown
* Improved bounceInLeft
* Improved bounceInRight
* Improved bounceInUp
* Improved bounceOutDown
* Improved bounceOuLeft
* Improved bounceOuRight
* Improved bounceOutRight
* Improved fadeInDown
* Improved fadeInDownBig
* Improved fadeInLeft
* Improved fadeInLeftBig
* Improved fadeInRightBig
* Improved fadeInUp
* Improved fadeInUpBig
* Improved fadeInRight
* Reverted fade animations
* Compiled
* Updated prefers-reduced-motion support on README
* Add .delay-1s (#982)
The .delay-1s is missing from the readme
* HTTPS relevant links on README (#972)
prevents HTTP redirects
* Create CONTRIBUTING.md (#1033)
Co-authored-by: Melek REBAI <melek.rebai89@gmail.com>
Co-authored-by: Christian Oliff <christianoliff@yahoo.com>
Co-authored-by: Daniel Eden <dan.eden@me.com>
* Updates dependencies
* Updates prettier config
* refactory transform-origin in styles
* animation shake with X and Y options 🔨
* Adds shakeX and shakeY to the build
* Set 0 Opacity to Out animation classes (#1043)
* Update issue templates
* Add 0 opacity to out classes
* Update builds
* Improved implemenation
* Update builds
* Update current readme
* Update builds
Co-authored-by: Elton Mesquita <callmeelton@gmail.com>
Co-authored-by: Waren Gonzaga <warengonzaga.dev@gmail.com>
* Removes prefix from att selector
* Feature/new demo site (#1046)
* Simplify & centralize the Animate.css home page. Finally.
* Design tweak
* Fix Lightspeed demos
* Fix Lightspeed demos (cont.)
* Trigger animation on change as well as click
* Correct jQuery example. Fixes#127
* Remove Readme on gh-pages to prevent mistakes like ee75b81
* Use animate.min.css because whatever
* Update demo page with MS animation JS hooks.
* Updating home page with rubberBand animation.
* Reverse hue animation
Red-orange-brown isn’t a great first impression.
* Add readme, use cssmin minified CSS instead of csso
* Update gh-pages
* Remove protocol from urls
Fixes Chrome’s SSL issue
* Remove Square Cash link
Donations are weird, and only US account holders could use this.
* Updating Gh-page animate.css to the current version
This is a simple commit, bringing animate.css up to date with the current master version.
* Updating Gh-page animate.min.css to reflect the current version
This is a simply update to the Animate.min.css file, to reflect the current version
* Update CSS
* Updating Gh-page index.html to the reflect the addition of zooms (in out down etc)
This adds the optgroup "zoom", and associated options of: ZoomIn, zoomOut, zoomInDown, zoomInUp, zoomInLeft, zoomInRight, zoomOutLeft, zoomOutRight, zoomOutUp, and zoomOutDown.
* refactoring index.html to mimic the current optgroup styling
I added zooms, which were absent, but added them in a way that didn't reflect the current optgroup styling and delineation. I fixed that and now exits and entrances are grouped appropriately.
* updated index.html to reflect the standard optgroup styling on sliders, added slideInDown
In addition to adding slider keyframes that were missing, I placed them into the appropriate optgroups to mimic the similar styling of the other animations.
* Merging updated version of animate.min.css
As requested, this is the updated version of animate.min.css that @daneden request I include in the pull request.
* Updated animate.min.css
Made it the new version
* added jello to options
* Update CSS
* Add jackInTheBox to gh-pages (#694)
* New Special - jackInTheBox
* copy min.css from master branch
* fixed the issue of overflow scroll (#740)
for more see this issue https://github.com/daneden/animate.css/issues/739
* Adds heartBeat animation demo (#893)
* Update animate.min.css to latest version
* Updated CSS for current browsers
* Updated animate.css
* Removed useless test folder
* Added warn about prefers-reduced-motion
* Adds docs compiler
* Adds new base template
* Improves the docs compiler
* Fixes flipOutY animation
* Updates docs template and build
* Reorder docs sections
* Updates docs animation list template
* Updates prettier ignore
* Adds syntax highlight to docs
* Small fixes to docs content
* Updates templates HTML
* Styles the demo website
* Adds functionality to demo website
* Fixes small website demo issue with medium screens
* Adds copy animation to demo site
* Renames loop classes to repeat
* Small adjusts to docs styles
* Updates docs template
* Updates docs improving copy and adding sections
* Reviews the docs copy
* Fix some issues with demo-site
* Fixes issue with the demo-site playground
* Adjusts tooltip on demo-site
* Fix layout issues on mobile and update “close” button for animations list
Co-authored-by: Daniel Eden <dan.eden@me.com>
Co-authored-by: Matt Willis <contact@mrwillis.net>
Co-authored-by: Gabrielmtn <Gabrielmtn@gmail.com>
Co-authored-by: Indy Prieto <proforced@gmail.com>
Co-authored-by: Robert Pemberton <hellorobertp@gmail.com>
Co-authored-by: Khaled nuur <kahalidnuur@gmail.com>
Co-authored-by: Vladimir Jovanović <vladimir.jovanovic993@gmail.com>
* Updates docs folders
* Fix some small documentation issues
* Updates edit on github link
Co-authored-by: Arda Gedik <arnoldsivastanegezer@hotmail.com>
Co-authored-by: Arda Gedik <ardagedikk@hotmail.com>
Co-authored-by: Jabran Rafique <jabran.rafique@ratedpeople.com>
Co-authored-by: Waren Gonzaga <waren.gonzaga.dev@gmail.com>
Co-authored-by: Jabran Rafique⚡️ <jabranr@users.noreply.github.com>
Co-authored-by: Vaibhav Tandon <vaibhav.tandongcet@gmail.com>
Co-authored-by: Waren Gonzaga <warengonzaga.dev@gmail.com>
Co-authored-by: Melek REBAI <melek.rebai89@gmail.com>
Co-authored-by: Christian Oliff <christianoliff@yahoo.com>
Co-authored-by: Daniel Eden <dan.eden@me.com>
Co-authored-by: Lucas Ferreira Lima <lucasferreiralimax@gmail.com>
Co-authored-by: Matt Willis <contact@mrwillis.net>
Co-authored-by: Gabrielmtn <Gabrielmtn@gmail.com>
Co-authored-by: Indy Prieto <proforced@gmail.com>
Co-authored-by: Robert Pemberton <hellorobertp@gmail.com>
Co-authored-by: Khaled nuur <kahalidnuur@gmail.com>
Co-authored-by: Vladimir Jovanović <vladimir.jovanovic993@gmail.com>
* Update the devDependencies
* Update the gitignore file
* Update the version of gulp
* Fix the build error in the gulpfile script
* Update node version testing for travis
* Update the package.json
* Fix some errors
* Update the devdependencies
* Re arrange the .gitignore
* Update devdependency to the latest stable version
* Add new line at the end of the file
* Fix versioning error
* Update DevDependencies
* Update the version from 3.6.1 into 3.6.2
* Add delays up to 5 seconds
* Update the files from 3.6.1 into 3.6.2
* Modify the documentation and add delay option
* Update the devDependencies
* Update the gitignore file
* Update the version of gulp
* Fix the build error in the gulpfile script
* Update node version testing for travis
In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
## Our Standards
Examples of behavior that contributes to creating a positive environment include:
- Using welcoming and inclusive language
- Being respectful of differing viewpoints and experiences
- Gracefully accepting constructive criticism
- Focusing on what is best for the community
- Showing empathy towards other community members
Examples of unacceptable behavior by participants include:
- The use of sexualized language or imagery and unwelcome sexual attention or advances
- Trolling, insulting/derogatory comments, and personal or political attacks
- Public or private harassment
- Publishing others' private information, such as a physical or electronic address, without explicit permission
- Other conduct which could reasonably be considered inappropriate in a professional setting
## Our Responsibilities
Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
## Scope
This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
## Enforcement
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at animate@eltonmesquita.com. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
## Attribution
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
[homepage]: https://www.contributor-covenant.org
For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq
Thanks for your interest in contributing to Animate.css! Before contributing, please make sure you understand the guidelines provided here. Animate.css is widely used, so it’s important to maintain a high level of quality and to contribute with the interests of the community in mind.
## Design Guidelines
Animations, like many facets of visual and interaction design, can be highly subjective. Maintaining a consistent library of animations in an active community can be difficult; these design guidelines are designed to help encourage thoughtful criticism of new animations that are proposed for Animate.css.
The animations in Animate.css should follow a few key principles:
- **Animations should be subtle.** Avoid creating animations that involve large translations, or span a natural duration of longer than 1 second.
- **Animations should be tolerable.** Related to subtlety, animations should be tolerable—seeing them repeatedly should not become too annoying or overbearing.
- **Animations should not interfere with document flow or control/input availability.** In other words, the absence of an animation should never reduce usability of a product: they should be non-critical and seen as “progressive enhancements”. Avoid animations that change properties such as `position` or `display`.
- **Animations should be helpful.** They should be designed to guide users to a point of interest, ease natural reading order, or to communicate relationships between elements.
- **Animations should feel familiar.** Avoid introducing animations that feel out-of-place compared to the existing set.
- **Animations should feel natural.** Animations should reflect, as much as is reasonable, motion that occurs in natural physics. Avoid extreme timing functions, and model animations on real-world events.
## Code Styling
1. Match the naming convention (camelCase, categorized [fades, bounces, etc])
2. Indent with two spaces
3. End each file with a blank line
4. Make sure you have an editorconfig plugin/extension enabled in your editor and all the dependencies installed so editorconfig and prettier can automatically format your code when committing.
## How To Contribute
1. [Fork](https://help.github.com/articles/fork-a-repo/) the project
2. Create a new topic branch on your local forked copy
3. Push your topic branch up to your fork
4. Create a [pen](https://codepen.io/) demonstrating what your change will do.
5. [Open a Pull Request](https://help.github.com/articles/about-pull-requests/) with a clear title and description against the `main` branch.
Animate.css Copyright 2021 Daniel Eden (“Licensor”)
Copyright (c) 2016 Daniel Eden
Hippocratic License Version Number: 2.1.
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
Purpose. The purpose of this License is for the Licensor named above to permit the Licensee (as defined below) broad permission, if consistent with Human Rights Laws and Human Rights Principles (as each is defined below), to use and work with the Software (as defined below) within the full scope of Licensor’s copyright and patent rights, if any, in the Software, while ensuring attribution and protecting the Licensor from liability.
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
Permission and Conditions. The Licensor grants permission by this license (“License”), free of charge, to the extent of Licensor’s rights under applicable copyright and patent law, to any person or entity (the “Licensee”) obtaining a copy of this software and associated documentation files (the “Software”), to do everything with the Software that would otherwise infringe (i) the Licensor’s copyright in the Software or (ii) any patent claims to the Software that the Licensor can license or becomes able to license, subject to all of the following terms and conditions:
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
* Acceptance. This License is automatically offered to every person and entity subject to its terms and conditions. Licensee accepts this License and agrees to its terms and conditions by taking any action with the Software that, absent this License, would infringe any intellectual property right held by Licensor.
* Notice. Licensee must ensure that everyone who gets a copy of any part of this Software from Licensee, with or without changes, also receives the License and the above copyright notice (and if included by the Licensor, patent, trademark and attribution notice). Licensee must cause any modified versions of the Software to carry prominent notices stating that Licensee changed the Software. For clarity, although Licensee is free to create modifications of the Software and distribute only the modified portion created by Licensee with additional or different terms, the portion of the Software not modified must be distributed pursuant to this License. If anyone notifies Licensee in writing that Licensee has not complied with this Notice section, Licensee can keep this License by taking all practical steps to comply within 30 days after the notice. If Licensee does not do so, Licensee’s License (and all rights licensed hereunder) shall end immediately.
* Compliance with Human Rights Principles and Human Rights Laws.
1. Human Rights Principles.
(a) Licensee is advised to consult the articles of the United Nations Universal Declaration of Human Rights and the United Nations Global Compact that define recognized principles of international human rights (the “Human Rights Principles”). Licensee shall use the Software in a manner consistent with Human Rights Principles.
(b) Unless the Licensor and Licensee agree otherwise, any dispute, controversy, or claim arising out of or relating to (i) Section 1(a) regarding Human Rights Principles, including the breach of Section 1(a), termination of this License for breach of the Human Rights Principles, or invalidity of Section 1(a) or (ii) a determination of whether any Law is consistent or in conflict with Human Rights Principles pursuant to Section 2, below, shall be settled by arbitration in accordance with the Hague Rules on Business and Human Rights Arbitration (the “Rules”); provided, however, that Licensee may elect not to participate in such arbitration, in which event this License (and all rights licensed hereunder) shall end immediately. The number of arbitrators shall be one unless the Rules require otherwise.
Unless both the Licensor and Licensee agree to the contrary: (1) All documents and information concerning the arbitration shall be public and may be disclosed by any party; (2) The repository referred to under Article 43 of the Rules shall make available to the public in a timely manner all documents concerning the arbitration which are communicated to it, including all submissions of the parties, all evidence admitted into the record of the proceedings, all transcripts or other recordings of hearings and all orders, decisions and awards of the arbitral tribunal, subject only to the arbitral tribunal's powers to take such measures as may be necessary to safeguard the integrity of the arbitral process pursuant to Articles 18, 33, 41 and 42 of the Rules; and (3) Article 26(6) of the Rules shall not apply.
2. Human Rights Laws. The Software shall not be used by any person or entity for any systems, activities, or other uses that violate any Human Rights Laws. “Human Rights Laws” means any applicable laws, regulations, or rules (collectively, “Laws”) that protect human, civil, labor, privacy, political, environmental, security, economic, due process, or similar rights; provided, however, that such Laws are consistent and not in conflict with Human Rights Principles (a dispute over the consistency or a conflict between Laws and Human Rights Principles shall be determined by arbitration as stated above). Where the Human Rights Laws of more than one jurisdiction are applicable or in conflict with respect to the use of the Software, the Human Rights Laws that are most protective of the individuals or groups harmed shall apply.
3. Indemnity. Licensee shall hold harmless and indemnify Licensor (and any other contributor) against all losses, damages, liabilities, deficiencies, claims, actions, judgments, settlements, interest, awards, penalties, fines, costs, or expenses of whatever kind, including Licensor’s reasonable attorneys’ fees, arising out of or relating to Licensee’s use of the Software in violation of Human Rights Laws or Human Rights Principles.
* Failure to Comply. Any failure of Licensee to act according to the terms and conditions of this License is both a breach of the License and an infringement of the intellectual property rights of the Licensor (subject to exceptions under Laws, e.g., fair use). In the event of a breach or infringement, the terms and conditions of this License may be enforced by Licensor under the Laws of any jurisdiction to which Licensee is subject. Licensee also agrees that the Licensor may enforce the terms and conditions of this License against Licensee through specific performance (or similar remedy under Laws) to the extent permitted by Laws. For clarity, except in the event of a breach of this License, infringement, or as otherwise stated in this License, Licensor may not terminate this License with Licensee.
* Enforceability and Interpretation. If any term or provision of this License is determined to be invalid, illegal, or unenforceable by a court of competent jurisdiction, then such invalidity, illegality, or unenforceability shall not affect any other term or provision of this License or invalidate or render unenforceable such term or provision in any other jurisdiction; provided, however, subject to a court modification pursuant to the immediately following sentence, if any term or provision of this License pertaining to Human Rights Laws or Human Rights Principles is deemed invalid, illegal, or unenforceable against Licensee by a court of competent jurisdiction, all rights in the Software granted to Licensee shall be deemed null and void as between Licensor and Licensee. Upon a determination that any term or provision is invalid, illegal, or unenforceable, to the extent permitted by Laws, the court may modify this License to affect the original purpose that the Software be used in compliance with Human Rights Principles and Human Rights Laws as closely as possible. The language in this License shall be interpreted as to its fair meaning and not strictly for or against any party.
* Disclaimer. TO THE FULL EXTENT ALLOWED BY LAW, THIS SOFTWARE COMES “AS IS,” WITHOUT ANY WARRANTY, EXPRESS OR IMPLIED, AND LICENSOR AND ANY OTHER CONTRIBUTOR SHALL NOT BE LIABLE TO ANYONE FOR ANY DAMAGES OR OTHER LIABILITY ARISING FROM, OUT OF, OR IN CONNECTION WITH THE SOFTWARE OR THIS LICENSE, UNDER ANY KIND OF LEGAL CLAIM.
This Hippocratic License is an Ethical Source license (https://ethicalsource.dev) and is offered for use by licensors and licensees at their own risk, on an “AS IS” basis, and with no warranties express or implied, to the maximum extent permitted by Laws.
`animate.css` is a bunch of cool, fun, and cross-browser animations for you to use in your projects. Great for emphasis, home pages, sliders, and general just-add-water-awesomeness.
1. Include the stylesheet on your document's `<head>`
> If you need the old docs - v3.x.x and under - you can find it [here](https://github.com/animate-css/animate.css/tree/a8d92e585b1b302f7749809c3308d5e381f9cb17).
```html
<head>
<linkrel="stylesheet"href="animate.min.css">
</head>
```
2. Add the class `animated` to the element you want to animate.
You may also want to include the class `infinite` for an infinite loop.
## _Just-add-water CSS animation_
3. Finally you need to add one of the following classes:
## Installation
* `bounce`
* `flash`
* `pulse`
* `rubberBand`
* `shake`
* `headShake`
* `swing`
* `tada`
* `wobble`
* `jello`
* `bounceIn`
* `bounceInDown`
* `bounceInLeft`
* `bounceInRight`
* `bounceInUp`
* `bounceOut`
* `bounceOutDown`
* `bounceOutLeft`
* `bounceOutRight`
* `bounceOutUp`
* `fadeIn`
* `fadeInDown`
* `fadeInDownBig`
* `fadeInLeft`
* `fadeInLeftBig`
* `fadeInRight`
* `fadeInRightBig`
* `fadeInUp`
* `fadeInUpBig`
* `fadeOut`
* `fadeOutDown`
* `fadeOutDownBig`
* `fadeOutLeft`
* `fadeOutLeftBig`
* `fadeOutRight`
* `fadeOutRightBig`
* `fadeOutUp`
* `fadeOutUpBig`
* `flipInX`
* `flipInY`
* `flipOutX`
* `flipOutY`
* `lightSpeedIn`
* `lightSpeedOut`
* `rotateIn`
* `rotateInDownLeft`
* `rotateInDownRight`
* `rotateInUpLeft`
* `rotateInUpRight`
* `rotateOut`
* `rotateOutDownLeft`
* `rotateOutDownRight`
* `rotateOutUpLeft`
* `rotateOutUpRight`
* `hinge`
* `rollIn`
* `rollOut`
* `zoomIn`
* `zoomInDown`
* `zoomInLeft`
* `zoomInRight`
* `zoomInUp`
* `zoomOut`
* `zoomOutDown`
* `zoomOutLeft`
* `zoomOutRight`
* `zoomOutUp`
* `slideInDown`
* `slideInLeft`
* `slideInRight`
* `slideInUp`
* `slideOutDown`
* `slideOutLeft`
* `slideOutRight`
* `slideOutUp`
Install with npm:
Full example:
```html
<h1class="animated infinite bounce">Example</h1>
```shell
npm install animate.css --save
```
[Check out all the animations here!](https://daneden.github.io/animate.css/)
Install with yarn:
##Usage
To use animate.css in your website, simply drop the stylesheet into your document's `<head>`, and add the class `animated` to an element, along with any of the animation names. That's it! You've got a CSS animated element. Super!
```html
<head>
<linkrel="stylesheet"href="animate.min.css">
</head>
```shell
yarn add animate.css
```
You can do a whole bunch of other stuff with animate.css when you combine it with jQuery or add your own CSS rules. Dynamically add animations using jQuery with ease:
You can find the Animate.css documentation on the [website](https://animate.style/).
You can also detect when an animation ends:
## Accessibility
<!--
Before you make changes to this file, you should know that $('#yourElement').one() is *NOT A TYPO*
Animate.css supports the [`prefers-reduced-motion` media query](https://webkit.org/blog/7551/responsive-design-for-motion/) so that users with motion sensitivity can opt out of animations. On supported platforms (currently all the majors browsers and OS), users can select "reduce motion" on their operating system preferences and it will turn off CSS transitions for them without any further work required.
You can change the duration of your animations, add a delay or change the number of times that it plays:
```css
#yourElement {
-vendor-animation-duration: 3s;
-vendor-animation-delay: 2s;
-vendor-animation-iteration-count: infinite;
}
```
*Note: be sure to replace "vendor" in the CSS with the applicable vendor prefixes (webkit, moz, etc)*
## Custom Builds
Animate.css is powered by [gulp.js](http://gulpjs.com/), and you can create custom builds pretty easily. First of all, you’ll need Gulp and all other dependencies:
```sh
$ cd path/to/animate.css/
$ sudo npm install
```
Next, run `gulp` to compile your custom builds. For example, if you want only some of the the “attention seekers”, simply edit the `animate-config.json` file to select only the animations you want to use.
Animate.css is licensed under the MIT license. (http://opensource.org/licenses/MIT)
Animate.css is licensed under the [Hippocratic License](http://firstdonoharm.dev).
## Code of Conduct
This project and everyone participating in it is governed by the [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to [animate@eltonmesquita.com](mailto:animate@eltonmesquita.com).
## Contributing
Pull requests are the way to go here. I apologise in advance for the slow action on pull requests and issues. I only have two rules for submitting a pull request: match the naming convention (camelCase, categorised [fades, bounces, etc]) and let us see a demo of submitted animations in a [pen](http://codepen.io). That last one is important.
Pull requests are the way to go here. We only have two rules for submitting a pull request: match the naming convention (camelCase, categorised [fades, bounces, etc]) and let us see a demo of submitted animations in a [pen](https://codepen.io). That **last one is important**.
> Animate.css v4 brought some **breaking changes**, please refer to the [migration guide](#migration) before updating from v3.x and under.
**Animate.css** is a library of ready-to-use, cross-browser animations for use in your web projects. Great for emphasis, home pages, sliders, and attention-guiding hints.
Or install with Yarn (this will only work with appropriate tooling like Webpack, Parcel, etc. If you are not using any tool for packing or bundling your code, you can simply use the CDN method below):
After installing Animate.css, add the class `animate__animated` to an element, along with any of the [animation names](#attention_seekers) (don't forget the `animate__` prefix!):
That's it! You've got a CSS animated element. Super!
> Animations can improve the UX of an interface, but keep in mind that they can also get in the way of your users! Please read the [best practices](#best-practices) and [gotchas](#gotchas) sections to bring your web-things to life in the best way possible.
#### Using `@keyframes`
Even though the library provides you a few helper classes like the `animated` class to get you up running quickly, you can directly use the provided animations `keyframes`. This provides a flexible way to use Animate.css with your current projects without having to refactor your HTML code.
Example:
```css
.my-element {
display: inline-block;
margin: 0 0.5rem;
animation: bounce; /* referring directly to the animation's @keyframe declaration */
animation-duration: 2s; /* don't forget to set a duration! */
}
```
Be aware that some animations are dependent on the `animation-timing` property set on the animation's class. Changing or not declaring it might lead to unexpected results.
#### CSS Custom Properties (CSS Variables)
Since version 4, Animate.css uses custom properties (also known as CSS variables) to define the animation's duration, delay, and iterations. This makes Animate.css very flexible and customizable. Need to change an animation duration? Just set a new value globally or locally.
Example:
```css
/* This only changes this particular animation duration */
.animate__animated.animate__bounce {
--animate-duration: 2s;
}
/* This changes all the animations globally */
:root {
--animate-duration: 800ms;
--animate-delay: 0.9s;
}
```
Custom properties also make it easy to change all your animation's time-constrained properties on the fly. It means that you can have a slow-motion or time-lapse effect with a javascript one-liner:
```javascript
// All animations will take twice the time to accomplish
Even though some aging browsers do not support custom properties, Animate.css provides a proper fallback, widening its support for any browser that supports CSS animations.
The `animate__animated` class has a default speed of `1s`. You can also customize the animations duration through the `--animate-duration` property, globally or locally. This will affect both the animations and the utility classes. Example:
```css
/* All animations will take twice as long to finish */
:root {
--animate-duration: 2s;
}
/* Only this element will take half the time to finish */
.my-element {
--animate-duration: 0.5s;
}
```
Notice that some animations have a duration of less than 1 second. As we used the CSS `calc()` function, setting the duration through the `--animation-duration` property will respect these ratios. So, when you change the global duration, all the animations will respond to that change!
### Repeating classes
You can control the iteration count of the animation by adding these classes, like below:
As with the delay and speed classes, the `animate__repeat` class is based on the `--animate-repeat` property and has a default iteration count of `1`. You can customize them by setting the `--animate-repeat` property to a longer or a shorter value:
```css
/* The element will repeat the animation 2x
It's better to set this property locally and not globally or
you might end up with a messy situation */
.my-element {
--animate-repeat: 2;
}
```
Notice that `animate__infinite` doesn't use any custom property, and changes to `--animate-repeat` will have no effect. Don't forget to read the [best practices](#best-practices) section to make the best use of repeating animations.
Animations can greatly improve an interface's UX, but it's important to follow some guidelines to not overdo it and deteriorate the user experience on your web-things. Following the following rules should provide a good start.
### Meaningful animations
You should avoid animating an element just for the sake of it. Keep in mind that animations should make an intention clear. Animations like attention seekers (bounce, flash, pulse, etc) should be used to bring the user's attention to something special in your interface and not only as a way to bring "flashiness" to it.
Entrances and exit animations should be used to orientate what is happening in the interface, clearly signaling that it's transitioning into a new state.
It doesn't mean that you should avoid adding playfulness to the interface, just be sure that the animations are not getting in the way of your user and that the page's performance is not affected by an exaggerated use of animations.
### Don't animate large elements
Avoid it as it won't bring much value to the user and will probably only cause confusion. Besides that, there is a good chance that the animations will be junky, culminating in bad UX.
### Don't animate root elements
Animating the `<html/>` or `<body/>` tags is possible, but you should avoid it. There were some reports pointing out that this could trigger some weird browser bugs. Besides, making the whole page bounce would hardly provide good value to your UX. If you indeed need this sort of effect, wrap your page in an element and animate it, like this:
Even though Animate.css provides utility classes for repeating animations, including an infinite one, you should avoid endless animations. It will just distract your users and might annoy a good slice of them. So, use it wisely!
### Mind the initial and final state of your elements
All the Animate.css animations include a CSS property called `animation-fill-mode`, which controls the states of an element before and after animation. You can read more about it [here](https://developer.mozilla.org/en-US/docs/Web/CSS/animation-fill-mode). Animate.css defaults to `animation-fill-mode: both`, but you can change it to suit your needs.
### Don't disable the `prefers-reduced-motion` media query
Since version 3.7.0 Animate.css supports the `prefers-reduced-motion` media query which disables animations based on the OS system's preference on supporting browsers (most current browsers support it). This is a **critical accessibility feature** and should never be disabled! This is built into browsers to help people with vestibular and seizure disorders. You can read more about it [here](https://css-tricks.com/revisiting-prefers-reduced-motion-the-reduced-motion-media-query/). If your web-thing needs the animations to function, warn users, but don't disable the feature. You can do it easily with CSS only. Here's a simple example:
Even though some browsers can animate inline elements, this goes against the CSS animation specs and will break on some browsers or eventually cease to work. Always animate block or inline-block level elements (grid and flex containers and children are block-level elements too). You can set an element to `display: inline-block` when animating an inline-level element.
### Overflow
Most of the Animate.css animations will move elements across the screen and might create scrollbars on your web-thing. This is manageable using the `overflow: hidden` property. There's no recipe to when and where to use it, but the basic idea is to use it in the parent holding the animated element. It's up to you to figure out when and how to use it, [this guide](https://developer.mozilla.org/en-US/docs/Web/CSS/overflow) can help you understand it.
### Intervals between repeats
Unfortunately, this isn't possible with pure CSS right now. You have to use Javascript to achieve this result.
If you had a hard time understanding the previous function, have a look at [const](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/const), [classList](https://developer.mozilla.org/en-US/docs/Web/API/Element/classList), [arrow functions](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/Arrow_functions), and [Promises](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise).
Animate.css v4 brought some improvements, improved animations, and new animations, which makes it worth upgrading. However, it also comes with a breaking change: we have added a prefix for all of the Animate.css classes - defaulting to `animate__` - so a direct migration is impossible.
But fear not! Although the default build, `animate.min.css`, brings the `animate__` prefix we also provide the `animate.compat.css` file which brings no prefix at all, like the previous versions (3.x and under).
If you're using a bundler, update your import:
from:
```js
import 'animate.min.css';
```
to
```js
import 'animate.compat.css';
```
Notice that depending on your project's configuration, this might change a bit.
In case of using a CDN, update the link in your HTML:
In the case of a new project, it's highly recommended to use the default prefixed version as it'll make sure that you'll hardly have classes conflicting with your project. Besides, in later versions, we might decide to discontinue the `animate.compat.css` file.
<pclass="warning">Custom builds are not possible from a node_modules folder as we don't ship the building tools in the npm module.</p>
Animate.css is powered by npm, postcss + postcss-preset-env, which means you can create custom builds pretty easily, using future CSS with proper fallbacks.
First of all, you’ll need Node and all other dependencies:
Next, run `npm start` to compile your custom build. Three files will be generated:
- `animate.css`: raw build, easy to read and without any optimization
- `animate.min.css`: minified build ready for production
- `animate.compat.css`: minified build ready for production **without class prefix**. This should only be used as an easy path for migrations.
For example, if you'll only use some of the “attention seekers” animations, simply edit the `./source/animate.css` file, delete every `@import`, and add the ones you want to use.
```css
@import 'attention_seekers/bounce.css';
@import 'attention_seekers/flash.css';
@import 'attention_seekers/pulse.css';
@import 'attention_seekers/rubberBand.css';
@import 'attention_seekers/shake.css';
@import 'attention_seekers/headShake.css';
@import 'attention_seekers/swing.css';
@import 'attention_seekers/tada.css';
@import 'attention_seekers/wobble.css';
@import 'attention_seekers/jello.css';
@import 'attention_seekers/heartBeat.css';
```
Now, just run `npm start` and your highly optimized build will be generated at the root of the project.
### Changing the default prefix
It's pretty straight forward to change animate's prefix on your custom build. Change the `animateConfig`'s `prefix` property in the `package.json` file and rebuild the library with `npm start`:
Animate.css supports the [`prefers-reduced-motion` media query](https://webkit.org/blog/7551/responsive-design-for-motion/) so that users with motion sensitivity can opt out of animations. On supported platforms (currently all the major browsers and OS, including mobile), users can select "reduce motion" on their operating system preferences, and it will turn off CSS transitions for them without any further work required.
Animate.css is licensed under the [Hippocratic License](http://firstdonoharm.dev).
### Contributing
Pull requests are the way to go here. We only have two rules for submitting a pull request: match the naming convention (camelCase, categorized [fades, bounces, etc.]) and let us see a demo of submitted animations in a [pen](https://codepen.io). That **last one is important**.
### Code of Conduct
This project and everyone participating in it is governed by the [Contributor Covenant Code of Conduct](https://github.com/animate-css/animate.css/blob/main/CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to [animate@eltonmesquita.com](mailto:animate@eltonmesquita.com).
<metaname="title"content="Animate.css | A cross-browser library of CSS animations.">
<metaname="description"content="Animate.css is a library of ready-to-use, cross-browser animations for you to use in your projects. Great for emphasis, home pages, sliders, and attention-guiding hints.">
<metaproperty="og:title"content="Animate.css | A cross-browser library of CSS animations.">
<metaproperty="og:description"content="Animate.css is a library of ready-to-use, cross-browser animations for you to use in your projects. Great for emphasis, home pages, sliders, and attention-guiding hints.">
<metaproperty="twitter:title"content="Animate.css | A cross-browser library of CSS animations.">
<metaproperty="twitter:description"content="Animate.css is a library of ready-to-use, cross-browser animations for you to use in your projects. Great for emphasis, home pages, sliders, and attention-guiding hints.">
Animate.css is a Hippocratic-2.1 licensed library.
You can use it freely, respecting the terms included in the <ahref="https://github.com/animate-css/animate.css/blob/main/LICENSE"title="license">license file.</a>
</p>
</footer>
<asideclass="motionless__banner">
<pclass="motionless__paragraph">
<b>Hey!</b> It seems that you have animations disabled on your OS, turning Animate.css
off.<br/>
Animate.css supports the
<a
title="prefers-reduced-motion CSS media feature on MDN"