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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@apiida/vue-components

v16.13.14

Published

The Vue Components is the component library for the API Control Plane and contains components built with Vue 3 and Typescript. It implements the Exosphere and therefore follows this design system.

Downloads

4,370

Readme

API Control Plane - Vue Components

https://apiida.com/

A Vue 3 component library.

When you are starting a new prototype you want to be able to develop features fast. We created this component library as a way for us to build products quickly without having to deal with complicated packages and a huge bundle sizes.

This library is built, maintained, tested and documented with Storybook.

https://www.npmjs.com/package/@apiida/vue-components

Merge conflicts / version conflicts

The branches "master" and "fallback" are published on npm. Npm always takes the highest version number, the branch doesn't matter. The "master" should always contain the highest version (see examples below). If there are problems with the versions during parallel development:

  1. In case of a merge conflict you have to check if there are breaking changes in the other frontends. If so, the merge must be aborted and the fallback must be used.

  2. There a new version number is set.

  3. With this new version number you can continue to work in the other frontends.

  4. Set the version number in the frontend:

    npm install @apiida/[email protected]
  5. Discuss with the team and merge the version number.

    // local version of vue-components
    npm list @apiida/vue-components
       
    // Highest verion in npm (online)
    npm view @apiida/vue-components

Usage

You can import the available components like so.

import { Button } from '@apiida/vue-components'

Links

https://storybook.js.org/docs/vue/get-started/introduction

Contribute

Guideline

Each component should have at least one story and one test. The GitHub action takes over the automatic deployment of the library to npm. However, the version number must be changed for this.

Version

The version is made up as follows.

BreakingChange.CreateOrUpdateComponent.BugFix (1.2.598)

How to contribute manual

Pull the Projekt

git pull https://github.com/apiida/vue-components

Start Storybook

start-storybook -p 6006

Create some cool components, stories and tests!

Components

Styles

Because VITE bundles all css files when building the library in a style.css and you may not want to have all in your project. You can also pack your styles in a separate file (css). This must then be included in the Storie and in the project as well.