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

@explorer-1/common

v2.0.0

Published

shared assets for all flavors of explorer-1

Downloads

290

Readme

@explorer-1/common

npm

What's included

This package includes compiled assets for Explorer-1 and assets shared with @explorer-1/vue.


@nasa-jpl/common/
├── dist/            <-- Compiled Assets
│ ├── css/
│ │ ├── explorer-1.min.css
│ │ └── font-face.css
│ ├
├── src/             <-- Source code, use by @explorer-1/vue
│ ├── fonts/
│ ├── images/
│ ├── js/
│ ├── public/
│ └── scss/
├── stylelint.config.js
├── tailwind.colors.ts
└── tailwind.config.ts

Getting Started

Install with npm or similar:

npm install --save @explorer-1/common

Include the assets in your project

Include all styles and scripts by adding the bundled CSS and JS to your project's HTML. You will need to retrieve the files from the installed package in node_modules/@explorer-1/common/dist/, place them somewhere in your project, and update the paths to point to the right location.

<!-- CSS -->
<link
  href="/path/to/explorer-1.min.css"
  rel="stylesheet"
/>

<!-- JavaScript -->
<script src="/path/to/explorer-1.min.js"></script>

The compiled CSS includes only the Tailwind CSS classes that are used by our team's products and in Explorer 1's documentation; other default Tailwind CSS classes are not available.

Fonts

The compiled CSS references fonts with the relative path of ../fonts/. You will need to add the fonts to your build process to ensure they are included in the relative path. An example of how to handle this is to write a Node script that copies the /dist/fonts/ folder to the correct path in your project.

your-project
├── css/
│   ├── explorer-1.min.css
├── fonts/
│   ├── archivo-narrow/
│   └── metropolis/
└── js/
    └── explorer-1.min.js

Preloading Fonts

If your project requires more control over font preloading, you can preload the font-face.css stylesheet in /dist/css/:

your-project
└── css/
    └── font-face.css

Then preload the CSS in your template followed by the necessary font files.

<!-- your-project.html -->
<link
  rel="preload"
  href="/path/to/font-face.css"
  as="style"
/>
<link
  rel="preload"
  href="/path/to/fonts/metropolis/Metropolis-Medium.woff2"
  as="font"
  type="font/woff2"
  crossorigin="true"
/>

Build your own component templates using our docs as a guide

Reference the Explorer 1 Storybook for HTML snippets you can use to create components and build your pages. Step-by-step instructions on how to copy HTML snippets can be found on the Getting Started Guide for Developers page.