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

@luckys_luis/nuxt-laravelize-rate-limiter

v0.3.0

Published

Cache-backed rate limiting for Nuxt Laravelize

Readme

@luckys_luis/nuxt-laravelize-rate-limiter

Espanol | English

Cache-backed rate limiting for Nuxt Laravelize

Install

pnpm add @luckys_luis/nuxt-laravelize-rate-limiter
// nuxt.config.ts
export default defineNuxtConfig({
  modules: ['@luckys_luis/nuxt-laravelize-rate-limiter'],
})

Package-specific usage

The package exposes a small, explicit surface. Configure its dependencies from an application provider or adapter and test its boundaries before promoting it to production.

Public entrypoints

Use only these public entrypoints. Paths not listed here are internals and may change without notice.

| Entrypoint | Use | |---|---| | package root | Public entrypoint for this package. | | ./runtime | Public entrypoint for this package. |

Rate limiting

@luckys_luis/nuxt-laravelize-rate-limiter provides cache-backed fixed-window limits. The complete preset registers it automatically; granular installations can add it directly.

pnpm add @luckys_luis/nuxt-laravelize-rate-limiter

Consume an attempt with the auto-imported useRateLimiter(event). The returned metadata is suitable for application responses and logs.

export default defineEventHandler(async (event) => {
  const result = await useRateLimiter(event).hit(`login:${userId}`, 5, 60)
  return {
    allowed: result.allowed,
    remaining: result.remaining,
    retryAfter: result.retryAfter,
  }
})

Use ThrottleRequests in a Laravelized middleware pipeline to reject excess requests with 429 Too Many Requests. It adds X-RateLimit-Remaining, X-RateLimit-Reset, and, when rejected, Retry-After.

const throttle = new ThrottleRequests(useRateLimiter(event), {
  key: event => getRequestIP(event, { xForwardedFor: true }) ?? 'unknown',
  maxAttempts: 60,
  decaySeconds: 60,
})

return await throttle.handle(event, next)

| API | Purpose | |---|---| | hit(key, maxAttempts, decaySeconds?) | Atomically consumes one attempt and returns window metadata. | | attempts(key) / remaining(key, max) | Inspects current usage without consuming an attempt. | | clear(key) | Removes attempts and timer for one logical key. | | rateLimiterToken | Resolves or replaces the configured limiter. | | useRateLimiter(event) | Resolves the request-scoped singleton in Nitro. |

Distributed enforcement requires a shared cache adapter whose add and increment operations are atomic. The default InMemoryCache only coordinates requests handled by one long-lived process. Derive keys from trusted, bounded identifiers; hashing unbounded user input avoids attacker-controlled cache key growth.

Compatibility and boundaries

Respect the at-least-once delivery, durability, authorization, tenant isolation, and secret-handling warnings in the reference section. Examples do not replace server-side authentication, authorization, or validation.

The shared API and security reference lives in the module guide. This page summarizes this package's contract and keeps copy-pasteable examples.

Related packages

@luckys_luis/nuxt-laravelize-cache, @luckys_luis/nuxt-laravelize-queue-middleware.