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

@lu-development/ux-style-guide

v0.0.3

Published

Liberty University Style Guide

Downloads

2

Readme

Liberty University: Style Guide

If you are seeing this on NPM... you can use this component library in any framework or the "no framework" of your choice. See getting started with components below.

If you are trying to develop the style guide. Note that though the component library is public the style guide is still a private repository.

Getting Started Developing the Style Guide

To start working on the style guide(and if you have access to repo), clone this repo to a new directory:

git clone [email protected]:lu-dev/ux-style-guide.git
cd ux-style-guide

and run:

npm install
npm start

To build the app for production, run:

npm run build

To run the unit tests once, run:

npm test

To run the unit tests and watch for file changes during development, run:

npm run test.watch

To publish the repo. Make sure the project version is incremented properly according to Semantic Versioning. Of course you need to be logged into you npm account and have publishing auth. If you need access create an npm account if you don't have one and email [email protected] with you request.

npm publish --access=public    

Getting Started With Components

######Script tag

Put this script tag with the version

<script src='https://unpkg.com/@lu-development/ux-style-guide@<version you want>/dist/uxstyleguide.js'></script>

in the head of your index.html Then you can use the element anywhere in your template, JSX, html etc.

######Node Modules

Run

npm install @lu-development/ux-style-guide --save

Put a script tag similar to this

<script src='node_modules/@lu-development/ux-style-guide/dist/uxstyleguide.js'></script>

in the head of your index.html Then you can use the element anywhere in your template, JSX, html etc.

######In a stencil-app-starter app

Run

npm install @lu-development/ux-style-guide --save

Add an import to the npm packages: import @lu-development/ux-style-guide; Then you can use the element anywhere in your template, JSX, html etc.

######Framework Integration Reference: https://stenciljs.com/docs/framework-integration

In my experience so far(because stencil still has not created the common js index.js magic at this point) you need to specify the /dist/esm/index.js when importing the defineCustomElements function.

Also the angular import does not work at his point but you can import with the script tag and still add the CustomElementSchema to the AppModule... it works just fine.