Loader
<auro-loader>
is a HTML custom element for the purpose of illustrating animated loaders.
Things take time. Sometimes we just need to take a second for some data to show up. For this Auro supports the <auro-loader>
custom element. This powerful element supports multiple modes for use, ringworm
, orbit
, pulse
, and laser
.
And each of these modes support five size settings, default
, sm
, md
, lg
, and xl
.
For color support <auro-loader>
supports currentColor
, this allows for any color set on the parent element to influence the color of the loader.
The <auro-loader>
custom element also supports three pre-defined color modes, onlight
, ondark
and white
.
UI development browser support
For the most up to date information on UI development browser support
Install
$ npm i @aurodesignsystem/auro-loader
Installing as a direct, dev or peer dependency is up to the user installing the package. If you are unsure as to what type of dependency you should use, consider reading this stack overflow answer.
Design Token CSS Custom Property dependency
The use of any Auro custom element has a dependency on the Auro Design Tokens.
CSS Custom Property fallbacks
CSS custom properties are not supported in older browsers. For this, fallback properties are pre-generated and included with the npm.
Any update to the Auro Design Tokens will be immediately reflected with browsers that support CSS custom properties, legacy browsers will require updated components with pre-generated fallback properties.
Define dependency in project component
Defining the component dependency within each component that is using the <auro-loader>
component.
import "@aurodesignsystem/auro-loader";
Reference component in HTML
foo
Install bundled assets from CDN
In cases where the project is not able to process JS assets, there are pre-processed assets available for use. See -- auro-loader__bundled.js
for modern browsers. Legacy browsers such as IE11 are no longer supported.
We recommend you load these bundles using differential serving so that the browser only loads the bundle correctly. To accomplish this, the script tag for the modern bundle should have type="module"
and the script tag.
Bundle example code
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@alaskaairux/design-tokens@latest/dist/tokens/CSSCustomProperties.css" />
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@aurodesignsystem/webcorestylesheets@latest/dist/bundled/essentials.css" />
<script src="https://cdn.jsdelivr.net/npm/@aurodesignsystem/auro-loader@latest/dist/auro-loader__bundled.js" type="module"></script>
auro-loader use cases
The <auro-loader>
element should be used in situations where developers may need to illustrate a wait time for their users.
API Code Examples
Default auro-loader
foo
Development
In order to develop against this project, if you are not part of the core team, you will be required to fork the project prior to submitting a pull request.
Please be sure to review the contribution guidelines for this project. Please make sure to pay special attention to the conventional commits section of the document.
Start development environment
Once the project has been cloned to your local resource and you have installed all the dependencies you will need to open a shell session to run the dev server.
$ npm run dev
Open localhost:8000
If running separate sessions is preferred, please run the following commands in individual terminal shells.
$ npm run build:watch
$ npm run serve
API generation
The custom element API file is generated in the build and committed back to the repo with a version change. If the API doc has changed without a version change, author's are to run npm run build:api
to generate the doc and commit to version control.
Testing
Automated tests are required for every Auro component. See .\test\auro-loader.test.js
for the tests for this component. Run npm test
to run the tests and check code coverage. Tests must pass and meet a certain coverage threshold to commit. See the testing documentation for more details.
Bundled assets
Bundled assets are only generated in the remote and not merged back to this repo. To review and/or test a bundled asset locally, run $ npm run bundler
to generate assets.