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

@camilaprav/makelovenotwar

v0.0.0

Published

PostCSS utility for per-element scoping of different CSS framework class names

Readme

💘 Make Love Not War

A PostCSS CLI tool and browser-side enabler that scopes CSS frameworks (like Tailwind, Bootstrap, and Bulma) to activate only when a specific class (e.g., .tw, .bs, .bu) is present on the same element. This enables per-element opt-in without global interference or class renaming.


Why?

When using multiple CSS frameworks on the same page, class name collisions (like container, text-center, etc.) are common. Tailwind offers a prefix option, but that requires rewriting every class and doesn’t help with framework interoperability.

This tool solves that by:

  • Transforming selectors like .text-red-500 into .tw.text-red-500, so Tailwind utilities only activate when class="tw text-red-500" is present.
  • Allowing Bootstrap and Bulma to be processed similarly (e.g., with .bs, .bu), enabling all three to coexist cleanly.
  • Eliminating the need descendant wrappers (can still cause conflicts) or class name prefixing (too verbose).

Features

  • 🔀 Namespace any CSS framework with a single opt-in class (e.g., tw, bs, bu)
  • 🧩 Keeps original class names intact
  • 📦 CLI tool for build-time processing
  • 🧪 Optional runtime support for Tailwind Play via MutationObserver workaround

CLI Usage

Use via npx with no installation required:

npx @camilaprav/makelovenotwar <prefix> <input.css> [options]

Arguments:

  • <prefix> – the class to use as a namespace (e.g., bs for Bootstrap)
  • <input.css> – path to the source CSS file

Options:

  • -o, --output <file> – specify output file (default: stdout)

What it does:

  • Rewrites selectors like .box.bu.box.
  • Activates Bulma classes only when class="bu" is present.

Example:

npx @camilaprav/makelovenotwar bs bootstrap.css -o bootstrap-scoped.css
npx @camilaprav/makelovenotwar bu bulma.css -o bulma-scoped.css

Then in HTML:

<link rel="stylesheet" href="bootstrap-scoped.css">
<link rel="stylesheet" href="bulma-scoped.css">
<div class="bs container mt-4">Bootstrap</div>
<div class="bu container is-primary">Bulma</div>

This enables side-by-side usage of multiple frameworks without class name collisions.


Browser Usage (for Tailwind Play CDN)

To use this with a Tailwind Play environment where build-time processing isn’t available or is undesirable, inject the following scripts:

<script src="https://cdn.jsdelivr.net/npm/@tailwindcss/browser@4"></script>
<script type="module" src="https://esm.sh/@camilaprav/makelovenotwar/tailwind-play.js"></script>

What it does:

  • Finds the inline <style> block with Tailwind utilities.
  • Rewrites selectors like .text-red-500.tw.text-red-500.
  • Activates Tailwind utilities only when class="tw" is present.

To prevent a flash of unstyled Tailwind content, add the hidden attribute to the body element. tailwind-play.js removes it automatically once patching is ready.