Skip to content

TAMULib/weaver-components

Folders and files

NameName
Last commit message
Last commit date

Latest commit

6f361c3 · Mar 20, 2025
Aug 30, 2022
Nov 12, 2021
Sep 23, 2022
Oct 9, 2020
Dec 9, 2024
Sep 26, 2022
Sep 28, 2022
Dec 1, 2020
Oct 16, 2020
Jan 10, 2020
Aug 30, 2022
Oct 16, 2020
Sep 26, 2022
Dec 9, 2024
Feb 14, 2020
Nov 10, 2022
Feb 13, 2025
Feb 13, 2025
Feb 14, 2020
Feb 13, 2020
Sep 28, 2022
Nov 12, 2020
Nov 12, 2020
Nov 12, 2020
Nov 12, 2020
Nov 12, 2020
Jan 29, 2021
May 11, 2021
Dec 9, 2024
May 19, 2021
Sep 2, 2021
Jul 31, 2020
May 19, 2021
Aug 30, 2022
Sep 23, 2022

Repository files navigation

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

Weaver Components

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

Weaver Components provides a collection of custom HTML elements that represent a toolkit of dynamically renderred HTML markup, CSS Styles, and effects. This toolkit may be made available to a given project either via a CDN URL, directly attached as a Javascript file and CSS file, or via a project dependency. Such elements may be dropped directly onto a page utilizing Weaver Components and they will be immediately renderred as appropriate.

Installation

Weaver 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 Weaver Elements NpmJs Repository.

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

npm install @wvr/elements

Installation via CDN

The files weaver-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/weaver-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 weaver-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 weaver-components.js and the styles.css

The weaver-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 weaver-components
  npm run build

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

  dist/bundle/styles.css
  dist/bundle/weaver-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 weaver-components
  npm run build

Once notable difference is that for those who want to develop against changes to this project, the publish:npm-local can be used as well. This process requires starting a Verdaccio service, of which is provided by the start:npm-local command. For further details, visit the links referenced in the detailed documentation below.

Documentation

Detailed documentation may be found:

Detailed reports may be found: