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

@kano/kit-app-shell-windows-store

v0.0.3-alpha.90

Published

Builds an .appx to be published on the Windows Store

Downloads

21

Readme

KASH Windows Store

Builds an .appx to be published on the Windows Store

Setup

To build applications for the Windows Store, you will need a developer certificate. Each certificate is tied to a publisher. If you are building an app locally and don't intend to publish it as is, you can use any publisher. e.g. CN=Myself. If you are preparing a Store Submission, see the Preparing a submission chapter.

Now run kash configure windows-store, choose Create a new certificate and input your choosen Publisher. This will create a save a certificate for that publisher and will be used when building the .appx package.

In your project's config files add the following:

{
    "WINDOWS_STORE": {
        "PACKAGE_NAME": "<Package name>",
        "PACKAGE_DISPLAY_NAME": "<Display name>",
        "PUBLISHER": "<Publisher>",
        "PUBLISHER_DISPLAY_NAME": "<Publisher Display Name>"
    }
}

This information can be found in the App identity section of the Microsoft partner center. For a local test, you can choose these fields, but make sure your generated certificate uses the same publisher as the one defined here.

Preparing a submission

Login the partner center at https://partner.microsoft.com/en-us/dashboard/windows/overview, navigate to your app in Overview > [App] > App Managment > App identity

App identity

You will find here all the info to fill in the fields in your project's config files

TODO

  • Generate All icons, some are missing
  • Add get-publisher key that retrieves the publisher ID for a given app