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

tap-vue

v0.0.2

Published

Use React hooks in Vue. Hook runtime powered by @assistant-ui/tap.

Readme

tap-vue

Use React hooks in Vue. Hook runtime powered by tap.

Install

npm install tap-vue

Hooks as composables

toComposable(hook) turns a React hook into a Vue composable.

import { useEffect, useState } from "react";
import { toComposable } from "tap-vue";

const useCount = (initialValue: number) => {
  const [count, setCount] = useState(initialValue);
  const bump = () => setCount((c) => c + 1);
  return { count, bump };
};

const useVueCount = toComposable(useCount);
<script setup>
const counter = useVueCount(5); // ShallowRef<{ count, bump }>
</script>

<template>
  <button @click="counter.bump">{{ counter.count }}</button>
</template>

The hook mounts when the component's scope is created and unmounts (running effect cleanups) when the scope is disposed.

Reactive args

const step = ref(1);
const counter = useVueStepCount(step);

step.value = 10; // hook re-renders with the new step

Args accept plain values, refs, and getters. When a reactive arg changes, the hook re-renders with the new value — its internal state is preserved, just like a React component receiving new props. Like props, arg changes are batched: mutations in the same tick produce a single re-render on the next tick.

Destructuring

The composable returns a single ShallowRef snapshot, so plain destructuring loses reactivity. To destructure into individual refs, use VueUse's toRefs:

import { toRefs } from "@vueuse/core";

const { count, bump } = toRefs(useVueCount(0));
count.value; // Ref<number>, stays reactive
bump.value(); // functions are wrapped too — call via .value in script

Templates auto-unwrap, so {{ count }} and @click="bump" work directly. Don't write to the refs — state is owned by the hook.

Synchronous updates

Updates land on tap's async scheduler by default: after calling bump(), the new count appears a tick later. If you want Vue's mutation semantics — call a function, read the updated state immediately — wrap the ref with toSyncCallbacks:

import { toSyncCallbacks } from "tap-vue";

const counter = toSyncCallbacks(useVueCount(5));

counter.value.bump();
counter.value.count; // already updated

toSyncCallbacks returns a ref whose functions (including those nested on the snapshot) flush the hook's re-render synchronously before returning. Errors thrown by the hook during such a re-render throw at the call site. Updates from other sources (timers, subscriptions inside the hook) still land on the async scheduler; use flushTapSync from @assistant-ui/tap if you need to force those synchronously.