Skip to content
PluginStats

@tkh/tailwind-plugin-full-bleed weekly downloads statistics

By tkh (5 listings) · npm · Tailwind plugins

Tailwindcss plugin to break elements out of width constraints and take up the full viewport

View on npm Fresh · Oct 28, 2026

@tkh/tailwind-plugin-full-bleed has 0 recorded weekly downloads on npm, ranking #2192 of 2,644 tracked listings.

Weekly downloads
0
Official API · Oct 26, 2026
7-day growth
—
Insufficient history
30-day growth
—
Insufficient history
90-day growth
—
Insufficient history
Rank
#2192
Among tracked npm listings

About @tkh/tailwind-plugin-full-bleed

@tkh/tailwind-plugin-full-bleed

Tailwindcss plugin to break elements out of width constraints and take up the full viewport.

Install

npm install @tkh/tailwind-plugin-full-bleed

Usage

Merge the plugin configuration with your tailwind.config.js

module.exports = {
  plugins: [require('@tkh/tailwind-plugin-full-bleed')()],
}

Description from the npm listing.

  • full-bleed
  • full width
  • plugin
  • tailwind css
  • tailwind
  • tailwindcss-plugin
  • tailwindcss

README badge

Show your rank in a README or on your website. The badge updates automatically.

Charts

Images: 30d · 1y · all time · 1600×900 dark

Adoption over time

@tkh/tailwind-plugin-full-bleed weekly downloads on npm, last 90 days: 0 weekly downloads as of Oct 26, 2026.@tkh/tailwind-plugin-full-bleedWeekly downloads on npm · Last 90 days0downloads / week-1-0.500.51Jul 28Aug 12Aug 27Sep 11Sep 26Oct 11Oct 26downloads / weekOct 26, 2026 – Oct 26, 2026 · 1 observations · Updated Oct 26, 2026pluginstats.com
@tkh/tailwind-plugin-full-bleed weekly downloads on npm, last 90 days: 0 weekly downloads as of Oct 26, 2026.

7/30/90-day growth

@tkh/tailwind-plugin-full-bleed weekly downloads growth on npm: 7-day growth unavailable, 30-day growth unavailable, 90-day growth unavailable.@tkh/tailwind-plugin-full-bleedWeekly downloads growth on npm0downloads / week now7-day growthinsufficient historyInsufficient history30-day growthinsufficient historyInsufficient history90-day growthinsufficient historyInsufficient historyGrowth vs. nearest observation to each baseline date · Updated Oct 26, 2026pluginstats.com
@tkh/tailwind-plugin-full-bleed weekly downloads growth on npm: 7-day growth unavailable, 30-day growth unavailable, 90-day growth unavailable.

Ranking history

@tkh/tailwind-plugin-full-bleed npm ranking history: currently #2192 (by weekly downloads).@tkh/tailwind-plugin-full-bleednpm ranking · by weekly downloads · Last 90 days#2192current rank#2190#2191#2192#2193#2194Jul 30Aug 14Aug 29Sep 13Sep 28Oct 13Oct 28rankOct 28, 2026 – Oct 28, 2026 · 1 observations · Updated Oct 26, 2026pluginstats.com
@tkh/tailwind-plugin-full-bleed npm ranking history: currently #2192 (by weekly downloads).

Listing placement

All npm2,642 listings · 133 pages · 1,322 shown · page 132, #15 (overall #2,635)
All npm: every listing in weekly downloads order

Listing placement

Tailwind plugins268 listings · 14 pages · page 14, #6 (overall #266)
Tailwind plugins: every listing in weekly downloads order

Filled points are observed values; hollow points come from Internet Archive snapshots of the listing page. Dashed segments span periods with no observations — values between points are not interpolated.

Each band is one page of 20. Weekly downloads on a linear scale. Placement is projected from weekly downloads, so it can differ from the marketplace's own sort order. Hover a dot to see the listing.

Recent observations

Full history (1)
Recent weekly downloads observations for @tkh/tailwind-plugin-full-bleed
Date (UTC)Weekly downloadsChange vs. previous
0—

Similar npm Tailwind plugins plugins

All 20 @tkh/tailwind-plugin-full-bleed alternatives

Data source

Weekly downloads (trailing 7 complete days) come from the official npm downloads API. Downloads include CI and mirrors and are not equivalent to installs or users. npm publishes no ratings.

Listing: https://www.npmjs.com/package/@tkh/tailwind-plugin-full-bleed. First seen Oct 28, 2026; last successful collection Oct 28, 2026. See the methodology.