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

@globus/globus-css

v3.0.0

Published

Utility-centric CSS and styled components to give you the building blocks for any Globus web project.

Vulnerabilities

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

Links

Maintainers

teresagteresagjbottiglierojbottigliero

Keywords

Readme

globus-css

Utility-centric CSS and styled components to give you the building blocks for any Globus web project.

  • Storybook – updated and deployed on merges to main.

Principles + Guidelines

  • Based on [email protected]
    • SCSS (variable) overrides and theming should be used in favor of overriding selectors.
  • Consumable as CSS
    • We should work toward consumption via Sass using the SCSS files directly to allow more control over end-usage bundle size.
    • The versioned CSS assets can/should be centrally hosted (CDN).
  • Consumable as an NPM package
  • Follow Semantic Versioning
    • With the project being consumed via NPM package, by many implementations, we should ensure changes are applied in an expected way.
  • Accessible via Storybook
    • This repository will essentially be a code-consumable version of globusonline/globus-webapp, limited to base utilities, objects, and components. There should be a place to easily reference and explore the contents.
    • Documentation in the Storybook can provide guidance on implementation requirements around common usage and accessibility.

Developing (Storybook)

This project contains a Storybook of available UI components. It is intended to be both an area to develop UI components in isolation and used as a documentation resource for consumers (when published).

To start Storybook, run: npm run storybook

Usage

As of v0.5.0 the dist folder only contains the most recently tagged release's built files.

The package is available on npm - npm i @globus/globus-css

As of v0.5.0, bundled assets can be referenced using unpkg.com or JSDelivr.

<link rel="stylesheet" href="https://unpkg.com/@globus/globus-css/dist/globus-css.css" crossorigin="anonymous">

<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@globus/globus-css/dist/globus-css.css" crossorigin="anonymous">

NOTE: Asset paths (ie. fonts, icons) in generated CSS files are currently relative – you will need to make sure these assets are locally available in your application.

Releasing

npm run release will bump the package using Conventional Commits (via standard-version) and update the dist folder.