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

@tdv_layer/transfers

v0.0.1

Published

Nuxt 3 introduces **layers**, a powerful feature for structuring your codebase into reusable and composable units. This is ideal for:

Readme

Nuxt 3 Layers Architecture

Nuxt 3 introduces layers, a powerful feature for structuring your codebase into reusable and composable units. This is ideal for:

  • Design systems or UI kits
  • Multisite applications
  • Shared logic between projects
  • White-labeling

🚀 What is a Nuxt Layer?

A layer is essentially a Nuxt project that can be extended by another. You can define layouts, components, plugins, stores, etc., inside a base layer and reuse them across multiple Nuxt apps.

Your app (consumer) imports and extends the base layer (provider) via extends: ['./features/transfers'] in nuxt.config.ts.


🧠 Key Concepts

  • A layer is just another Nuxt project (with its own nuxt.config.ts).
  • You can override anything from the base layer in your consuming app.
  • Layers support TypeScript, Pinia, composables, middleware, and more.

📁 Folder Structure Example

my-app/
├── app.config.ts
├── nuxt.config.ts      # <-- extends ./features/transfers
├── layers/
│   └── transfers/
│       ├── app.config.ts
│       ├── nuxt.config.ts
│       ├── components/
│       ├── layouts/
│       ├── pages/
│       ├── plugins/
│       └── stores/
├── pages/
├── components/
└── ...

📚 Official Documentation

Nuxt Layer Starter

Create Nuxt extendable layer with this GitHub template.

Setup

Make sure to install the dependencies:

pnpm install

Working on your layer

Your layer is at the root of this repository, it is exactly like a regular Nuxt project, except you can publish it on NPM.

The .playground directory should help you on trying your layer during development.

Running pnpm dev will prepare and boot .playground directory, which imports your layer itself.

Distributing your layer

Your Nuxt layer is shaped exactly the same as any other Nuxt project, except you can publish it on NPM.

To do so, you only have to check if files in package.json are valid, then run:

npm publish --access public

Once done, your users will only have to run:

npm install --save your-layer

Then add the dependency to their extends in nuxt.config:

defineNuxtConfig({
  extends: 'your-layer'
})

Development Server

Start the development server on http://localhost:3000

npm dev

Checkout the deployment documentation for more information.