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

@verdnatura/vn-front-lib

v0.0.8

Published

Vue 3 component and composable library

Downloads

890

Readme

vn-front-lib

A shared library of Vue 3 components and composables used across the salix-front and hedera-web projects. It is not a standalone app — it's built in library mode (Vite build.lib) and consumed as a dependency.

What's inside

  • lib/components/ — Vue components (prefixed with Vn, e.g. VnInput).
  • lib/composables/ — reusable composables (e.g. useRequired, useValidator).
  • lib/stores/ — Pinia stores (e.g. useValidationsStore).
  • lib/i18n/locale/ — translation files (en.yml, es.yml).

pinia, vue-i18n, axios, validator and quasar are expected to be provided by the consuming project (declared as peerDependencies).

Recommended VS Code extension

This project uses oxlint and oxfmt for linting and formatting. It's advisable to install the Oxc VS Code extension, which powers format-on-save and inline lint diagnostics based on the .oxlintrc.json and .oxfmtrc.json config files in this repo.

Scripts

pnpm install
pnpm run dev         # Vite dev server
pnpm run build       # build the library (output to dist/)
pnpm run lint        # oxlint
pnpm run lint:fix    # oxlint --fix
pnpm run fmt         # oxfmt
pnpm run fmt:check   # oxfmt --check

Developing locally against another project

To test changes locally in another project (e.g. salix-front or hedera-web) without publishing, add this repo as a real pnpm workspace member rather than using a plain link: dependency, so vue/pinia get deduped into a single instance across both projects:

  1. In the consuming project's pnpm-workspace.yaml, add this repo as a package:

    packages:
        - .
        - ../vn-front-lib
  2. In the consuming project's package.json, depend on it via the workspace protocol, using the real package name:

    "vn-front-lib": "workspace:@verdnatura/vn-front-lib@*",
  3. Enable the vnSource resolution condition in the consumer's Vite/Vitest config so imports resolve to this repo's lib/ source instead of the dist/ build:

    resolve: {
        conditions: ['vnSource'],
    },
  4. Reinstall dependencies in the consuming project (pnpm install), then run pnpm why vue -r / pnpm why pinia -r to confirm only one version of each resolves across the workspace.