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

xtra-web-components

v1.1.1

Published

The Preact Web Components used on the Xtra website

Downloads

291

Readme

Web Boilerplate

The boilerplate for the Xtra Preact Custom Elements.

Introduction

This project contains everything needed to build a working Custom Element with Preact & TypeScript.

Using a custom element on a website

As these elements are supposed to be used inside a normal HTML context, the person implementing these can follow these steps in order to get a running app.

Add the stylesheet & script tag at the top of the page with:

<link href="style.css" rel="stylesheet" />
<script src="xtra-web.js"></script>

Add a custom element with the required parameters from the list

Development

Software dependencies

It is important to note that a postinstall script will run after the installation process in order to install the pre-commit hook. If you (the developer) do not have this installed, it will try to install pre-commit using brew.

For windows devices, this can be installed using Conda. If a developer makes use of this, please be so kind to update the postinstall-local.sh script 😊.

Installation proces

  • Clone this repository
  • Run asdf install to get the right version of Node & npm
  • Run npm install to install the required dependencies
  • Run npm run dev to get a working example at localhost:1234

Testing and build the application

Testing the application

Test are run with Jest & Preact Testing Library, in order to run the tests you can use the following commands:

npm run test

npm run test:coverage

Building the application

In order to get a production ready build, you can run the following command:

npm run build

Publishing the application

In order to publish a new version on npm, run the following command:

npm run release -- --release-as <majore|minor|patch>

git push --follow-tags origin main

Contributing

Folder Structure

When creating a new Custom Element it is important to follow the following directory structure to ensure parity within the codebase:

Profile (Custom Element)
 ┣ Statistics (feature inside Profile)
 ┃ ┗ Overview (Page)
 ┃ ┃ ┣ hooks (hooks used for this page)
 ┃ ┃ ┣ Overview.module.css
 ┃ ┃ ┣ Overview.test.tsx
 ┃ ┃ ┗ index.tsx
 ┃ ┣ GraphQL (Generated GraphQL)
 ┃ ┃ ┣ Statistics.generated.ts
 ┃ ┃ ┗ Statistics.ts
 ┃ ┣ Statistics.module.css
 ┗ index.tsx

As these Custom Elements will also make use of common components, suchs as buttons, form elements, etc., these elements should be placed inside the common folder. In order to structure these, we make use of atomic design

Git Workflow

In order to contribute to this project, clone the project and create a new branch following this convention. When you're finished with your changes, you can create a PR.

Make sure to follow the styleguide provided with ESLint, Prettier and StyleLint!