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

@mojimoto/vue

v0.3.0

Published

Vue 3 components and composables for rendering Mojimoto CMS content (rich text, images, links).

Readme

@mojimoto/vue

Vue 3 components and composables for rendering Mojimoto content. For Nuxt, use @mojimoto/nuxt instead — it wires this package up for you (auto-imports, SSR, global components).

npm i @mojimoto/vue @mojimoto/client

Setup

Register a client (and optional defaults) as a plugin:

import { createApp } from 'vue';
import { createClient } from '@mojimoto/client';
import { createMojimoto } from '@mojimoto/vue';
import App from './App.vue';

const cms = createClient({ endpoint, project, token });

createApp(App)
  .use(createMojimoto({ client: cms, linkResolver: (l) => `/${l.uid}` }))
  .mount('#app');

Or inside a component's setup() with provideMojimoto({ client, linkResolver }).

Components

<MojiRichText>

<script setup>
import { MojiRichText } from '@mojimoto/vue';
import { h } from 'vue';
</script>

<template>
  <MojiRichText :field="doc.data.body" :link-resolver="(l) => `/${l.uid}`">
    <template #fallback>
      <p class="text-stone-400">No content yet.</p>
    </template>
  </MojiRichText>
</template>

Override individual nodes with the components prop (each returns a VNode or string; keys are handled for you):

<script setup>
import { h } from 'vue';
const components = {
  heading2: ({ children }) => h('h2', { class: 'text-2xl font-serif' }, children),
};
</script>

<template>
  <MojiRichText :field="doc.data.body" :components="components" />
</template>

<MojiImage>, <MojiText>, <MojiLink>

<MojiImage :field="doc.data.background_image" alt="Hero" :transform="{ width: 1280, format: 'webp' }" />
<MojiText :field="doc.data.intro" as="h1" />
<MojiLink :field="doc.data.cta_link" class="btn">Get started</MojiLink>

<MojiLink> accepts an as prop to render through a router link component:

<MojiLink :field="doc.data.cta_link" :as="RouterLink">Read more</MojiLink>

Composables

Reactive, client-side data fetching (re-runs when args change, aborts on cleanup):

<script setup>
import { useMojiQuery, useMojiDocument } from '@mojimoto/vue';

const { data: posts, loading } = useMojiQuery({ type: 'blog_post', perPage: 10 });
const { data: home } = useMojiDocument('marketing_page', 'home');
</script>

useMojiQuery also accepts a getter for reactive options: useMojiQuery(() => ({ type, uid: uid.value })).

For SSR in Nuxt, prefer the useMojiQuery / useMojiDocument from @mojimoto/nuxt, which wrap useAsyncData so data is fetched on the server and hydrated on the client.

Embed safety

The default embed renderer injects provider oEmbed HTML via v-html. That HTML originates from your CMS's oEmbed provider (editor-controlled, same trust model as Prismic/Contentful renderers). If you embed untrusted third-party content, override the embed component to sanitize it or render an iframe yourself.

License

MIT © Your Ikigai Ltd