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

@dotsha/web-components

v0.70.1

Published

Ready to deploy web components for Dotsha resources.

Downloads

20

Readme

Dotsha Web Components

Ready to deploy web components for Dotsha resources.

Installation

Using npm

npm install @dotsha/web-components

Using yarn

yarn add @dotsha/web-components

unpkg

https://unpkg.com/@dotsha/web-components/dist/dotsha-components.js

Usage

HTML

<script type="module" src='https://js.dotsha.com/v0/dotsha-components.js' async></script>

<!-- Available components -->
<dotsha-contact-summary></dotsha-contact-summary>
<dotsha-credit-note-table></dotsha-credit-note-table>
<dotsha-invoice-table></dotsha-invoice-table>
<dotsha-offer-summary-list></<dotsha-offer-summary-list>
<dotsha-subscription-table></<dotsha-subscription-table>
<dotsha-subscription-summary-list></<dotsha-subscription-summary-list>
<dotsha-quote-list></dotsha-quote-list>

<dotsha-offers-to-quote></<dotsha-offers-to-quote>
<dotsha-offers-to-subscription></<dotsha-offers-to-subscription>

<!-- Parameters example -->
<dotsha-offers-to-subscription
  api-url='https://api.dotsha.com/'
  client-id='XXX'
  client-secret='XXX'
  currency-code='EUR'
  label='Select this'
  offer-ids='638f13b55cc034628023f681,63f645eadf8c8ba5a1bffbab'
></<dotsha-offers-to-subscription>

Contribute

Before contributing, please read the Contributing Guide.

Quick Start

This project is a web components collection, built with Lit.

Run:

yarn install --frozen-lockfile

yarn start

Setup environment

You will need to install Node.js 16.17.0 with npm@7and yarn@1


Login

Retrieving token

Web components will need a valid token to call the Dotsha API.

Using Postman

  1. Go to the active environment (ex: DEV) and retrieve the access_token for self portal credentials: you now have a token with a userId linked to it

Using the browser developper tools

You can start the self-portal to grab an access_token from there, either after login or with each call.


Linting and formatting

To scan the project for linting and formatting errors, run

yarn lint

Testing with Web Test Runner

To execute a single test run:

yarn test

Demoing with Storybook

To run a local instance of Storybook for your component, run

yarn storybook

To build a production version of Storybook, run

yarn storybook:build

Demoing locally with web-dev-server

yarn start

To run a local development server that serves the basic demo located in demo/index.html.
Take care of hot reloading, sometimes it does not trigger after saving a change.