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

@xyziovue/design-system

v0.5.7

Published

xyz.io Vue Design System

Readme

xyz.io Vue Design System (xyziovue-design-system)

Installation

npm install @xyziovue/design-system --save

Overview

The Design System was created to provide easy and harmonious development of the UI of the customer application and modules. It work will ultimately resemble Vue Storefront or AWS Amplify Framework.

Quasar was used as UI framework.
Stylus was preferred as CSS preprocessor.

Components

DSHome

The Home component is a wrapper for pages that the login user can access. The pages to be accessed should be placed under Home route nested in the routes configuration.

{
  "home": {
    "name": "",
    "component": "views/DSHome",
    "meta": { "authenticated": true },
    "children": {
      "default-home-view": {
        "path": "",
        "name": "home",
        "redirect": { "name": "dashboard" }
      },
      "dashboard": {
        "path": "dashboard",
        "component": "views/Dashboard"
      }
    }
  }
}

DSLayout

The DSLayout component based on QLayout contains the elements that wrap application's content:

  • AppBar: Application bar shown on top of the page - can be overriden using the header slot
  • SideNav : A left side navigation panel (which is shown alongside page content on wide screens) - can be overriden using the left slot
  • RightPanel : A right side panel (which can be shown alongside page content on wide screens) - can be overriden using the right slot
  • TabBar: A navigation with QTabs
  • Fab: An action button based on a Quasar Floating Action Button at the bottom right corner of the page
  • SearchBar: a global search bar
  • Page Content: The embedded content of the page

The DSLayout component is usually wrapped using the Home component that simply load it depending on the authentication state of the user.

Some layout components are fixed for the entire application lifecycle. The application developer can customize using the layout configuration in config folder.

Forms

The Form is a generic form component capable of building HTML forms from of a JSON Schema. Moreover Form validates that the data is conformed to the schema using AJV validator.

A schema must have the following convention:

  • $id: Specifying the id of the schema. It is mainly used by AJV to cache the schema.
  • title: Specifying the title of the form. It is used by the Editors.
  • description: Providing a brief description of the usage of the schema
  • type: Must be object
  • properties: Define the list of the fields of the form. To each object is assigned a field. The name of the field is the name of the object and the properties are used to provide the characteristics of the field. A field sub-object provides the UI characteristic to assign to the field: the component to be used for the rendering as well as the properties to apply to this component.
  • required: To define the required fields. You must specify the name of the fields.

License

Licensed under the MIT license.