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

@coveops/component-label

v1.0.1

Published

This component can be used to append a DOM-friendly label to a component that is missing it.

Downloads

1

Readme

ComponentLabel

This component can be used to append a DOM-friendly label to a component that is missing it.

Disclaimer: This component was built by the community at large and is not an official Coveo JSUI Component. Use this component at your own risk.

Getting Started

  1. Install the component into your project.
npm i @coveops/component-label
  1. Use the Component or extend it

Typescript:

import { ComponentLabel, IComponentLabelOptions } from '@coveops/component-label';

Javascript

const ComponentLabel = require('@coveops/component-label').ComponentLabel;
  1. You can also expose the component alongside other components being built in your project.
export * from '@coveops/component-label'
  1. Or for quick testing, you can add the script from unpkg
<script src="https://unpkg.com/@coveops/component-label@latest/dist/index.min.js"></script>

Disclaimer: Unpkg should be used for testing but not for production.

  1. Include the component in your template as follows:

Place the component in your markup:

<div class="CoveoComponentLabel"></div>

Options

The following options can be configured:

| Option | Required | Type | Default | Notes | | --- | --- | --- | --- | --- | | content | No | string | label | Content of the label. | | contentType | No | string | text | Specifies the content type of the label. Valid values are header or text. | | labelType | No | string | empty string | Specifies the logic we will apply as to the visibility of the label. Valid values are pager or breadcrumb. If no value is provided, we will simply display the label. | | shouldBeLocalized | No | boolean | false | Specifies whether to translate the label's value. |

Extending

Extending the component can be done as follows:

import { ComponentLabel, IComponentLabelOptions } from "@coveops/component-label";

export interface IExtendedComponentLabelOptions extends IComponentLabelOptions {}

export class ExtendedComponentLabel extends ComponentLabel {}

Contribute

  1. Clone the project
  2. Copy .env.dist to .env and update the COVEO_ORG_ID and COVEO_TOKEN fields in the .env file to use your Coveo credentials and SERVER_PORT to configure the port of the sandbox - it will use 8080 by default.
  3. Build the code base: npm run build
  4. Serve the sandbox for live development npm run serve