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

get-proxy-settings

v0.1.13

Published

Retrieve proxy settings specified by the system

Downloads

15,040

Readme

Note: This project is not actively maintained. If some issues come up we'll look into fixing them but new features will most likely not make it.

System Proxy

Build Status npm version

This library support

  • Reading proxy settings from the HTTP_PROXY or HTTPS_PROXY environment variables
  • Reading proxy settings from the HTTP_PROXY or HTTPS_PROXY node configuration
  • Retrieving the settings from the internet settings on Windows in the registry
  • Validating the connection and asking for credentials if needed
  • Note that it doesn't support every proxy system. If you are using electron it is recommended to use electron/chromium built in proxy support which is much more advanced.

Install

npm install --save get-proxy-settings

Usage

Import

// With named import
import { getProxySettings, getAndTestProxySettings } from "get-proxy-settings";

// Or with commonjs
const { getProxySettings, getAndTestProxySettings } = require("get-proxy-settings");

Use


async function basic() {
    const proxy = await getProxySettings();
    console.log("proxy", proxy.http, proxy.https);
}

// Get and validate the proxy settings
async function withValidation() {
    async function login() {
        // Do any async operation to retrieve the username and password of the user(prompt?)
        return {username: "abc", password: "123"}
    }

    const proxy = await getAndTestProxySettings(login);
    console.log("proxy", proxy.http, proxy.https);
}

Config

Update the test url (Which url is used to validate the proxy)

import { defaults } from "get-proxy-settings";

defaults.testUrl = "https://example.com";

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.

Credits

  • Timothee Guerin
  • Adar Zandberg from the CxSCA AppSec team at Checkmarx. (Finding Command injection vulnerability)