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

@cycjimmy/hello-vue-lib

v2.0.0

Published

hello vue lib

Readme

hello-vue-lib

NPM latest version NPM next version NPM alpha version NPM beta version NPM bundle size npm download jsdelivr Test CI status Coverage status libraries dependency status libraries sourcerank Release date semantic-release npm license

An ESM-only Vue 3 component library template with automatic test, release and maintenance workflows. Demo

Requirements

  • Node.js ^22.22.2 || ^24.15.0 || >=26.0.0 for development (the build scripts run through Node's native TypeScript stripping, and the lint/test toolchain needs the same range).
  • An ESM environment. The package ships a single import entry: there is no CommonJS and no UMD bundle.
  • Vue ^3.5.0 as a peer dependency. The generated declarations rely on the DefineComponent type shape introduced in Vue 3.5.

Install

npm install @cycjimmy/hello-vue-lib

Usage

The style sheet is a separate file, so it has to be imported explicitly:

import HelloWorld from '@cycjimmy/hello-vue-lib'
import '@cycjimmy/hello-vue-lib/style.css'

A named export is available as well:

import { HelloWorld } from '@cycjimmy/hello-vue-lib'

The component accepts one required prop, msg: string.

Breaking changes in v2

  • CommonJS and UMD bundles were removed. exports only exposes an import entry, and main / module point at the same ESM file.
  • Styles are emitted to dist/index.css and must be imported through @cycjimmy/hello-vue-lib/style.css.
  • Type declarations are generated into dist/; the hand-written types/index.d.ts placeholder was removed.
  • vue is a peer dependency (^3.5.0) instead of a regular dependency, so the published manifest constrains the Vue version the declarations target.
  • Node.js ^22.22.2 || ^24.15.0 || >=26.0.0 is required to build, test and lint.
  • The toolchain moved to Vite 8, Vitest 5, TypeScript 6, ESLint 10 with @antfu/eslint-config (Prettier was removed) and stylelint for SCSS.

Packages

  • dist/index.js: ESM entry (vue stays external).
  • dist/index.css: the component styles.
  • dist/index.d.ts: the generated declarations.

Development

npm install
npm run dev

| Script | Description | | --- | --- | | npm run dev | Start the Vite dev server for the demo. | | npm run build | Build the ESM entry, the style sheet and the declarations. | | npm run build:deployment | Build the demo into .publish/ for GitHub Pages. | | npm test | Run the unit tests once. | | npm run test:watch | Run the unit tests in watch mode. | | npm run test:coverage | Run the unit tests with coverage (lcov for Coveralls). | | npm run test:types | Check that the packaged declarations resolve for a NodeNext ESM consumer (run it after npm run package). | | npm run type-check | Type check the library, the demo and the build configs. | | npm run lint | Lint JavaScript/TypeScript/Vue with ESLint. | | npm run lint:fix | Lint and auto-fix with ESLint. | | npm run lint:style | Lint the SCSS in src/ with stylelint. | | npm run lint:style:fix | Lint and auto-fix the SCSS with stylelint. | | npm run package | Build and prepare the publishable .release/ directory. |

Release

Commits follow the Conventional Commits specification. Pushing to main makes semantic-release bump the version, update docs/CHANGELOG.md, publish to npm through trusted publishing (OIDC) and to the GitHub Package Registry, and push the vN branch.

Issues are triaged automatically: a report without enough information is labelled needs-info and closed after 7 days without a reply, and issues without activity are marked stale after half a year and closed two weeks later.

License

MIT