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

tailbreak

v0.2.2

Published

Lightweight library that let's you detect the current breakpoint of the window from the breakpoints in your tailwind config

Downloads

3

Readme

About The Project

Example Gif

tailbreak is a ultra lightweight (80 loc!) utility that let's you detect which tailwind breakpoint you are in based on your configuration file. It supports all the custom screen breakpoints from the tailwind documentation. It has no dependencies, other than the reccomended resolveConfig which already comes with tailwind.

Getting Started

To install in your project / web application

npm install tailbreak

To get the source code & tests

  1. Clone the repo
    git clone https://github.com/h-arry-smith/tailbreak.git
  2. Install NPM packages
    npm install

Dependencies

  • None !

Dev-Dependencies

"autoprefixer": "^10.1.0",
"chai": "^4.2.0",
"mocha": "^8.2.1",
"mock-browser": "^0.92.14",
"postcss": "^8.2.1",
"tailwindcss": "^2.0.2"

Usage

Default Configuration

  import Tailbreak from 'tailbreak';
  const tb = Tailbreak();

  if (tb.sm) { ... }
  if (tb.md) { ... }
  if (tb.lg) { ... }
  if (tb.xl) { ... }
  if (tb['2xl']) { ... }

Passing nothing to the constructor will load the defaults as of Tailbreak 2.0.2.

Custom Configuration

// tailwind.config.js
module.exports = {
  theme: {
    screens: {
      'tablet': '640px',
      'laptop': '1024px',
      'desktop': '1280px'
    }
  }
}
// index.js
import Tailbreak from 'tailbreak'
import resolveConfig from 'tailwind/resolveConfig'
import customConfig from 'tailwind.config'

const tb = Tailbreak(resolveConfig(customConfig));

if (tb.tablet) {...}
if (tb.laptop) {...}
if (tb.desktop) {...}

See the tailwind breakpoint docs for more information on the formatting of custom breakpoints.

It's reccomended to use the resolveConfig function that tailwind provides, as this will smart merge the configuration files. It's also possible to just pass the config in code if you like, if you are concerned about bundle size. The package currently does not support the extends functionality - use resolveConfig for this for better future proofing.

See the resolveConfig docs from tailwind for suggestions on static configuration for production builds.

...
const tb = Tailbreak({
  theme: {
    screens: {
      'phone': '640px'
      ... 
    }
  }
});

If you do this, I reccomend you create a tailbreak object in a file, export it and import this preconfigured object in your project, so that there is one source of truth.

Using custom configs with React

If you are using tailbreak in a react project (or any other framework that doesn't allow imports outside of /src/) then make sure to move the config inside /src and tell tailwind the new location.

For example, with craco and create-react-app:

// craco.config.js
module.exports = {
  ...
style: {
  postcss: {
    plugins: [
      require('tailwindcss')('/src/tailwind.config.js'),
      require('autoprefixer'),
      ...
    ],
  },
},
}

If you are using the default tailwind breakpoints there is no need to do this, just call Tailbreak().

Acessing the media queries

You can access the MediaQueryList objects, by prepending _ to the relevant breakpoint

console.log(tb._sm.media)
// -> (min-width: 640px)

Contributing / Issues / Suggestions

Contributions, suggestions, bug reports are all welcome in the issue tracker.

License

Distributed under the MIT License. See LICENSE for more information.

Contact

Harry Smith - [email protected]

Project Link: https://github.com/h-arry-smith/tailbreak