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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@adaptive-web/adaptive-web-components

v0.8.1

Published

Standards based, framework agnostic web components built using FAST.

Downloads

333

Readme

Adaptive Web Components

Note this is an alpha release. The components are functional and performant and safe to use. They are however based on the beta release of FAST Element.

While we are committed to following semver for this project, it's important to note that while we move through alpha and beta, minor version numbers can and will likely include breaking changes until we hit 1.0.0. After 1.0.0, we will be aligned with semver2.0.

We currently recommend consuming them with as few adjustments as possible because many common issues will be made much easier, including building your own customized design system.

Please see the Next Steps for upcoming work.

What

This project is based on FAST and implements the first comprehensive web component library built as Web Components for enterprise web software utilizing the power of Adaptive User Interfaces.

Why

Stop reinventing the wheel, and cut your engineering costs by up to 75%! Simply consume these Web Components, configure your own brand and design system, and start building immediately.

  • Optimized for performance
  • Optimized for scale
  • Optimized for accessibility
  • Build on the latest Open Web Standards
  • Build on architectural best practices
  • Build on framework-less TypeScript foundation
  • Built for Design-to-Code principles

How

Add the components:

npm install "@adaptive-web/adaptive-web-components"

Import and use everything:

import { AdaptiveDesignSystem } "@adaptive-web/adaptive-web-components";
import { AllComponents } from "@adaptive-web/adaptive-web-components/all-components";
AdaptiveDesignSystem.defineComponents(AllComponents);

Import via CDN link on a script tag:

<!DOCTYPE html>
<html lang="en">
    <head>
        <script type="module" src="https://cdn.jsdelivr.net/npm/@adaptive-web/adaptive-web-components/dist/adaptive-web-components.min.js"></script>
    </head>
    <!-- ... -->
</html>

Author html with imported components:

<adaptive-button>Click Me</adaptive-button>

See the examples for more details.

Next Steps

  • Component styling will evolve with the capabilities of Adaptive UI. Default component styles are currently split between templateStyles and aestheticStyles. The aesthetic styles will migrate to a modular styling approach that will be configurable using the Design Tokens Community Group working format standards.
  • Universal support for an appearance attribute on all components, allowing for extreme flexibility in creating and styling the variations you need.
  • Evolving the component definition model for enhanced customization.