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

[ismailPervez]

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?

[sindresorhus]

This is a problem with your Webpack config. This is not the place to ask Webpack questions.