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

goblin-builder

v3.7.15

Published

Electron and Debian builder

Downloads

578

Readme

Goblin Builder

Electron

This goblin provides a versatil and easy way in order to produce releases for all usual platforms. A release is based on an "application". It means that with Westeros you can build more than one application just by providing the right definition to the electronify.build command.

Application's definitions

The definitions are located in the app/ directory of Westeros. The directory's name should matchs the name provided in the app.json file.

The appCompany and appId entries should be as simple as possible (only /[a-z]+/) because it's used for creating the settings directories in the $HOME (OS user).

The xcraft section is very useful for providing settings to the xcraft modules, especially xcraft-core-host. This module is used for bootstrapping the first application.

Here an example:

{
  "xcraft": {
    "xcraft-core-host": {
      "mainQuest": "myapp.boot",
      "secondaryQuest": "myapp.start"
    }
  }
}

The mainQuest is executed before the ready state of Electron. It should be used for handling special parameters (on command line) for example and all other stuffs which are not depending of Electron.

The secondaryQuest is called when Electron is ready. Then it's possible to use goblins like goblin-wm in order to create windows.

The values pass to the quests are commands without arguments.

Building

To build a release, you have to send the electronify.build command with the application's name (diectory's name in app/) and the absolute output path. Note that cross-building is not supported. The output is always using the same platform that the one used by Westeros.

In some cases it's possible to build Windows releases on Linux host but it's an exception and it's not handled here.