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

@vimesh/headless

v0.7.0

Published

This is Alpine.js implementation of [Tailwind Headless UI](https://headlessui.com/). Built with [Vimesh UI](https://github.com/vimeshjs/vimesh-ui) framework, Vimesh Headless UI has some nice features: ### Ultra lightweight Vimesh Headless UI has much sma

Downloads

1,236

Readme

Vimesh Headless UI

Features

This is Alpine.js implementation of Tailwind Headless UI. Built with Vimesh UI framework, Vimesh Headless UI has some nice features:

Ultra lightweight

Vimesh Headless UI has much smaller code size

| Components | Vimesh Headless UI | Tailwind Headless UI for Vue | Tailwind Headless UI for React | | ----------- | -------------------- | -------- | ----- | | Listbox | 8k | 34k | 30k | | Combobox | 9k | 25k | 39k | | Menu | 7k | 18k | 20k | | Switch | 0.6k | 5k | 6k | | Tabs | 4k | 12k | 16k | | Dialog | 2k | 15k | 17k | | Popover | 6k | 23k | 28k | | Radio Group | 1k | 11k | 14k |

Comparing the production version of Vimesh and Tailwind headless dialog example page size, Vimesh is much smaller with more features and less bugs (check the menu display in the tailwind popup dialog).

| Vimesh | Tailwind | | ---- | ---- | | | | | 192k | 425k |

Load only used components dynamically

Components are plain html files, which could be hosted anywhere, normally at CDN. They could be shared cross different projects without extra tree shaking magic. For example, the dialog basic example uses two components hui-dialog and hui-menu. Just load them asynchronously with x-import. Vimesh UI registers corresponding native custom elements and initialize them.

<template x-component:page="dialog-basic" x-import="hui:dialog,menu" x-data="setupDialogBasicData()"
    class="overflow-y-auto">
    ...
    <hui-dialog :open="isOpen" @close="setIsOpen(false)">
        ...
        <hui-menu>
        </hui-menu>
    </hui-dialog>
    ...
</template>

No build, no bundle

What you write is what you get. Organize components to html files under meaningful namespaces. You do not need webpack, rollup, vite etc.

Getting Started

Development mode

Install development dependencies, including alpinejs, @vimesh/style, @vimesh/ui, universal-router and http-server.

yarn

Run static http server

yarn dev

Open the url http://127.0.0.1:8080/playground/dev.html

It shows an index page

There are many examples for different components with relative source code.

It uses development version of alpinejs and @vimesh/ui in the node_modules folder.

Production mode

Please check playground/index.html, which use the latest alpinejs and @vimesh/ui at unpkg.com. In fact it is also what you would do if you use Vimesh Headless UI in your real projects.

<head>
    <link rel="icon" type="image/x-icon" href="./assets/favicon.ico">

    <script src="https://unpkg.com/@vimesh/style"></script>
    <script src="https://unpkg.com/@vimesh/ui"></script>
    <script src="https://unpkg.com/alpinejs" defer></script>
    <script src="https://unpkg.com/universal-router/universal-router.min.js"></script>

    <script>
        const DEBUG = false
        $vui.config.debug = DEBUG
        $vui.config.importMap = {
            "hui": '../components/${component}.html' + (DEBUG ? '?v=' + new Date().valueOf() : '?v=0.1'),
            "app": './components/${path}${component}.html' + (DEBUG ? '?v=' + new Date().valueOf() : '?v=0.1'),
            "page": './pages/${path}${component}.html' + (DEBUG ? '?v=' + new Date().valueOf() : '?v=0.1'),
        }
    </script>
    ...
</head>

Online Playground

Yes, the online playground are 100% plain html hosted at unpkg.com. It is very old school style, right? Let's make frondend development back to what it should be.