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

@microsoft/vscode-container-client

v0.1.2

Published

Extensibility model for implementing container runtime providers (shared by VS and VS Code)

Downloads

145

Readme

vscode-container-client

Overview

This package adds support for various Docker container runtimes, abstracting away the details of the runtime and the way it is called, to provide a common interface for any Docker runtime (e.g. Docker in WSL, Docker Engine, Docker Desktop, etc.).

Usage

Each of the runtime clients provide a command line to execute and a function to parse the output, for each relevant operation. These items are combined into a CommandResponse object. In addition, many helpful utility classes are provided, for building command lines, running the commands, and a handful of other scenarios.

Example

Here is an example for inspecting a container that uses the ShellStreamCommandRunnerFactory provided by this library:

// Build the necessary objects
const dockerClient = new DockerClient();
const factory = new ShellStreamCommandRunnerFactory({
    // Many options are supported
});
const runCommand = factory.getCommandRunner();

// Get the command response, and run it in the shell command runner
const inspectionResults: InspectContainersItem[] | undefined = await runCommand(
    dockerClient.inspectContainers({ containers: ['myContainerName'] })
);

// Get the first item in the results
const result: InspectContainersItem | undefined = inspectionResults?.[0];

// If an item was found, output some information about it
if (result) {
    console.log(`${result.name} is running image ${result.imageName} (${result.imageId})`);
}

License

MIT

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.opensource.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., status check, 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.

Microsoft Open Source Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct.

Resources: