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

@mmg-dev/webpipeline-gbw-shared-vars

v1.5.1

Published

This package contains common CSS variables used by the Webpipeline team.

Readme

Introduction

This package contains common CSS variables used by the Webpipeline team.

Publish to npm

  1. Commit
  2. Update the version with npm version patch|minor|major
  3. Push changes
  4. Publish with npm publish --access public

Installation

pnpm i @mmg-dev/webpipeline-gbw-shared-vars

Regular (Stencil):

@import '~@mmg-dev/webpipeline-gbw-shared-vars';

Vite:

@import '@mmg-dev/webpipeline-gbw-shared-vars';

Stencil:

import { options } from '@mmg-dev/webpipeline-gbw-shared-vars';
console.log(options.res.lg);

Media-Queries: (md = 768px)

@include breakpoint(md) { // min:md ~ max:lg
@include breakpoint-down(md) {
@include breakpoint-up(md) {

Media-Queries v2 (2026, reduced breakpoints)

Migrating from v1? See the full Breakpoint V2 Migration Guide.

Breakpoints:

  • s: 0 - 767px
  • m: 768 - 1439px
  • l: >= 1440px
@include breakpoint-v2(s) { // max: 767px
@include breakpoint-v2(m) { // min: 768px ~ max: 1439px
@include breakpoint-v2(l) { // min: 1440px

@include breakpoint-up-v2(m) { // min: 768px
@include breakpoint-down-v2(m) { // max: 1439px

Optional wrapper for step-by-step migration

Use a wrapper class (default: .gbw-bp-v2) so new components can be enabled only inside specific areas.

.my-component {
  @include breakpoint-v2-scope {
    // base styles
    @include breakpoint-up-v2(m) {
      // styles for >= 768px
    }
  }
}

Root-level alternative:

@include breakpoint-v2-wrap {
  .my-component {
    // styles here
  }
}

You can change or disable the wrapper by overriding $bpV2Scope before importing this package:

$bpV2Scope: null; // disables the wrapper

SCSS Vars:

$bpSm: 375px;
$bpMd: 768;
$bpLg: 1024;
$bpXl: 1280;
$bpXxl: 1440;
$bpXxxl: 1920;
$bpSmDownPx:  374px
$bpMdDownPx: 767px
$bpLgDownPx:  1023px
$bpXlDownPx:  1279px
$bpXxlDownPx:  1439px
$bpXxxlDownPx:  1919px

SCSS Vars v2

$bpV2M: 768;
$bpV2L: 1440;
$bpV2Scope: '.gbw-bp-v2';

$bpV2MDownPx: 767px
$bpV2LDownPx: 1439px