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

docker-host-url

v0.2.0

Published

URL host resolver for Docker applications

Downloads

1,891

Readme

Docker Host URL

URL host resolver for Docker applications

This library provides URL resolving helpers that resolve URLs that contain the domain host.docker.internal. On Mac and Linux hosts this resolves differently, and this library is designed to handle both types of hosts.

You can pass a variety of values to the resolution functions that will detect and replace host.docker.internal:

  • HTTP/HTTPS URLs: http://host.docker.internal/some/page
  • Other protocols: ftp://host.docker.internal/dir
  • Just the domain: host.docker.internal
  • URLs with credentials: mysql://user:[email protected]:3306/dbname

Installation

Install this library as a dependency to use in any environment:

npm install docker-host-url --save

Usage

Consider an internal application URL like http://host.docker.internal:8080/api/resource - when being requested from inside a Docker application this may not resolve correctly. Using this library, a call like the following would be able to resolve it to an IP address:

import { resolveURL } from "docker-host-url";

// ...

const url = await resolveURL("http://host.docker.internal:8080/api/resource");
// url = http://172.17.0.1:8080/api/resource

Whereas URLs not containing host.docker.internal will not be changed:

const url = await resolveURL("https://test.com:8080/api/resource");
// url = https://test.com:8080/api/resource

This difference allows you to continue using this library in production as it will have no effect on other domains.

Sync usage

This library makes async calls to resolve the host.docker.internal domain, so sync use is not possible without first performing some async call. In situations where you're able to run some async task before the application properly starts, you can call the init function to resolve the domain early, allowing you to later call resolveURLSync synchronously.