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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@mvuijs/core

v0.0.4

Published

Minimum Viable UI

Downloads

10

Readme

Mvui - A Minimalist Webcomponent Framework

Tests

"Minimum Viable UI"

Yes, this is a new frontend framework, and no, this is not a joke.

import { Component, rx, h } from '@mvuijs/core';

@Component.register
export class CounterComponent extends Component {
  render() {
    const count = new rx.State(0);
    return [
      h.p([
        h.button({ events: {
          click: _ => count.next(c => c + 1)
        }}, 'Increment'),
        h.span(count.derive(v => `count: ${v}`))
      ])
    ];
  }
}

Projects Status

Mvui is almost ready for release. There is still some cleanup left to be done and some documentation to write and publish. But it has been used in practice for a while now in Wournal and seems to be stable. There are also plenty of unit tests.

Dear God Why Yet Another Frontend Framework?

Fundamentally, I (@dominiksta) believe that frontend development is significantly overcomplicated for small to medium size applications. Mvui is built on this intuition. It does not strive for perfection in nether syntax nor performance nor its programming model but to simply be good enough while making it easy to reason about the code.

Core Features:

  • A fully typesafe component model based on webcomponents
  • Templates and styling are defined in TS/JS, so there are no special requirements for your editor and they can be typechecked
  • Reactivity is implemented on top of a very minimal recreation of some the core principles of rxjs. This has several advantages:
    • The reactivity is independent of the component model, much like signals in SolidJS. You can write your business logic reactively while not locking yourself into using Mvui.
    • Updates to the DOM only happen exactly where some value has changed. Much like SolidJS (all be it less powerful), a component renders only once upon being mounted. When an Observable is used in the template, it is automatically subscribed to and any change to it will trigger a DOM update.
    • Anyone familiar with ReactiveX or rxjs or angular should be immediatly familiar with the reactivity model.
  • Wrapping existing Webcomponents to work with Mvui in a typesafe way