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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@myuw-web-components/myuw-help-link

v1.1.0

Published

Stylized hyperlink to help content.

Downloads

3

Vulnerabilities

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

Links

Git

Maintainers

benjaminsousabenjaminsousalstelslstelsnogalpaulinanogalpaulinamyuw-web-components-jenkinsmyuw-web-components-jenkinsjordanalanjonesjordanalanjoneszeke.witterzeke.witterapetroapetroscott.bergscott.berg

Keywords

Readme

myuw-help-link

This Web Component presents a stylized link to help.

Using

To use the myuw-help-link web component,

  1. Make it available in the HTML page by invoking suitable <script>, and
  2. Use it via the <myuw-help-link> element.

Import the web component

In MyUW

MyUW provides a local CDN-like (Content Delivery Network-like) affordance.

Rely upon the latest v1-compatible release

<script
  type="module"
  src="/static/web-components/myuw/myuw-help-link/1-x/myuw-help-link.min.mjs"></script>
<script
  nomodule
  src="/static/web-components/myuw/myuw-help-link/1-x/myuw-help-link.min.js"></script>

(See documentation about myuw-help-link in static for more conservative options.)

Using unpkg

In HTML <head>,

<script type="module" src="https://unpkg.com/@myuw-web-components/myuw-help-link@^1?module"></script>
<script nomodule src="https://unpkg.com/@myuw-web-components/myuw-help-link@^1"></script>

to import via unpkg.

WARNING: unpkg is a third-party service neither provided nor endorsed by MyUW. In a MyUW context, sourcing from /static is preferred.

Redistribute with the downstream app

Alternatively include the web component files locally in the application and import from there.

Invoke the Web Component

Use the component's in the HTML page:

<myuw-help-link
  app-context="Payroll"
  url="https://uwservice.wisc.edu/help/payroll">
</myuw-help-link>

app-context attribute

The app-context attribute clarifies the scope and context of the help linked.

Implementation detail: myuw-help-link uses it to compose the link label, as {app-context} resources and help. (This is an implementation detail, not a guarantee of the API exposed by myuw-help-link).

url

The url attribute tells the web component where the link should take the user.

Absolute links (starting with http) open in a new tab (via target='_blank' with the page-jacking-prevention workaround of rel='noopener noreferrer').

Developing

Practice Semantic Versioning

Carefully practicing Semantic Versioning allows downstream applications making use of myuw-help-link to automatically, transparently upgrade to the latest compatible version of the component.

If a change is not backwards-compatible, it MUST yield a MAJOR version number bump, e.g. from 1.1.12 to 2.0.0.

Keep a changelog

Update CHANGELOG.md to document the changes. This is useful documentation, and it's also a prompt to think about the nature of the changes and to ensure that they are backwards-compatible.

Locally testing

npm install
npm start

Visit http://127.0.0.1:8080/docs/ .

Releasing aka Publishing

First, update package.json to reflect the version number you intend to release.

Then

npm publish --public

and capture the /dist/ outputs to myuw-shared-static.

Oh no that release wasn't backwards-compatible

Immediately release a new PATCH version that restores compatibility.