npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@wavelo/angular

v0.5.0

Published

An Angular standalone component for CSS loading spinners, skeletons and progress, library-compiled so AOT builds accept it

Readme

@wavelo/angular

Angular component for Wavelo, for Angular 14 and up (standalone components and inject(); the package is compiled with ngc in partial mode, so an AOT application can import it). Import LoaderComponent into a standalone component and drive it with inputs.

import { Component } from '@angular/core';
import { LoaderComponent } from '@wavelo/angular';

@Component({
  standalone: true,
  imports: [LoaderComponent],
  template: '<wavelo-loader type="three-dots" label="Loading data" [size]="48" />'
})
export class Screen {}

Inputs cover all 28 configuration keys. Two names need care: style binds as waveloStyle, because Angular already owns [style], and data-* attributes on the host are read into the configuration. paused, loading, inline and decorative take a boolean binding, and a bare attribute (paused, loading) is true the way HTML means it.

Defaults for a whole tree are a provider, not a global:

providers: [{ provide: WAVELO_DEFAULTS, useValue: { color: '#6366f1', size: 32 } }]
<wavelo-loader type="ring" [loading]="busy" [count]="3" inline />

[loading]="false" renders no markup and injects no stylesheet; the host element (display: contents) stays empty.

The host element is display: contents, change detection is OnPush, and the rendered content is cleared on destroy. Only markup is written into the host; ensureStyles puts the design's stylesheet slice in the document head, so a server-rendered page should add @wavelo/core/styles.css to the server styles.

Supported peer range: @angular/core >=14.0.0.

Interactive documentation & live preview gallery: https://princegoel0.github.io/wavelo/

See docs/FRAMEWORKS.md and docs/COMPATIBILITY.md.