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

@zoovu/runner-web-design-base

v4.60.0

Published

Runner Base Components

Downloads

9

Readme

Runner Web Design Base Components

This projects delivers:

  • Library of reusable UI components that allow to build browser GUI for Runner Runtime (codezillas/runner-runtime>),
  • Zoovu Web Design CLI - commandline interface for building production-ready Web Designs according to the contract that is expected by integration code.

Overview

This project aims to deliver as reusable as possible library of UI components that can be used to assemble Web Designs of different flavours and UX.

Web Design class is defined by WebDesignDefinition:

export interface WebDesignDefinition {
    webDesignName: string;
    AdvisorView: Component<any>;
    componentRegistry: ComponentRegistry;
    styleRegistry: StyleRegistry;
    rootContainerStyle?: ComponentStyleDefinition;
    plugins?: AdvisorWebDesignPlugin[];
}

and can be created using factory from Runner Browser API (see: codezillas/runner-runtime>):

const WebDesignClass = CreateWebDesignClass({
    webDesignName: "bikes-assistant",
    AdvisorView: componentRegistry.getComponent("AdvisorView"),
    componentRegistry,
    styleRegistry
});

(full example can be seen for example in theme-1 source code located in codezillas/runner-themes>)

As we can see from those two snippets, minimal set of data, that we need in order to create our own Web Design, is:

  • Web Design name
  • AdvisorView, that is root vue component that will be mounted to DOM. AdvisorView determines Vue instance as in https://vuejs.org/v2/guide/instance.html
  • Components Registry - as Runner Browser API provides number of custom built annotations and even supports injecting different child components in runtime, it is necessary to allow framework to scan all Vue components that are being used by the Web Design
  • Styles Registry - preferred way of styling components is to use JSS (https://cssinjs.org) attached to each component. JSS was chosen because allows to drive styling through JSON configuration, it allow componentization, re-usability and styles isolation. Styles Registry defines which Vue component should use which JSS.

Guide

If you would like contribute to the project please read through our guide.

Table of contents: