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

@loklify/nuxt

v0.2.3

Published

Loklify SDK · Nuxt 3/4 module. Zero-config translation loading via @nuxtjs/i18n integration.

Readme

@loklify/nuxt

npm

Nuxt 3/4 module for Loklify, the translation management platform for small teams. Adds a single line to your nuxt.config.ts and your app loads translations from Loklify on the fly, with full @nuxtjs/i18n integration.

Get a free Loklify account at app.loklify.com.

Install

npm install @loklify/nuxt @nuxtjs/i18n

Setup

// nuxt.config.ts
export default defineNuxtConfig({
  modules: [
    '@nuxtjs/i18n',
    '@loklify/nuxt',
  ],

  i18n: {
    locales: ['en', 'fr', 'de'],
    defaultLocale: 'en',
  },

  loklify: {
    project: 'your-project-id',
  },
})

That's all. On client-side startup, the module fetches the active locale's translations from Loklify and merges them into vue-i18n via setLocaleMessage. Switching locale auto-fetches the new language.

You'll find your project ID in your Loklify dashboard at app.loklify.com, under your project's settings.

Module options

loklify: {
  project: 'your-project-id',  // required · your Loklify project ID
  token:   '...',              // optional · Bearer token for private projects
}

| Option | Type | Required | Description | |---|---|---|---| | project | string | yes | Your Loklify project ID | | token | string | no | Bearer token for private projects |

Without @nuxtjs/i18n

The module works without @nuxtjs/i18n. It still installs a Vue plugin exposing useLoklify():

<script setup>
const { client, loadLocale } = useLoklify()
const messages = await client.loadLocale('fr')
</script>

How it works

  1. The module adds a client-side plugin that depends on i18n:plugin.
  2. On startup, it reads nuxtApp.$i18n and connects it to @loklify/vue.
  3. The current locale is fetched from https://api.loklify.com and injected via setLocaleMessage.
  4. A reactive watch handles locale changes automatically.

Runtime config

The module exposes its options through runtimeConfig.public.loklify. You can override at runtime via env vars:

NUXT_PUBLIC_LOKLIFY_PROJECT=xxx
NUXT_PUBLIC_LOKLIFY_TOKEN=xxx

Related packages

Links

License

MIT