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

@flyva/nuxt

v0.8.2

Published

Seamless page transitions for Nuxt

Readme

@flyva/nuxt

Nuxt 4 module for Flyva page transitions.

Install

pnpm add @flyva/nuxt @flyva/shared

Setup

1. Register the module

// nuxt.config.ts
export default defineNuxtConfig({
  modules: ['@flyva/nuxt'],
  flyva: {
    defaultKey: 'defaultTransition',
    transitionsDir: 'page-transitions',
  },
});

2. Write a transition

Place transition files in the directory specified by transitionsDir (default: page-transitions/). The module auto-discovers and registers them.

// page-transitions/defaultTransition.ts
import { animate } from 'animejs';
import { defineTransition } from '@flyva/shared';

export const defaultTransition = defineTransition({
  async leave(ctx) {
    const el = ctx.container;
    if (!el) return;
    await animate(el, { opacity: 0, duration: 400 });
  },
  beforeEnter(ctx) {
    const el = ctx.container;
    if (!el) return;
    el.style.opacity = '0';
  },
  async enter(ctx) {
    const el = ctx.container;
    if (!el) return;
    await animate(el, { opacity: 1, duration: 400 });
  },
});

3. Add FlyvaPage to your app

<!-- app.vue -->
<template>
  <NuxtLayout>
    <FlyvaPage />
  </NuxtLayout>
</template>

FlyvaPage registers outgoing and incoming page roots — use context.container in transition hooks instead of querying the document.

<!-- layouts/default.vue -->
<template>
  <div>
    <nav>...</nav>
    <main>
      <slot />
    </main>
  </div>
</template>

4. Use FlyvaLink

<FlyvaLink to="/about">About</FlyvaLink>

<!-- Override the default transition -->
<FlyvaLink to="/work" flyva-transition="slideTransition">Work</FlyvaLink>

<!-- Pass options -->
<FlyvaLink to="/work" :flyva-options="{ direction: 'left' }">Back</FlyvaLink>

Module options

| Option | Type | Default | Description | |--------|------|---------|-------------| | defaultKey | string | 'defaultTransition' | Key of the transition used when none is specified | | transitionsDir | string | 'flyva-transitions' | Directory containing transition files | | useNamedExports | boolean | true | Use named exports from transition files |

Explicit imports

  • @flyva/nuxt — components, composables, and shared transition types in one barrel
  • @flyva/nuxt/composablesuseFlyvaTransition, useRefStack, globalGetRefStackItem, useDetachedRoot, etc.
  • @flyva/nuxt/componentsFlyvaPage, FlyvaLink

Avoid deep paths under runtime/; composables and components use the exports map in package.json.

Auto-imported composables

The module auto-imports these — no explicit import needed in Vue files:

| Composable | Description | |------------|-------------| | useFlyvaTransition() | Returns { prepare, isRunning, stage, hasTransitioned } | | useRefStack(key, ref) | Register a Vue ref in the global ref stack | | globalGetRefStackItem(key) | Retrieve a ref from the stack | | globalGetRefStack() | Get the entire ref stack as an object |