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 🙏

© 2026 – Pkg Stats / Ryan Hefner

tamu-library-components

v2.0.9

Published

[![Build Status](https://github.com/TAMULib/tamu-library-components/workflows/Build/badge.svg)](https://github.com/TAMULib/tamu-library-components/actions?query=workflow%3ABuild) [![Coverage Status](https://coveralls.io/repos/github/TAMULib/tamu-library-c

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

jamess-tamujamess-tamu

Keywords

Readme

Build Status Coverage Status Compodoc Coverage Performance Accessibility Best Practices SEO Progressive Web App

TAMU Library Components

Copyright © 2020-2025 Texas A&M University Libraries under the MIT license.

TAMU Library Components is an extension both on top of and perpendicular to Weaver Components. This either extends components, providing custom styles, or provides entirely new components.

Installation

TAMU Library Components may be installed by either referencing a CDN or by using NpmJs.

Installation via NpmJs

The latest pre-built package may be found in the TAMU Library Elements NpmJs Repository.

Using the npm command (from NpmJs), install this project as a dependency to an existing project:

npm install @wvr/tl-elements

Installation via CDN

The files tl-components.js and styles.css need to be available on some server. See the Building section below for details on how to build these files.

The CSS file should be added as an HTML <link> element to the HTML <header> element, such as:

<html>
  <head>
    <link rel="stylesheet" type="text/css" href="https://localhost/styles.css">
  </head>
</html>

The Javascript file should be added an HTML <script> element to the HTML <bottom> element at the very end, such as:

<html>
  <body>
    ...
    <script src="https://localhost/tl-components.js"></script>
  </body>
</html>

Building

To build this project use the npm command (from NpmJs).

This project can be built to run locally for development purposes be built to get the tl-components.js and styles.css files needed to run on a CDN. More detailed documentation about the build process may be found via the referenced links in the Documentation section below.

Building the tl-components.js and the styles.css

The tl-components.js and the styles.css files are needed if intending to utilize this project via a CDN.

These files are built using the build command from within the project root directory:

  cd tamu-library-components
  npm run build

Once this has successfully completed the tl-components.js and styles.css files should be located under the dist/bundle/ sub-directory:

  dist/bundle/styles.css
  dist/bundle/tl-components.js

Building for a NpmJs Package

Building this for a NpmJs Package is the same as building this for a CDN.

These files are built using the build command from within the project root directory:

  cd tamu-library-components
  npm run build

Building against a Local Weaver Components

When wanting to run against a locally built Weaver Components, the Verdaccio service in Weaver Components should be used. Follow the Weaver Components documentation to set this up.

Once Weaver Components is properly set up, the npm-local command can be used to fetch only the local Weaver Components from the Verdaccio service. The npm install command will overwrite the local version which will result in loss of changes made by npm-local. Once Weaver Components is properly setup, the build and even start commands may be performed.

  npm install
  npm run npm-local
  npm run build
  npm run start

Documentation

Detailed documentation may be found:

Detailed reports may be found: