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

@preact-mvc/core

v0.1.5

Published

Angular-inspired modules/DI/decorators + class-based JSX views rendered by Preact + signal reactivity

Readme

@preact-mvc/core

CI codecov Socket Badge

Angular-inspired architecture rendered by Preact: @Module/@Component decorators, hierarchical dependency injection, class-based View components, controllers, an injector-scoped router, and signal reactivity via @preact/signals — all over plain JSX, with no template compiler.

PreactMVC — documentation

Install

npm install @preact-mvc/core preact @preact/signals

Point JSX at Preact (tsconfig.json):

{
  "compilerOptions": {
    "jsx": "react-jsx",
    "jsxImportSource": "preact",
    "experimentalDecorators": true,
    "useDefineForClassFields": false
  }
}

A view is a class

View subclasses are constructed once per mount inside their own injector scope — inject() works in field initializers and constructors, render() stays hook-free, and signals drive re-rendering:

import { Component, View, inject, signal, computed } from '@preact-mvc/core';

@Component()
export class CounterView extends View {
  count = signal(0);
  doubled = computed(() => this.count.value * 2);

  render() {
    return (
      <section>
        <button onClick={() => (this.count.value -= 1)}>−</button>
        <span>{this.count.value}</span>
        <button onClick={() => (this.count.value += 1)}>+</button>
        <p>doubled: {this.doubled.value}</p>
      </section>
    );
  }
}

Modules are the app map

import { Module, RouterModule } from '@preact-mvc/core';
import { AppShell } from './app.shell';
import { routes } from './app.routes';

@Module({
  imports: [RouterModule.forRoot(routes)],
  providers: [{ provide: API_URL, useValue: '/api' }],
  bootstrap: [AppShell],
})
export class AppModule {}
// main.tsx
import { bootstrap } from '@preact-mvc/core';
import { AppModule } from './app/app.module';

bootstrap(AppModule, document.getElementById('app')!);

components/bootstrap declarations are enforced ownership: a declared view may only mount where its module's injector is an ancestor. Undeclared views mount anywhere — structure is opt-in per declaration.

DI, controllers, router

  • @Injectable/@Controller classes resolve through the element-injector hierarchy — view providers → module providers → root, closest scope wins.
  • OnInit/OnDestroy lifecycle plus DestroyRef make teardown declaration-driven instead of useEffect cleanup.
  • RouterModule.forRoot(routes) + <RouterOutlet/> + <Link/> give you nested routes whose module boundaries get their own child injectors.

Published builds ship compiled dist/ (.js + .d.ts).