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

windows-admin-center-cli

v0.1.29

Published

Cli for creating a new Windows Admin Center extension.

Downloads

24

Readme

Windows Admin Center CLI

The Windows Admin Center CLI was created to simplify the process of generating new tools for the platform.

Usage

There is only one command for the CLI, "Create". In order to create a new tool, type the following:

wac create --company <Your Company Name> --tool<Your Tool Name>

For instance, when creating a tool called Foo for Microsoft, my command would be:

wac create --company Microsoft --tool Foo

You can also use the CLI to create solution extensions as well:

wac create --company Microsoft --tool Foo --solution MySolution

In addition to creating extensions, you can specify which version of the SDK you want to utilize. There are 5 rings for you to choose from:

  • legacy (the GA release behind the current, 2 updates per year)
  • latest (the most current GA release, 2 updates per year)
  • insider (build most recently released to Insiders. Updates monthly)
  • next (current dev build. Updates frequently, up to weekly)
  • experimental (Updates frequently, up to daily)

In order to specify which SDK version you want to use, add the version tag to the create command:

wac create --company Microsoft --tool Foo --version insider

Default value is latest.

Get started with the SDK

Getting started with Windows Admin Center development is easy! Follow along with step-by-step directions to prepare your environment, and learn more about writing and publishing extensions at our documentation site.

Don't have Windows Admin Center installed yet? Download Windows Admin Center.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.