sindresorhus / ipify

Get your public IP address

ipify

Get your public IP address

Using the Ipify API or a custom Ipify instance.

Install

npm install ipify

Usage

import ipify from 'ipify';

console.log(await ipify());
//=> '2001:0db8:85a3:0000:0000:8a2e:0370:7334'

API

ipify(options?)

Returns a Promise<string> with an IP address.

options

Type: object

useIPv6

Type: boolean
Default: true

Use the IPv6 API endpoint. The IPv6 endpoint will return an IPv6 address if available, IPv4 address otherwise.

Setting the endpoint option will override this.

import ipify from 'ipify';

console.log(await ipify({useIPv6: false}));
//=> '82.142.31.236'

endpoint

Type: string
Default: 'https://api6.ipify.org'

Custom API endpoint.

FAQ

How is this different from public-ip?

This package only targets the Ipify service, while public-ip targets multiple services, is faster, and more resilient. Unless you run your own Ipify instance, you probably want public-ip instead.

Related

• ipify-cli - CLI for this module
• internal-ip - Get your internal IPv4 or IPv6 address

ipify's Issues

Allow parsing of `API_KEY` to get more info from geo.ipify.org/api [Suggestion]

Thank you for this useful API.
I was working with it and wanted to use the geo.ipify api to get more details like ISP, since ipify api does does not support this out of the box unless you use the geo.ipify api and create an apikey to add to the endpoint url.

• If possible, it would be cool to add the geo.ipify api endpint as well to the list of constants and call that if the user provides a valid api key to the ipify() function; e.g ipify(API_KEY).
• If this would be useful, if need be I can make this addition myself if contributions are accepted. I did not see a contribution guild file so I decided to raise an issue to ask the team.

Cheers.

java.net.ConnectException

java.net.ConnectException: Failed to connect to api.ipify.org/0.0.0.0:443

Actually I got this exception while using a VPN. Please check this issue.

Awesome!

I'm the guy who runs ipify -- just saw this npm package -- very cool! Thanks for writing it <333

Support the IPv6 endpoint

https://www.ipify.org/

I think we could do a breaking change and return IPv6 by default and fall back to IPv4. Need to check what the IPv6 endpoint returns when IPv6 is not supported. Could then have an option to pick either: auto, ipv6, ipv4.

Not sure how this fits with the endpoint option though.

Thoughts?

---

IssueHunt Summary

stroncium has been rewarded.

Sponsors (Total: $40.00)

• issuehunt ($40.00)

Tips

• Checkout the Issuehunt explorer to discover more funded issues.
• Need some help from other developers? Add your repositories on IssueHunt to raise funds.

Cannot find module 'object-assign'

Hey, great work! Just installed it and run the simple example you have on your page and got this error.
I am assuming this is a dependency that isn't listed?

module.js:338
throw err;
^
Error: Cannot find module 'object-assign'
at Function.Module._resolveFilename (module.js:336:15)
at Function.Module._load (module.js:278:25)
at Module.require (module.js:365:17)
at require (module.js:384:17)
at Object. (/ipify/node_modules/got/index.js:8:20)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Module.require (module.js:365:17)

local ip

it would be awesome if this tool could also give you your local IP address with a tag like -l. Just a suggestion

upgrade builds with 0.10.0 < engines < lts/boron

Test the library for node argon + boron

Module not found error, Can't resolve dns when using ipify

Am getting a whole lot of errors when importing ipify
`
Module not found: Error: Can't resolve 'dns' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\cacheable-lookup\source'
WARNING in ./node_modules/keyv/src/index.js 26:16-42
Critical dependency: the request of a dependency is an expression

WARNING in [eslint]
src\components\ip.jsx
Line 2:8: 'ipify' is defined but never used no-unused-vars

ERROR in ./node_modules/cacheable-lookup/source/index.js 11:4-18
Module not found: Error: Can't resolve 'dns' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\cacheable-lookup\source'

ERROR in ./node_modules/cacheable-lookup/source/index.js 15:4-19
Module not found: Error: Can't resolve 'util' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\cacheable-lookup\source'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "util": require.resolve("util/") }'
- install 'util'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "util": false }

ERROR in ./node_modules/cacheable-lookup/source/index.js 17:11-24
Module not found: Error: Can't resolve 'os' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\cacheable-lookup\source'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "os": require.resolve("os-browserify/browser") }'
- install 'os-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "os": false }

ERROR in ./node_modules/cacheable-request/node_modules/get-stream/buffer-stream.js 5:4-21
Module not found: Error: Can't resolve 'stream' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\cacheable-request\node_modules\get-stream'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
- install 'stream-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "stream": false }

ERROR in ./node_modules/cacheable-request/node_modules/get-stream/index.js 5:4-21
Module not found: Error: Can't resolve 'buffer' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\cacheable-request\node_modules\get-stream'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "buffer": require.resolve("buffer/") }'
- install 'buffer'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "buffer": false }

ERROR in ./node_modules/cacheable-request/src/index.js 5:15-29
Module not found: Error: Can't resolve 'url' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\cacheable-request\src'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "url": require.resolve("url/") }'
- install 'url'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "url": false }

ERROR in ./node_modules/clone-response/src/index.js 3:20-49
Module not found: Error: Can't resolve 'stream' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\clone-response\src'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
- install 'stream-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "stream": false }

ERROR in ./node_modules/compress-brotli/src/index.js 5:4-19
Module not found: Error: Can't resolve 'util' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\compress-brotli\src'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "util": require.resolve("util/") }'
- install 'util'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "util": false }

ERROR in ./node_modules/compress-brotli/src/index.js 9:13-28
Module not found: Error: Can't resolve 'zlib' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\compress-brotli\src'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "zlib": require.resolve("browserify-zlib") }'
- install 'browserify-zlib'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "zlib": false }

ERROR in ./node_modules/decompress-response/index.js 6:4-21
Module not found: Error: Can't resolve 'stream' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\decompress-response'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
- install 'stream-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "stream": false }

ERROR in ./node_modules/decompress-response/index.js 8:13-28
Module not found: Error: Can't resolve 'zlib' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\decompress-response'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "zlib": require.resolve("browserify-zlib") }'
- install 'browserify-zlib'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "zlib": false }

ERROR in ./node_modules/get-stream/buffer-stream.js 5:4-21
Module not found: Error: Can't resolve 'stream' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\get-stream'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
- install 'stream-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "stream": false }

ERROR in ./node_modules/get-stream/index.js 5:4-21
Module not found: Error: Can't resolve 'buffer' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\get-stream'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "buffer": require.resolve("buffer/") }'
- install 'buffer'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "buffer": false }

ERROR in ./node_modules/get-stream/index.js 7:15-32
Module not found: Error: Can't resolve 'stream' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\get-stream'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
- install 'stream-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "stream": false }

ERROR in ./node_modules/get-stream/index.js 11:4-19
Module not found: Error: Can't resolve 'util' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\get-stream'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "util": require.resolve("util/") }'
- install 'util'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "util": false }

ERROR in ./node_modules/http2-wrapper/source/agent.js 6:4-18
Module not found: Error: Can't resolve 'url' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\http2-wrapper\source'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "url": require.resolve("url/") }'
- install 'url'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "url": false }

ERROR in ./node_modules/http2-wrapper/source/agent.js 10:12-26
Module not found: Error: Can't resolve 'tls' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\http2-wrapper\source'

ERROR in ./node_modules/http2-wrapper/source/agent.js 12:14-30
Module not found: Error: Can't resolve 'http2' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\http2-wrapper\source'

ERROR in ./node_modules/http2-wrapper/source/auto.js 7:4-18
Module not found: Error: Can't resolve 'url' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\http2-wrapper\source'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "url": require.resolve("url/") }'
- install 'url'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "url": false }

ERROR in ./node_modules/http2-wrapper/source/auto.js 9:13-28
Module not found: Error: Can't resolve 'http' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\http2-wrapper\source'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "http": require.resolve("stream-http") }'
- install 'stream-http'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "http": false }

ERROR in ./node_modules/http2-wrapper/source/auto.js 11:14-30
Module not found: Error: Can't resolve 'https' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\http2-wrapper\source'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "https": require.resolve("https-browserify") }'
- install 'https-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "https": false }

ERROR in ./node_modules/http2-wrapper/source/client-request.js 7:4-18
Module not found: Error: Can't resolve 'url' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\http2-wrapper\source'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "url": require.resolve("url/") }'
- install 'url'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "url": false }

ERROR in ./node_modules/http2-wrapper/source/client-request.js 9:14-30
Module not found: Error: Can't resolve 'http2' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\http2-wrapper\source'

ERROR in ./node_modules/http2-wrapper/source/client-request.js 13:4-21
Module not found: Error: Can't resolve 'stream' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\http2-wrapper\source'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
- install 'stream-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "stream": false }

ERROR in ./node_modules/http2-wrapper/source/incoming-message.js 5:4-21
Module not found: Error: Can't resolve 'stream' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\http2-wrapper\source'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
- install 'stream-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "stream": false }

ERROR in ./node_modules/http2-wrapper/source/index.js 3:14-30
Module not found: Error: Can't resolve 'http2' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\http2-wrapper\source'

ERROR in ./node_modules/http2-wrapper/source/proxies/h1-over-h2.js 3:12-26
Module not found: Error: Can't resolve 'tls' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\http2-wrapper\source\proxies'

ERROR in ./node_modules/http2-wrapper/source/proxies/h1-over-h2.js 5:13-28
Module not found: Error: Can't resolve 'http' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\http2-wrapper\source\proxies'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "http": require.resolve("stream-http") }'
- install 'stream-http'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "http": false }

ERROR in ./node_modules/http2-wrapper/source/proxies/h1-over-h2.js 7:14-30
Module not found: Error: Can't resolve 'https' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\http2-wrapper\source\proxies'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "https": require.resolve("https-browserify") }'
- install 'https-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "https": false }

ERROR in ./node_modules/http2-wrapper/source/proxies/h2-over-h1.js 3:13-28
Module not found: Error: Can't resolve 'http' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\http2-wrapper\source\proxies'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "http": require.resolve("stream-http") }'
- install 'stream-http'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "http": false }

ERROR in ./node_modules/http2-wrapper/source/proxies/h2-over-h1.js 5:14-30
Module not found: Error: Can't resolve 'https' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\http2-wrapper\source\proxies'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "https": require.resolve("https-browserify") }'
- install 'https-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "https": false }

ERROR in ./node_modules/http2-wrapper/source/proxies/initialize.js 6:4-18
Module not found: Error: Can't resolve 'url' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\http2-wrapper\source\proxies'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "url": require.resolve("url/") }'
- install 'url'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "url": false }

ERROR in ./node_modules/http2-wrapper/source/utils/calculate-server-name.js 5:4-18
Module not found: Error: Can't resolve 'net' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\http2-wrapper\source\utils'

ERROR in ./node_modules/http2-wrapper/source/utils/calculate-server-name.js 7:15-32
Module not found: Error: Can't resolve 'assert' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\http2-wrapper\source\utils'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "assert": require.resolve("assert/") }'
- install 'assert'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "assert": false }

ERROR in ./node_modules/http2-wrapper/source/utils/js-stream-socket.js 3:15-32
Module not found: Error: Can't resolve 'stream' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\http2-wrapper\source\utils'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
- install 'stream-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "stream": false }

ERROR in ./node_modules/http2-wrapper/source/utils/js-stream-socket.js 5:12-26
Module not found: Error: Can't resolve 'tls' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\http2-wrapper\source\utils'

ERROR in ./node_modules/resolve-alpn/index.js 3:12-26
Module not found: Error: Can't resolve 'tls' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\resolve-alpn'

ERROR in ./node_modules/responselike/src/index.js 3:17-43
Module not found: Error: Can't resolve 'stream' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules\responselike\src'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
- install 'stream-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "stream": false }

ERROR in ./node_modules/@szmarczak/http-timer/dist/source/index.js 2:0-29
Module not found: Error: Can't resolve 'util' in 'C:\Users\HP\cisco-starter-repo\sextant\node_modules@szmarczak\http-timer\dist\source'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "util": require.resolve("util/") }'
- install 'util'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "util": false }

ERROR in node:buffer
Module build failed: UnhandledSchemeError: Reading from "node:buffer" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.
at C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:832:25
at Hook.eval [as callAsync] (eval at create (C:\Users\HP\cisco-starter-repo\sextant\node_modules\tapable\lib\HookCodeFactory.js:33:10), :6:1)
at Object.processResource (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:829:8)
at processResource (C:\Users\HP\cisco-starter-repo\sextant\node_modules\loader-runner\lib\LoaderRunner.js:220:11)
at iteratePitchingLoaders (C:\Users\HP\cisco-starter-repo\sextant\node_modules\loader-runner\lib\LoaderRunner.js:171:10)
at runLoaders (C:\Users\HP\cisco-starter-repo\sextant\node_modules\loader-runner\lib\LoaderRunner.js:398:2)
at NormalModule._doBuild (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:819:3)
at NormalModule.build (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:963:15)
at C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\Compilation.js:1371:12
at NormalModule.needBuild (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:1253:32)

ERROR in node:events
Module build failed: UnhandledSchemeError: Reading from "node:events" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.
at C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:832:25
at Hook.eval [as callAsync] (eval at create (C:\Users\HP\cisco-starter-repo\sextant\node_modules\tapable\lib\HookCodeFactory.js:33:10), :6:1)
at Object.processResource (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:829:8)
at processResource (C:\Users\HP\cisco-starter-repo\sextant\node_modules\loader-runner\lib\LoaderRunner.js:220:11)
at iteratePitchingLoaders (C:\Users\HP\cisco-starter-repo\sextant\node_modules\loader-runner\lib\LoaderRunner.js:171:10)
at runLoaders (C:\Users\HP\cisco-starter-repo\sextant\node_modules\loader-runner\lib\LoaderRunner.js:398:2)
at NormalModule._doBuild (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:819:3)
at NormalModule.build (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:963:15)
at C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\Compilation.js:1371:12
at NormalModule.needBuild (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:1253:32)

ERROR in node:https
Module build failed: UnhandledSchemeError: Reading from "node:https" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.
at C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:832:25
at Hook.eval [as callAsync] (eval at create (C:\Users\HP\cisco-starter-repo\sextant\node_modules\tapable\lib\HookCodeFactory.js:33:10), :6:1)
at Object.processResource (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:829:8)
at processResource (C:\Users\HP\cisco-starter-repo\sextant\node_modules\loader-runner\lib\LoaderRunner.js:220:11)
at iteratePitchingLoaders (C:\Users\HP\cisco-starter-repo\sextant\node_modules\loader-runner\lib\LoaderRunner.js:171:10)
at runLoaders (C:\Users\HP\cisco-starter-repo\sextant\node_modules\loader-runner\lib\LoaderRunner.js:398:2)
at NormalModule._doBuild (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:819:3)
at NormalModule.build (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:963:15)
at C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\Compilation.js:1371:12
at NormalModule.needBuild (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:1253:32)

ERROR in node:http
Module build failed: UnhandledSchemeError: Reading from "node:http" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.
at C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:832:25
at Hook.eval [as callAsync] (eval at create (C:\Users\HP\cisco-starter-repo\sextant\node_modules\tapable\lib\HookCodeFactory.js:33:10), :6:1)
at Object.processResource (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:829:8)
at processResource (C:\Users\HP\cisco-starter-repo\sextant\node_modules\loader-runner\lib\LoaderRunner.js:220:11)
at iteratePitchingLoaders (C:\Users\HP\cisco-starter-repo\sextant\node_modules\loader-runner\lib\LoaderRunner.js:171:10)
at runLoaders (C:\Users\HP\cisco-starter-repo\sextant\node_modules\loader-runner\lib\LoaderRunner.js:398:2)
at NormalModule._doBuild (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:819:3)
at NormalModule.build (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:963:15)
at C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\Compilation.js:1371:12
at NormalModule.needBuild (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:1253:32)

ERROR in node:net
Module build failed: UnhandledSchemeError: Reading from "node:net" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.
at C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:832:25
at Hook.eval [as callAsync] (eval at create (C:\Users\HP\cisco-starter-repo\sextant\node_modules\tapable\lib\HookCodeFactory.js:33:10), :6:1)
at Object.processResource (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:829:8)
at processResource (C:\Users\HP\cisco-starter-repo\sextant\node_modules\loader-runner\lib\LoaderRunner.js:220:11)
at iteratePitchingLoaders (C:\Users\HP\cisco-starter-repo\sextant\node_modules\loader-runner\lib\LoaderRunner.js:171:10)
at runLoaders (C:\Users\HP\cisco-starter-repo\sextant\node_modules\loader-runner\lib\LoaderRunner.js:398:2)
at NormalModule._doBuild (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:819:3)
at NormalModule.build (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:963:15)
at C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\Compilation.js:1371:12
at NormalModule.needBuild (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:1253:32)

ERROR in node:process
Module build failed: UnhandledSchemeError: Reading from "node:process" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.
at C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:832:25
at Hook.eval [as callAsync] (eval at create (C:\Users\HP\cisco-starter-repo\sextant\node_modules\tapable\lib\HookCodeFactory.js:33:10), :6:1)
at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (C:\Users\HP\cisco-starter-repo\sextant\node_modules\tapable\lib\Hook.js:18:14)
at Object.processResource (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:829:8)
at processResource (C:\Users\HP\cisco-starter-repo\sextant\node_modules\loader-runner\lib\LoaderRunner.js:220:11)
at iteratePitchingLoaders (C:\Users\HP\cisco-starter-repo\sextant\node_modules\loader-runner\lib\LoaderRunner.js:171:10)
at runLoaders (C:\Users\HP\cisco-starter-repo\sextant\node_modules\loader-runner\lib\LoaderRunner.js:398:2)
at NormalModule._doBuild (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:819:3)
at NormalModule.build (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:963:15)
at C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\Compilation.js:1371:12

ERROR in node:stream
Module build failed: UnhandledSchemeError: Reading from "node:stream" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.
at C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:832:25
at Hook.eval [as callAsync] (eval at create (C:\Users\HP\cisco-starter-repo\sextant\node_modules\tapable\lib\HookCodeFactory.js:33:10), :6:1)
at Object.processResource (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:829:8)
at processResource (C:\Users\HP\cisco-starter-repo\sextant\node_modules\loader-runner\lib\LoaderRunner.js:220:11)
at iteratePitchingLoaders (C:\Users\HP\cisco-starter-repo\sextant\node_modules\loader-runner\lib\LoaderRunner.js:171:10)
at runLoaders (C:\Users\HP\cisco-starter-repo\sextant\node_modules\loader-runner\lib\LoaderRunner.js:398:2)
at NormalModule._doBuild (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:819:3)
at NormalModule.build (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:963:15)
at C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\Compilation.js:1371:12
at NormalModule.needBuild (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:1253:32)

ERROR in node:tls
Module build failed: UnhandledSchemeError: Reading from "node:tls" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.
at C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:832:25
at Hook.eval [as callAsync] (eval at create (C:\Users\HP\cisco-starter-repo\sextant\node_modules\tapable\lib\HookCodeFactory.js:33:10), :6:1)
at Object.processResource (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:829:8)
at processResource (C:\Users\HP\cisco-starter-repo\sextant\node_modules\loader-runner\lib\LoaderRunner.js:220:11)
at iteratePitchingLoaders (C:\Users\HP\cisco-starter-repo\sextant\node_modules\loader-runner\lib\LoaderRunner.js:171:10)
at runLoaders (C:\Users\HP\cisco-starter-repo\sextant\node_modules\loader-runner\lib\LoaderRunner.js:398:2)
at NormalModule._doBuild (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:819:3)
at NormalModule.build (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:963:15)
at C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\Compilation.js:1371:12
at NormalModule.needBuild (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:1253:32)

ERROR in node:url
Module build failed: UnhandledSchemeError: Reading from "node:url" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.
at C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:832:25
at Hook.eval [as callAsync] (eval at create (C:\Users\HP\cisco-starter-repo\sextant\node_modules\tapable\lib\HookCodeFactory.js:33:10), :6:1)
at processResource (C:\Users\HP\cisco-starter-repo\sextant\node_modules\loader-runner\lib\LoaderRunner.js:220:11)
at iteratePitchingLoaders (C:\Users\HP\cisco-starter-repo\sextant\node_modules\loader-runner\lib\LoaderRunner.js:171:10)
at runLoaders (C:\Users\HP\cisco-starter-repo\sextant\node_modules\loader-runner\lib\LoaderRunner.js:398:2)
at NormalModule._doBuild (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:819:3)
at NormalModule.build (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:963:15)
at C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\Compilation.js:1371:12
at NormalModule.needBuild (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:1253:32)

ERROR in node:util
Module build failed: UnhandledSchemeError: Reading from "node:util" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.
at C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:832:25
at Hook.eval [as callAsync] (eval at create (C:\Users\HP\cisco-starter-repo\sextant\node_modules\tapable\lib\HookCodeFactory.js:33:10), :6:1)
at Object.processResource (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:829:8)
at processResource (C:\Users\HP\cisco-starter-repo\sextant\node_modules\loader-runner\lib\LoaderRunner.js:220:11)
:10)
at runLoaders (C:\Users\HP\cisco-starter-repo\sextant\node_modules\loader-runner\lib\LoaderRunner.js:398:2)
at NormalModule._doBuild (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:819:3)
at NormalModule.build (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:963:15)
at C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\Compilation.js:1371:12
at NormalModule.needBuild (C:\Users\HP\cisco-starter-repo\sextant\node_modules\webpack\lib\NormalModule.js:1253:32)

webpack compiled with 49 errors and 2 warnings
`
I tried to fix the 1st error using this first answer to the question, I still have 48 errors, is this an issue with ipify and if so, how can I solve it?

Make the ipify API location configurable

This could be allow for example to set a location like ipify.mycompany.com where could be deployed a ipify fork, to ensure the API is always available.

ie issue

this is awesome and very useful, however as soon as i add to my react project and import it i am no longer compatible with ie, works on all other browsers though. it gives a 1002 syntax error.

Getting more done in GitHub with ZenHub

Hola! @rbecheras has created a ZenHub account for the sindresorhus organization. ZenHub is the only project management tool integrated natively in GitHub – created specifically for fast-moving, software-driven teams.

---

How do I use ZenHub?

To get set up with ZenHub, all you have to do is download the browser extension and log in with your GitHub account. Once you do, you’ll get access to ZenHub’s complete feature-set immediately.

What can ZenHub do?

ZenHub adds a series of enhancements directly inside the GitHub UI:

• Real-time, customizable task boards for GitHub issues;
• Multi-Repository burndown charts, estimates, and velocity tracking based on GitHub Milestones;
• Personal to-do lists and task prioritization;
• Time-saving shortcuts – like a quick repo switcher, a “Move issue” button, and much more.

Add ZenHub to GitHub

Still curious? See more ZenHub features or read user reviews. This issue was written by your friendly ZenHub bot, posted by request from @rbecheras.

What is the difference between ipify and public-ip?

I have found:

• https://github.com/sindresorhus/ipify
• https://github.com/sindresorhus/public-ip

What is the difference? I think it should be mentioned somewhere in the readme. Thanks

Unhandled Rejection (TypeError): ipify is not a function

Hi when I copy the following code into my create-react-app

`const ipify = require('ipify');

(async () => {
console.log(await ipify({useIPv6: false}));
//=> '82.142.31.236'
})();`

I got the following error in the browser

Unhandled Rejection (TypeError): ipify is not a function

and the error is pointing at (async () => { line

How do I fix this?

module 'platform' has no attribute 'linux_distribution'

When using python 3.8 or higher, it seems there is an issue with the package platform. As per this SO answer it seems the package.linux_distribution was deprecated starting with Python 3.5.

This makes the line 9 of settings.py:
from platform import mac_ver, win32_ver, linux_distribution, system

fail with the following error message:
ImportError: cannot import name 'linux_distribution' from 'platform'

An alternative seems to be the usage of the distro package.

I can make a PR if you are ok

Support multiple endpoints?

Currently, I'm using Promise.any() to get the IP address from multiple endpoints, it would be nice if we can support this directly.