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

@tjmonsi/kwark

v0.0.1

Published

Yet another lightweight web-component sugar-syntax library that enables developers to create small web-components faster

Downloads

4

Readme

kwark

Additional templating setups for web components. Compatible with UpdateElement of lit-element.

Table of Contents

  • Put your table of contents here

Installation

Put your installation instructions here

Usage

Put your usage here or how to run this system

Development Setup and Contributing

Simply follow the instructions to run above.

Before submitting any change, make sure to:

Why build additional templates?

Because LitElement's default templating setup uses shadowDOM. Because there is a lot of libraries already that does almost the same thing: creating a better developer experience in creating re-usable web components. This library hopes to make the footprint of the syntactic sugar really small so that what the developer has to do is to create interactive components with minimal footprint - meaning, the main logic of how the interaction should be would be the one taking up more bytes than the library itself.

I see similar code

There would be some similar code lifted from Polymer, LitElement and Element-Lite, which are the base inspiration of the code. What I am hoping for this library is to make it as small and as extensible as possible.