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-core

v0.3.0

Published

Framework-neutral container and provider lifecycle for Nuxt Laravelize

Readme

@luckys_luis/nuxt-laravelize-core

Espanol | English

Framework-neutral container and provider lifecycle for Nuxt Laravelize

Install

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

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. | | ./runtime/server | Public entrypoint for this package. | | ./kit | Public entrypoint for this package. | | ./testing | Public entrypoint for this package. |

Core

@luckys_luis/nuxt-laravelize-core provides the dependency container, typed tokens, service providers, application lifecycle and logging. Feature modules install it automatically.

pnpm add @luckys_luis/nuxt-laravelize-core

Container and tokens

| API | Purpose | |---|---| | createToken<T>(key) | Creates a typed service identifier. | | createContainer() | Creates an empty container. | | bind(token, factory) | Registers a transient service. | | singleton(token, factory) | Registers one shared instance. | | scoped(token, factory) | Registers one instance per child scope. | | instance(token, value) | Registers an existing value. | | make(token) / has(token) | Resolves a service or checks its registration. | | createScope() | Creates a request or operation scope. | | seal() | Prevents further registrations. Nuxt seals after boot. | | dispose() | Disposes this container. Dispose each child scope separately. |

import { createContainer, createToken } from '@luckys_luis/nuxt-laravelize-core/runtime'

interface Clock { now(): Date }
const clockToken = createToken<Clock>('app.clock')
const container = createContainer()

container.singleton(clockToken, () => ({ now: () => new Date() }))
container.seal()

const now = container.make(clockToken).now()

Implement ServiceProvider.register() for bindings and optional boot() for work that requires all providers to be registered.

import type { Container, ServiceProvider } from '@luckys_luis/nuxt-laravelize-core/runtime'

export default class ClockServiceProvider implements ServiceProvider {
  register(container: Container) {
    container.singleton(clockToken, () => ({ now: () => new Date() }))
  }
}

Register an application provider from a Nuxt module with addLaravelizeProvider(nuxt, path, mode) from @luckys_luis/nuxt-laravelize-core/kit. In Nitro handlers, the auto-imports useContainer(event) and useLogger(event) resolve the current request scope.

Logging

| API | Purpose | |---|---| | ConsoleLogger | Writes human-readable records to a console. | | StructuredLogger | Writes structured JSON records. | | FileLogger | Appends records to a file; use in Node runtimes. | | loggerFor(resolver) | Resolves loggerToken or returns a warning-level console fallback. | | shouldEmit(level, minimum) | Compares log levels using LOG_LEVELS. | | FakeLogger | Records logs for assertions through /testing. |

import { ConsoleLogger } from '@luckys_luis/nuxt-laravelize-core/runtime'

const logger = new ConsoleLogger({ threshold: 'info' })
logger.info('Invoice created', { invoiceId: 'inv_1' })

The lifecycle classes LaravelizeApplication and Kernel, container errors, logger contracts and option interfaces are exported for framework and adapter authors. Most applications use providers and the Nuxt runtime helpers instead.

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-testing, @luckys_luis/nuxt-laravelize-execution-context.