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

@enos5/enos-vue-default

v1.8.16

Published

Shared Vue 3 UI components from Enos, packaged as the Default workspace inside the monorepo.

Readme

@enos5/enos-vue-default

Shared Vue 3 UI components from Enos, packaged as the Default workspace inside the monorepo.

Requirements

  • Node.js 20+
  • npm

Install

From the workspace root:

npm install

Build this package:

npm run build -w @enos5/enos-vue-default

Use In Another Project

Install the published package:

npm install @enos5/enos-vue-default

This package expects these peer dependencies in the consuming app:

  • vue
  • @inertiajs/vue3 (^2.0.0 or ^3.0.0)
  • @heroicons/vue
  • vue-i18n

Rich text support uses TinyMCE and is bundled as a regular dependency in this library. The component set mirrors the Jetstream package except for ApplicationLogo, AuthenticationCard, Banner, NavGroup, NavLink, NavMenu, and ResponsiveNavLink.

You can register everything globally:

import { createApp } from 'vue'
import App from './App.vue'
import { EnosVueDefault } from '@enos5/enos-vue-default'

createApp(App).use(EnosVueDefault).mount('#app')

Or import individual components:

import { Button, ColorPicker, TextInput } from '@enos5/enos-vue-default'

ColorPicker resolves its built-in UI labels through vue-i18n using the English copy as keys. If your app wants localized picker chrome, define translations for keys such as Color, Selected color, Pick color from screen, Hue, Opacity, Hex value, Saturation and brightness for {color}, and Rainbow color area for {color}.

DateInput and DateRangeInput default to English locale behavior. Pass locale to override that, and for native browser date fields remember the final picker UI is still browser-controlled, with lang used as the locale hint.

Styles are loaded automatically when you import the package entrypoint, so consumers do not have to remember a separate CSS import.

If a consuming app wants earlier stylesheet loading during npm run dev, it can opt into the stable stylesheet entry explicitly:

import '@enos5/enos-vue-default/styles.css'

That explicit import is optional. It mainly improves dev-mode first paint and avoids importing from dist directly.

Publish To npm

Before publishing, build the package and verify the tarball:

npm run build -w @enos5/enos-vue-default
npm pack --dry-run -w packages/default

Then bump the version in packages/default/package.json, commit the change, and publish the workspace:

npm publish -w packages/default --access public

The first public release of this package needs --access public. After the package exists on npm, subsequent publishes can use the same command.