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

@omerdlw/base-framework

v1.0.6

Published

Microkernel engine and first-party declarative UI modules for app-like Next.js products.

Readme

@omerdlw/base-framework

Microkernel orchestration engine and first-party declarative UI modules for app-like Next.js 16 (App Router) & React 19 web applications.

npm version License: MIT TypeScript 5.8 React 19


📖 Complete Documentation Index

For in-depth architecture guides and module-by-module references, explore the docs/ folder:

General Architecture Guides

Module & Component Reference


✨ Features

  • ⚡ Microkernel Architecture: Ultra-lean orchestration host with topological module dependency sorting, transactional multi-source registry, and atomic route lifecycle commits.
  • 🧩 First-Party Declarative UI Modules: 9 production-tested modules (dock, modal, notification, ambient, background, context-menu, controls, loading, media) that communicate strictly through typed contracts without tight coupling.
  • 🎯 Single Route Declaration (usePage): Cleanly declare titles, navigation cards, modals, loading states, and background media in a single atomic hook call.
  • 🔒 Type-Safe Result Pattern (Result<T, E>): Functional, bulletproof error handling with ok(), err(), and direct feedback bridging via toast.fromResult().
  • 🛡️ Cross-Bundle Context Deduplication: Guarantees stable React Context singletons across Next.js split chunks and monorepo boundaries.
  • 🎨 Tailwind CSS v4 & OKLCH Ready: GPU-accelerated motion presets (translate3d, scale) and semantic color tokens.

📦 Installation

npm install @omerdlw/base-framework motion

Ensure peer dependencies are satisfied (next >= 15.0.0, react >= 19.0.0, react-dom >= 19.0.0, motion >= 12.0.0).


🚀 Quick Start

1. Configure Providers in Your Next.js App

Create your client providers component (e.g. src/app/providers.tsx):

"use client";

import { CoreProvider } from "@omerdlw/base-framework/provider";
import { dockModule } from "@omerdlw/base-framework/modules/dock";
import { modalModule } from "@omerdlw/base-framework/modules/modal";
import { notificationModule } from "@omerdlw/base-framework/modules/notification";
import { ambientModule } from "@omerdlw/base-framework/modules/ambient";
import { backgroundModule } from "@omerdlw/base-framework/modules/background";
import { loadingModule } from "@omerdlw/base-framework/modules/loading";

const modules = [
  dockModule,
  modalModule,
  notificationModule,
  ambientModule,
  backgroundModule,
  loadingModule,
];

export function Providers({ children }: { children: React.ReactNode }) {
  return <CoreProvider modules={modules}>{children}</CoreProvider>;
}

Wrap your root app/layout.tsx:

import { Providers } from "./providers";
import "./globals.css";

export default function RootLayout({ children }: { children: React.ReactNode }) {
  return (
    <html lang="en">
      <body>
        <Providers>{children}</Providers>
      </body>
    </html>
  );
}

2. Tailwind CSS v4 Configuration

Add the package path to your @source scanning inside src/app/globals.css:

@import "tailwindcss";
@source "../node_modules/@omerdlw/base-framework";

3. Declare Route State with usePage

In any route client component:

"use client";

import { usePage } from "@omerdlw/base-framework/kernel";

export default function DashboardPage() {
  const page = usePage({
    title: "Analytics Dashboard",
    dock: {
      description: "Live system metrics and user activity",
      icon: "solar:widget-bold",
    },
    background: {
      image: "/media/dashboard-bg.webp",
      overlay: true,
    },
    loading: false,
  });

  return (
    <main className="p-8">
      <h1 className="text-3xl font-bold">Analytics</h1>
      <button
        onClick={() => page.modules.notification?.toast("Data refreshed!")}
        className="mt-4 rounded bg-white px-4 py-2 font-semibold text-black"
      >
        Refresh
      </button>
    </main>
  );
}

📚 Subpath Export Directory

| Subpath | Purpose & Key Exports | | :---------------------------------- | :---------------------------------------------------------------- | | @omerdlw/base-framework | Root exports of all sub-systems | | @omerdlw/base-framework/kernel | usePage, defineModule, definePeer, createContextRegistry | | @omerdlw/base-framework/provider | CoreProvider composition pipeline & ModuleHost | | @omerdlw/base-framework/result | ok(), err(), isResult(), type Result<T, E> | | @omerdlw/base-framework/events | Decoupled event bus (globalEvents, EVENT_TYPES) | | @omerdlw/base-framework/theme | ThemeProvider, useTheme, defineThemeSpec | | @omerdlw/base-framework/tokens | Motion easing, timing presets, z-index hierarchy | | @omerdlw/base-framework/atoms | Primitive components (Button, Icon, Spinner, Tooltip) | | @omerdlw/base-framework/utils | Pure utilities (cn, report, createStore, createScheduler) | | @omerdlw/base-framework/hooks | Essential hooks (useClickOutside, useGlobalEvent, useStore) | | @omerdlw/base-framework/error | Error boundaries and reporter sink | | @omerdlw/base-framework/modules/* | 9 standalone modules (dock, modal, notification, etc.) |


🤖 For AI Coding Assistants (Cursor, Antigravity, Claude Code)

When developing a project that consumes @omerdlw/base-framework, copy templates/AGENTS.md into your downstream project root as AGENTS.md. This gives the AI assistant instant, complete context over the framework's strict rules, boundaries, and best practices.


📄 License

MIT © Ömer Deliavcı