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

@qikkeronline/qikker-ui

v0.7.0

Published

<p align="center"><img src="https://qikker-assets.s3.eu-central-1.amazonaws.com/images/Qikker_logo_black.png" width="400"></p>

Downloads

249

Readme

Qikker UI

A collection of basic vue components for use with the qikker frontend boilerplate.

Getting Started

Install qikker-ui via npm or yarn.

# Via NPM.
$ npm install @qikkeronline/qikker-ui

# Via Yarn.
$ yarn add @qikkeronline/qikker-ui

By design, Qikker UI doesn't ship with pre-built files, so you must compile the code in your project. Please follow the following instruction to set up your build system.

Qikker UI comes with a config file qikker-ui.scss, this file is created post install at the root of your project. You can change global variables here.

To compile Vue Components, you must have appropriate build settings. For example, in Nuxt.js, you should define the following setting at nuxt.config.js, this allows using named exports for the components. (In vue projects this does not seem to be needed. TODO examine this)

export default {
  // ...

  build: {
    transpile: ['@qikkeronline/qikker-ui'],
  },

  // ...
}

To begin using the components, import them from the qikker-ui package.

<template>
  <div>
    <QInput label="Label" placeholder="Placeholder" />
  </div>
</template>

<script>
import { QInput } from '@qikkeronline/qikker-ui'

export default {
  components: {
    QInput
  }
}
</script>

You can also import them as global components.

Example usage with NuxtJS plugin

// qikker-ui.js
import Vue from 'vue'
import { QIcon, QSvg, QInput, QCheckbox, QRadio, QToggle } from '@qikkeronline/qikker-ui'

Vue.component('q-icon', QIcon) // * see notes below for alternative registration
Vue.component('q-svg', QSvg)
Vue.component('q-input', QInput)
Vue.component('q-checkbox', QCheckbox)
Vue.component('q-radio', QRadio)
Vue.component('q-toggle', QToggle)

Important Notes

It is suggested that you import at least these components as global: Qicon, Qsvg. For the rest it depends on your project.

QIcon is set to stroke: currentColor by default. If you want to globally set it to fill: currentColor you can do so by registering it like this instead in the qikker-ui.js:

Vue.use(QIcon, { isFill: true })

Build Setup

# install dependencies
$ npm install

# serve with hot reload at localhost:8080
$ npm run serve

# build for production
$ npm run build


For detailed explanation on how things work, checkout [Nuxt.js docs](https://nuxtjs.org).