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

electron-publisher-azure

v0.0.6

Published

Publish your release to azure storage blob using electron-builder

Downloads

38

Readme

How to Use

Install packages

Install the electron-publisher-azure by npm or yarn.

Config Package JSON

In your packages.json, add this to your publish list:

{
    "build": {
        "publish": [
            {
                "provider": "custom", // have to be custom
                "providerName": "azure",
                "container": "releases", // can be any container in your azure blob, default is release
                "account": "accountName" // your azure storage account name
            }
        ]
    }
}

Create a Javascript File to Redirect

In your build dir, add a file named electron-publisher-custom.js with the content

module.exports = require('electron-publisher-azure').default;

Where is your build dir? In package.json, build.directories.output is the build dir

Config your Publish Environment

To actual publish the release to azure, you have to have someting as credential. These things are secret. Don't put them in public space.

You can either have accountKey, token of azure storage account to use as credential.

For accountKey, you can place it inside the environment variable named AZURE_STORAGE_ACCOUNT_KEY. Or, you can put it in package.json like:

{
    "provider": "custom", // have to be custom
    "providerName": "azure",
    "accountKey": "Your account key",
    "container": "releases", // can be any container in your azure blob, default is release
    "account": "accountName" // your azure storage account name
}

For token, you can place it inside the environment variable named AZURE_STORAGE_ACCOUNT_TOKEN. Or, you can put it in package.json like:

{
    "provider": "custom", // have to be custom
    "providerName": "azure",
    "accountKey": "Your account token",
    "container": "releases", // can be any container in your azure blob, default is release
    "account": "accountName" // your azure storage account name
}