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

vue-hyper

v1.0.2

Published

Prototyping extremely dynamic interfaces. Programming html without directly using html

Readme

Vue-hyper

GitHub stars

Prototyping extremely dynamic interfaces. Programming html without directly using html

Install

# Using npm
$ npm install --save vue-hyper

# Using yarn
$ yarn add vue-hyper

Import

import Vue from 'vue'
import VueHyper from 'vue-hyper'

import Schema from './schema'

new Vue({
  el: '#app',
  name: 'hello',
  data () {
    return {
      schema: Schema
    }
  },
  template: '<VueHyper :schema="schema"/>',
  components: { VueHyper }
})

Schema

The scheme is a direct bridge that leads directly to the creation of native components of vues. Therefore, properties follow the style of VueJS names, such as click, change, input... The same applies to attributes: title, class, placeholder, value, innerHtml...

// filename: schema.js
// dir: examples/schema.js

module.exports = {
  root: {
    type: 'form',
    method: 'post'
  },
  name: {
    type: 'input',
    properties: {
      title: 'Name',
      class: 'form-control',
      tooltip: 'Input your first name',
      value: 'Julian',
      innerHtml: 'hello',
      placeholder: ''
    },
    events: {
      change: function (data) {
        console.log('Element changed to', data.target.value)
      },
      click: function (data) {
        console.log('Element clicked ', data)
      },
      input: function (data) {
        console.log('Pressed input', data.target.value)
      },
      keypress: function (data) {
        console.log('Pressed key', data.key, data.keyCode)
      }
    }
  },
  lastname: {
    type: 'input',
    properties: {
      title: 'lastname',
      tooltip: 'Input your first lastname',
      value: 'David'
    },
    events: {
      input: function (data) {
        console.log('Element changed to', data.target.value)
      }
    }
  },
  description: {
    type: 'input',
    properties: {
      title: 'biografy',
      tooltip: 'Here your text',
      placeholder: 'Text'
    },
    events: {
      input: function (data) {
        console.log('Element changed to', data.target.value)
      }
    }
  },
  genre: {
    type: 'select',
    properties: {
      title: 'genre',
      tooltip: 'Input your genre',
      value: ['M', 'F', 'Other']
    },
    events: {
      change: function (value) {
        console.log('Element genre changed to ', value.target.value)
      },
      click: function (value) {
        console.log('Element genre clicked ', value)
      }
    }
  }
}

See example schema.js

The rendered elements look like this:

CURRENTLY RECORDING

Events

| Prop | Description | | --------------- | ------------- | | click | Custom class to add to the component | | change | Custom url that the component will load | | input | Custom text |

See full list of events

Development, Build Setup

# install dependencies
npm install

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

# build for production with minification
npm run build

# build for production and view the bundle analyzer report
npm run build --report

# run unit tests
npm run unit

# run e2e tests
npm run e2e

# run all tests
npm test

Contributing

License

MIT @juliandavidmr