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

@duetds/components

v8.4.0

Published

This package includes Duet Design System Web Components and related utilities.

Downloads

15,301

Readme

Build Status Version

Duet Components

This package includes Duet Web Components and related tools.

Usage

For usage instructions, please see Duet Design System documentation.

Architecture

This package is built with Stencil.js, a compiler and toolchain for building web components. The component source code is written in TypeScript + JSX (TSX), with stylesheets written in SCSS.

Development

The following are the most commonly used commands during development:

  • npm start - Compile components, start watching for changes, start local development server
  • npm test - Compile components, start watching for changes, start local development server and run tests.

The local development server started by npm start or npm test serves a files located at /src/prototypes/. Any local changes or new components are available on this page, so this can be used as a testing ground when developing.

On that page you can also press ctrl + p to choose any of the component fixtures to work on.

How to develop new components

  1. Create component files
    1. add directory for component under src/components/[component-name]
    2. add [component-name].tsx
    3. add [component-name].scss
    4. add [component-name].e2e.ts
    5. add readme.md
  2. Implement component
  3. Write tests
  4. Write readme
    1. add info for docs
    2. add comprehensive examples
  5. Test theming for both default and turva
  6. Browser testing
  7. Accessibility testing, following the Duet accessibility checklist
  8. Test SSR
  9. Add the following to docs/:
    1. An SVG icon for listing on component page
    2. Add to changelog.md

Documentation and examples

  • Documentation that is shown on duetds.com acts as our primary component development platform. To get started locally, open /docs/ directory and run npm install and npm start.
  • Once the server is up and running, you can access the local development environment by pointing your browser to http://localhost:8000. The components section in the documentation will be empty at this point.
  • Next, go to /packages/components/ directory and run npm install and npm start that starts up the component watch and build tasks.
  • If you now open any of the *.tsx, *.scss, or readme.md files underneath /packages/components/src/components/ and hit save, that will trigger a rebuild task which also copies the necessary changes over to the local documentation running at http://localhost:8000.
  • Editing *.tsx and *.scss files will generate a new JavaScript bundle, while editing the readme.md files only generates and copies over the documentation and component usage examples.
  • When working on new components or editing existing ones, make sure to follow our code style guide found under the guidelines section.
  • Component variation examples are inside each component’s readme.md, while the component templates are located under /docs/src/templates/ directory.

Copyright

Copyright © 2023 LocalTapiola/Turva.