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

@casus-campus/cc-support

v0.21.0

Published

Angular library with components, services that are used throughout the CC ecosystem.

Readme

CcSupport

This project was generated with Angular CLI version 7.2.0 supported the instructions of this article.

Provided components and services

  • cc-dynamic-content-viewer (component): Renders hyperlinks in html content as dialog, tooltip, external link or collapsible.

Requirements

  • @angular/material
  • hammerjs

Installation

  1. Install npm install --save @casus-campus/cc-support

  2. Add to app.module.ts

  imports: [
    \\ ...
    CcSupportModule,
  ]
  1. Apply material theme
@use '@casus-campus/cc-support' as *;

@include cc-support-theme($theme);

Development

This repository contains two projects: the CC-Support library (@casus-campus/cc-support) and a test application (lib-tester). To see changes of the library files (projects/casus-campus/cc-support/src/lib) inside the test app (projects/lib-tester/src/app), you need to build the library with npm run build.

Development server

Run ng serve for a dev server for the lib-tester. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.

Build

Run npm run build to build the library. The build artifacts will be stored in the dist/ directory.

Running unit tests

Run ng test to execute the unit tests via Karma.

Further help

To get more help on the Angular CLI use ng help or go check out the Angular CLI README.

Publish library to NPM

Publishing the library is only needed, if the develop branch has some changes that are not already in the production branch. The latest production commit reflects the latest published version on NPM.

Semi-automated (preferred)

  • make sure that develop branch is checked out (git checkout develop)
  • make sure that the tests succeed (ng test @casus-campus/cc-support)
  • increase version in ./projects/casus-campus/cc-support/package.json (following SemVer)
  • commit and push changes
  • merge into production (git checkout production && git merge develop)
  • push changes (git push)

Manual

  • make sure that develop branch is checked out (git checkout develop)
  • make sure that the tests succeed (ng test @casus-campus/cc-support)
  • increase version in ./projects/casus-campus/cc-support/package.json (following SemVer)
  • commit changes
  • merge into production (git checkout production && git merge develop)
  • perform npm run pack
  • perform npm publish ./dist/casus-campus/cc-support/[tgz-file] (make sure to be login first via npm login)
  • push changes (git push) and tag (git push --tag origin production)