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

@aqua-ds/web-components

v0.0.8

Published

AquaDS Web Components

Downloads

19

Readme

AquaDS WebComponents

version lastUpdated

AquaDs

Design together. Build together. Speak the same language.

npm i @aqua-ds/web-components


Use the components directly in HTML without any framework by installing the Aqua Web Components package.

Installation

Aqua DS Web Components can be installed in two different ways depending on your project’s needs:

Using NPM

For projects using Node.js with a build system (like Vite, Webpack, etc.):

  1. Make sure your project is initialized and supports modern JavaScript.
  2. Install Aqua DS Web Components:
npm i @aqua-ds/web-components
  1. Import and define the components in your JavaScript entry point:

    When use defineCustomElements you will subscribe all the web-components on the website. That will enable the possibility of access to any web-component at any moment. That not affects the app performance.

import { defineCustomElements } from '@aqua-ds/web-components/loader';
defineCustomElements();

Using CDN

For simpler setups (e.g., pure HTML without a build step):

  1. Include the Aqua DS script in your HTML:
<script type="module" src=[url-to-cdn]></script>

If you need access to the URL AQUA CDN to connect to Aqua’s private cdn, please send an email to the FrontOps team [email protected]

Note: CDN is ideal for prototyping or static environments.

Using Components

Aqua DS offers a wide range of Web Components that can be used across compatible environments. Each component comes with defined props, slots, and events to provide flexible UI behavior.

Here’s how you can use components from the official list:

Components

Example: <aq-button>

<aq-button variant="primary" type="submit">
  <em class="aq-icon-settings"></em>Submit
</aq-button>

Handling Events

Aqua DS components emit custom events to allow interaction and dynamic behavior in your applications. When using Web Components directly (e.g., in HTML or JavaScript), you can listen to these events using standard DOM event listeners.

<aq-button variant="primary" type="submit" id="aqButton">
  <em class="aq-icon-settings"></em>Submit
</aq-button>

<script>
	const aqButton = document.getElementById("aqButton");
	
	aqButton.addEventListener('click', (event)=> {
		console.log("Click from AqButton: ", event.detail);
	});
</script>

Each Aqua DS component defines its own set of custom events to support interactive and reactive behavior. These events are designed to reflect meaningful user interactions or internal state changes.

Always refer to the documentation of each individual component for a complete list of supported events, their purpose, and usage examples.

Using the correct event names and handlers ensures proper integration within your app logic and facilitates a seamless user experience.

Passing Properties to Web Components

In Aqua DS, you can pass properties (also known as "props" or "attributes") directly to Web Components via HTML attributes or JavaScript.

These properties control the component’s behavior, appearance, and logic. Each component has its own set of supported props, which you can find in its documentation.

HTML Example

<aq-text-field
	id="aqTextField"  
	type="number"
	placeholder="This has slot with left content" 
	icon="aq-icon-settings" 
	label="This is a label" 
	sublabel="Sub"
  helper-text="This is a helper text"
  info="This is a tooltip"
  char-counter
	is-required
	is-textarea>
</aq-text-field>

Javascript Example

const aqTextField = document.getElementById("aqTextField");
aqTextField.icon = "aq-icon-email";
aqTextField.label = "TextField Label"
  • Boolean props (like is-disabled or is-required) can be added without a value in HTML.

Complex data types as property

In WebComponents some props only works when are manually set via Javascript, depending on the component’s internal logic.

<aq-button-split
    id="aqButtonSplit"
    type="button"
    variant="default"
    size="medium"
    info="This is a tooltip" >
    <em class="aq-icon-send-money"></em> Button
</aq-button-split>
<script>
  const buttonSplit = document.querySelector('#aqButtonSplit');
  
  // Setting a JS-only attribute (complex object)
  buttonSplit.items = [
    { id: "1", name: "Option 1" },
    { id: "2", name: "Option 2" },
    { id: "3", name: "Option 3" }
  ];
</script>

Always check the official documentation of each component to understand which props are available and how they behave

Design together. Build together. Speak the same language.