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

junction-assets

v3.3.0

Published

Junction Assets is the home to Insight's shared components and style declarations

Readme

Junction Assets

Junction Assets is the home to Insight's shared components and style declarations

Contributing to Junction Assets

  1. Make necessary changes to projects/junction-assets/...
  • For style based changes, modify src/assets/scss/...
  • For component based changes (i.e. changes to header/footer), modify src/lib/...
  1. Push your changes to the insight/junction-assets project

Testing Junction Assets

Junction Assets cannot be run as a standalone application. It must be tied to a pre-existing Insight application. When you are done with your changes, you can test them in a pre-existing application as follows:

  1. Ensure all the changes you've made are complete
  2. Build the /dist folder using npm run build
  3. Copy the junction-assets folder inside the generated /dist folder from step 2
  4. Replace the @insight/junction-assets with the junction-assets folder you copied from step 3 into a pre-existing Insight application
  5. Run the Insight application using ng serve --base-href /URL/ if necessary

Common Errors

My changes are not displaying after I copy junction-assets into an Insight application

  • Make sure you are replacing @insight/junction-assets with dist/junction-assets built from npm run build
  • Make sure you are modifying project/junction-assets/... and not src/...

Running npm run build fails causes a lot of errors

  • Ensure that you have all the required packages by running npm install before running npm run build
  • If you require additional packages, install them using npm install --save

After copying junction-assets, I get errors where @insight/junction-assets/... cannot be found

  • Make sure that you are replacing @insight/junction-assets with dist/junction-assets
    • Do not use the base junction-assets (i.e. the entire project)