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

bakelor-tailwind-editors

v0.0.32

Published

`bakelor-tailwind-editors` is a library styled with Tailwind CSS. To ensure the styles are applied correctly in your project, follow the configuration steps below.

Downloads

10

Readme

Bakelor-Tailwind-Editors Configuration Guide

bakelor-tailwind-editors is a library styled with Tailwind CSS. To ensure the styles are applied correctly in your project, follow the configuration steps below.

Tailwind CSS Configuration for Bakelor-Tailwind-Editors

1. Update Tailwind CSS Configuration File

Ensure your tailwind.config.js file in your main project (not the library) is configured to consider the styles from bakelor-tailwind-editors. Update the content section as follows:

module.exports = {
  // ...
  content: [
    './src/**/*.{html,ts}', // Your Angular files
    './node_modules/bakelor-tailwind-editors/**/*.{html,ts,js,mjs,scss}', // Bakelor-Tailwind-Editors library
  ],
  // ...
}

This configuration ensures that Tailwind CSS considers the classes used within the bakelor-tailwind-editors library during the purge process, preventing them from being removed in the production build.

2. Include Library Styles and Assets in Your Project

In your angular.json file, ensure that the styles and assets from bakelor-tailwind-editors are included in your project's build options:

{
  // ...
  "projects": {
    "your-app-name": {
      // ...
      "architect": {
        "build": {
          // ...
          "options": {
            // ...
            "styles": [
              "./node_modules/bakelor-tailwind-editors/assets/styles/common.scss", // Library styles
              "src/styles.scss", // Your style file
              // ...
            ],
            "assets": [
              "src/favicon.ico",
              "src/assets",
              {
                "glob": "**/*",
                "input": "./node_modules/bakelor-tailwind-editors/assets",
                "output": "/assets/"
              }
            ],
            // ...
          },
          // ...
        },
        // ...
      },
      // ...
    },
    // ...
  },
  // ...
}

Note

Ensure that your application is set up to include the styles and scripts from the bakelor-tailwind-editors library. If you face any issues with styles not being applied, double-check the paths and ensure that the Tailwind CSS classes used within the library are not being purged unintentionally.