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

@nullkeys/electron-vue

v2.0.1

Published

Vue.js extension for Electron applications

Downloads

3

Readme

electron-vue

Vue.js extension for Electron applications

Gitter chat

Installation

npm install @nullkeys/electron-vue

Getting Started

Since ElectronVue simply extends Vue.js with some integration points for building Electron applications, please checkout those projects to help get started. This document tries to focus on things that have been added by ElectronVue.

Template Rendering

Dead simple example

This is about as simple as it gets when creating a vue. This example simply associates an ElectronVue instance with an element and renders a bit of data into the output.

new ElectronVue({
    el: '#app',
    template: '<div>{{ message }}</div>',
    data: {
        message: 'This is a template from a string.'
    }
});
<!-- input element -->
<div id="app"></div>

<!-- rendered output -->
<div>This is a template from a string.</div>

External template example

In addition to defining templates as inline strings, you can reference external html files as templates too. There isn't anything special about the html file in this example, it's just good ol' html. The only requirement is that the file only has one root element.

new ElectronVue({
    el: '#app',
    template: 'app-template.html'
});
<!-- example app-template.html -->
<div>This is a template file.</div>
<!-- input element -->
<div id="app"></div>

<!-- rendered output -->
<div>This is a template file.</div>

Component Registration

You can also register components too. Here's an example building on ElectronVue's ability to reference external templates. In this example, a component called app-component is registered where it produces some content based on an inline template string.

Note: Only local registration is currently supported.

new ElectronVue({
    el: '#app',
    template: 'app-template.html',
    components: {
        'app-component': {
            template: '<div>This is my template.</div>'
        }
    }
});
<!-- example app-template.html -->
<app-component></app-component>
<!-- input element -->
<div id="app"></div>

<!-- rendered output -->
<div>This is my template.</div>

Electron Messages

ElectronVue attempts to make it easy to pass messages between your Vue in the renderer process and the main process of an Electron application. Take a look at the Electron documentation to see how this works under the hood. Here's an example of how it works with an ElectronVue.

// renderer process
const {ipcRenderer} = require('electron');

new ElectronVue({
    el: '#app',
    template: 'app-template.html',
    ipc: {
        pingPong(event, arg) {
            console.log(arg) // prints 'pong'
        }
    }
});

ipcRenderer.send('ping-pong');
// main process
const {ipcMain} = require('electron');

ipcMain.on('ping-pong', (event) => {
    event.sender.send('ping-pong', 'pong');
});

In the above example, you'll notice that the registered event name on the ipc object is the spinal-case representation of the function name. ElectronVue attempts to convert functions within this object during the registration process. If this doesn't work for you, then you can always fallback to the following pattern for a specific event which lets you explicitly define your event name. It's possible to use both patterns within the same ipc object.

new ElectronVue({
    ipc: {
        tableTennis: {
            channel: 'ping-pong',
            method(event, arg) {
                console.log(arg) // prints 'pong'
            }
        }
    }
});

Running Tests

npm test