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

@soundworks/electron

v1.0.0-alpha.0

Published

Electron wrapper for soundworks applications

Downloads

3

Readme

soundworks | electron

Minimal wrapper to build Electron applications from existing soundworks applications. Derived from https://github.com/szwacz/electron-boilerplate.

Install

npm install --save-dev @soundworks/electron

create an .electron.cjs file at the root of your application with the following informations:

const pkg = require('./package.json');

const config = {
  productName: "My App",
  // keep versionning synchronized with the current repo
  buildVersion: pkg.version,
  appId: 'fr.ircam.ismm.my-app',
  icon: './media/icon.png',
  // to be fixed confirmed...
  publish: [
    {
      provider: 'github',
      owner: 'ircam-ismm',
      reop: 'como-vox',
    }
  ],
  // list of files or directories that we don't want to include in the binary
  // by default the whole application except the .git directory is copied
  exclude: [
    'resources',
    // ...
  ]
  // @todos
  // icons, etc.
}

module.exports = config;

Make sure you have the following script in your package.json, this command is used by @soundworks/electron to watch and build the soundworks project in dev mode.

"watch-build": "soundworks-build -b -w",

Commands

soundworks-electron init (@todo)

  • generate the .electron.js file
  • add the npm script command in package.json if not exists
  • add a default icon
  • add electron-build directory to .gitignore

soundworks-electron dev

  • run electron in dev mode, the host soundworks application is watch and transpiled
  • be aware that if you modify server side files, you will have to relaunch

soundworks-electron build

  • build the application

Release

Mac

To build a release for Mac, you should have a valid Certificate installed on your machine

Trouble shooting:

  • check codesign
codesign --verify --deep --verbose ./electron-build/mac/CoMo\ Vox.app/
  • check notarization
spctl -a -t exec -vvv electron-build/mac/CoMo\ Vox.app/

output

# on the machine where the build has been done
spctl -a -t exec -v /path/to/notarised.app
source=Notarized Developer ID

# on another machine (not sure of this one)
spctl -a -t exec -v /path/to/not_notarised.app
source=Developer ID

These checks should be done both on the dev machine and on another one after download to check gatekeeper behavior.

Auto-update

auto update seems to be automatically done from .git/config infos https://github.com/iffy/electron-updater-example

to be tested

Todos

  • build for windows (and linux ?)
  • automate releases

License

BSD-3-Clause