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 🙏

© 2024 – Pkg Stats / Ryan Hefner

esbuild-css-as-string

v1.0.8

Published

Transform your CSS files into string

Downloads

35

Readme

CSS as String Plugin for esbuild

Transform your CSS files into string exports effortlessly with the esbuild-css-as-string plugin for esbuild. Designed to streamline the development of web components and widgets, this plugin is a must-have for developers working with Shadow DOM or seeking to encapsulate their styles within JavaScript modules. By enabling CSS imports directly as strings, it offers an elegant solution for styling isolation, enhancing both the scalability and maintainability of your projects.

Features

  • CSS Import as String: Easily import CSS files as strings, perfect for injecting styles into Shadow DOM.
  • Easy Integration: Seamlessly integrates with your esbuild setup, making it straightforward to add to your project.
  • Improved Style Encapsulation: Achieve style encapsulation within web components, avoiding global style leaks.
  • Shadow DOM Support: Ideal for projects utilizing Shadow DOM for component-based architectures.

Installation

To get started with the esbuild-css-as-string plugin, first ensure you have esbuild installed in your project. If not, you can add it along with the esbuild-css-as-string plugin by running:

npm install esbuild --save-dev
npm install esbuild-css-as-string --save-dev

Setup

Integrating the esbuild-css-as-string plugin into your esbuild configuration is straightforward. Here's a quick guide:

// esbuild.config.js
import * as esbuild from 'esbuild'
import cssAsStringPlugin from 'esbuild-css-as-string';

esbuild.build({
  entryPoints: ['src/index.js'],
  bundle: true,
  outfile: 'dist/bundle.js',
  plugins: [cssAsStringPlugin],
}).catch(() => process.exit(1));

Usage

Once installed and configured, you can import CSS files as strings within your JavaScript modules. This feature is especially useful for applying styles within Shadow DOM. Here’s an example of how to use it:

import styles from './styles.css';

const initWidget = () => {
  const rootElement = document.createElement("div");
  const shadowRoot = rootElement.attachShadow({ mode: "open" });
  const styleElement = document.createElement("style");
  
  styleElement.textContent = styles;
  shadowRoot.appendChild(styleElement);
  document.body.appendChild(rootElement);
};

initWidget();

This setup ensures that your styles are encapsulated within the Shadow DOM, preventing any style leakage and maintaining the integrity of your component's visual presentation.

Contributing

We welcome contributions! If you have suggestions for improvements or encounter any issues, please feel free to open an issue or submit a pull request.

License

This project is licensed under the MIT License - see the LICENSE file for details.