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

@rlmcneary2/weko-render

v0.1.0-alpha1

Published

## Usage

Downloads

18

Readme

@rlmcneary2/weko-render

Usage

This package supports rendering for web components with the following features:

  • stores state information for the web component
  • a render cycle is started when state is changed

WekoRenderMixin

WekoRenderMixin is a mixin that extends a class implementing a custom component. The class must have a constructor and the constructor must call super.

👉 The weko-render package includes TypeScript type support.

import { WekoRenderMixin } from "https://esm.sh/@rlmcneary2/weko-render";

class MyWebComponent extends WekoRenderMixin(HTMLElement) {
  constructor() {
    super();
  }

  // class implementation
}

Weko attributes

none

Static HTML attributes

none

Runtime attributes

none

API

TODO: methods and properties

Properties

Installation

As part of an ES module

Use "esm.sh" and import this module into a source file where you need to use render.

import from "https://esm.sh/@rlmcneary2/weko-render";

As part of a bundle

If you are bundling your source code you may need to use a dynamic import to load the library like so:

async function main() {
  await import("https://esm.sh/@rlmcneary2/weko-render");
}

Using a script element

The script can also be loaded in an HTML file, typically as part of the <head> element.

<head>
  <script src="https://esm.sh/@rlmcneary2/weko-render" type="module"></script>
</head>

TypeScript support

To use Typescript during development you need to do three things.

  1. Install the package locally from npm under devDependencies: npm i -D @rlmcneary2/weko-render.
  2. Update the tsconfig.json file's compilerOptions.paths with the local installation of the package.
"paths": {
  "@rlmcneary2/weko-render": ["./node_modules/@rlmcneary2/weko-render/src/index"]
}
  1. Create a .d.ts file somewhere in a path processed by tsconfig.json that declares a module for the remote address.
// remote.d.ts

// Allow all module names starting with "https://". This will suppress TS errors.
declare module "https://*";

// Map the URL to all the exports from the locally installed package.
declare module "https://esm.sh/@rlmcneary2/weko-render" {
  export * from "@rlmcneary2/weko-render";
}