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

@sixsrc/brick-slider-tailwind

v1.0.12

Published

Tailwind plugin package with BrickSlider structural utilities.

Readme

@sixsrc/brick-slider-tailwind

Structural Tailwind package for BrickSlider.

It provides the structural slider classes without forcing a visual theme. In practice, the package handles the layout layer and leaves the final styling in the user's hands.

Installation

pnpm add @sixsrc/brick-slider @sixsrc/brick-slider-tailwind tailwindcss
npm install @sixsrc/brick-slider @sixsrc/brick-slider-tailwind tailwindcss

CSS Setup

Add the plugin and preset to your main stylesheet, for example app.css:

@import "tailwindcss";
@import "@sixsrc/brick-slider-tailwind/preset.css";
@plugin "@sixsrc/brick-slider-tailwind";

This is the required CSS configuration for a Tailwind v4 project.

Structural CSS Export

If you want to keep the BrickSlider markup classes but do not want to run Tailwind in the project, import the plain structural CSS shipped with this package:

import "@sixsrc/brick-slider-tailwind/brick-slider.css"
@import "@sixsrc/brick-slider-tailwind/brick-slider.css";

This file includes the default structural layout for BrickSlider markup without adding a visual theme.

CDN CSS

<link
  rel="stylesheet"
  href="https://unpkg.com/@sixsrc/[email protected]/lib/brick-slider.css"
/>
<link
  rel="stylesheet"
  href="https://cdn.jsdelivr.net/npm/@sixsrc/[email protected]/lib/brick-slider.css"
/>

Exported Classes

  • bs-root
  • bs-track
  • bs-container
  • bs-slide
  • bs-dots
  • bs-dot
  • bs-arrow
  • bs-prev
  • bs-next
  • bs-hidden
  • bs-peek
  • bs-peek-sm
  • bs-peek-lg

The bs-peek, bs-peek-sm, and bs-peek-lg classes are optional and should be applied to the bs-track element.

  • bs-peek-sm = 48px per side
  • bs-peek = 80px per side
  • bs-peek-lg = 120px per side

Active State Example

.active > .bs-content {
  @apply border border-violet-800 rounded-lg;
}

.bs-dot--active {
  @apply bg-violet-800 border border-violet-800;
}

Stories Progress Example

.bs-stories-progress-item {
  @apply bg-white/20;
}

.bs-stories-progress-item--active {
  @apply bg-white/35;
}

.bs-stories-progress-item--completed {
  @apply bg-white/45;
}

.bs-stories-progress-bar {
  @apply bg-white;
}

Arrow Navigation

Use bs-arrow as the base class and add:

  • bs-prev for the previous button
  • bs-next for the next button

Responsive slideSizes

Global slideSizes works as a fallback.

Priority:

  • responsive[breakpoint].useSlidesPerView === false → ignores slidesPerView from that breakpoint
  • responsive[breakpoint].useSlidesPerPage === false → ignores slidesPerPage from that breakpoint
  • responsive[breakpoint].useSlideSizes === false → ignores all slideSizes
  • responsive[breakpoint].slideSizes → overrides the global config
  • slideSizes global → fallback

Exemplo:

{
  slideSizes: {
    0: 70,
    1: 15,
    2: 15
  },
  responsive: {
    xs: {
      slidesPerView: 1,
      slidesPerPage: 1,
      useSlideSizes: false
    },
    lg: {
      slidesPerView: 4,
      slidesPerPage: 4,
      useSlidesPerPage: false
    }
  }
}

useSlidesPerView: true and useSlidesPerPage: true are unnecessary because both are implicitly enabled. useSlideSizes: true is unnecessary because slideSizes is already implicitly enabled.

Without Tailwind

If you do not want Tailwind, keep the same bs-* markup classes and use the exported brick-slider.css file as the structural base.

Monorepo Development

In the local demo of this repository, the plugin is loaded like this:

@import "../../../tailwind/src/preset.css";
@plugin "../../../tailwind/src/index.ts";