MSSQL connection with itwin web app

[Zubair-KPM]

HI guys, when iam connecting with the mssql for testing the databse is runing on the local server as well on the VS CODE terminal but when connect with my digital twin app it shows error.

Its a compilation error there no error in the code but when run it. It shows the error.

ERROR:

Compiled with problems:
×
ERROR in ./src/database/node_modules/body-parser/lib/read.js 19:11-26
Module not found: Error: Can't resolve 'zlib' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\body-parser\lib'

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 ./src/database/node_modules/body-parser/lib/types/urlencoded.js 201:12-34
Module not found: Error: Can't resolve 'querystring' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\body-parser\lib\types'

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: { "querystring": require.resolve("querystring-es3") }'
- install 'querystring-es3'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "querystring": false }
ERROR in ./src/database/node_modules/content-disposition/index.js 21:15-39
Module not found: Error: Can't resolve 'path' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\content-disposition'

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: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
ERROR in ./src/database/node_modules/cookie-signature/index.js 5:13-30
Module not found: Error: Can't resolve 'crypto' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\cookie-signature'

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: { "crypto": require.resolve("crypto-browserify") }'
- install 'crypto-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "crypto": false }
ERROR in ./src/database/node_modules/destroy/index.js 15:17-41
Module not found: Error: Can't resolve 'fs' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\destroy'
ERROR in ./src/database/node_modules/destroy/index.js 16:13-30
Module not found: Error: Can't resolve 'stream' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\destroy'

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 ./src/database/node_modules/destroy/index.js 17:11-26
Module not found: Error: Can't resolve 'zlib' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\destroy'

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 ./src/database/node_modules/etag/index.js 20:13-30
Module not found: Error: Can't resolve 'crypto' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\etag'

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: { "crypto": require.resolve("crypto-browserify") }'
- install 'crypto-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "crypto": false }
ERROR in ./src/database/node_modules/etag/index.js 21:12-31
Module not found: Error: Can't resolve 'fs' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\etag'
ERROR in ./src/database/node_modules/express/lib/application.js 22:11-26
Module not found: Error: Can't resolve 'http' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\express\lib'

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 ./src/database/node_modules/express/lib/application.js 29:14-37
Module not found: Error: Can't resolve 'path' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\express\lib'

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: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
ERROR in ./src/database/node_modules/express/lib/request.js 17:11-30
Module not found: Error: Can't resolve 'net' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\express\lib'
ERROR in ./src/database/node_modules/express/lib/request.js 19:11-26
Module not found: Error: Can't resolve 'http' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\express\lib'

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 ./src/database/node_modules/express/lib/response.js 20:11-26
Module not found: Error: Can't resolve 'http' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\express\lib'

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 ./src/database/node_modules/express/lib/response.js 23:11-26
Module not found: Error: Can't resolve 'path' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\express\lib'

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: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
ERROR in ./src/database/node_modules/express/lib/utils.js 23:18-40
Module not found: Error: Can't resolve 'querystring' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\express\lib'

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: { "querystring": require.resolve("querystring-es3") }'
- install 'querystring-es3'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "querystring": false }
ERROR in ./src/database/node_modules/express/lib/view.js 16:11-26
Module not found: Error: Can't resolve 'path' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\express\lib'

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: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
ERROR in ./src/database/node_modules/express/lib/view.js 17:9-22
Module not found: Error: Can't resolve 'fs' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\express\lib'
ERROR in ./src/database/node_modules/js-md4/src/md4.js 116:17-34
Module not found: Error: Can't resolve 'crypto' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\js-md4\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: { "crypto": require.resolve("crypto-browserify") }'
- install 'crypto-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "crypto": false }
ERROR in ./src/database/node_modules/mime-types/index.js 15:14-37
Module not found: Error: Can't resolve 'path' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\mime-types'

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: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
ERROR in ./src/database/node_modules/mime/mime.js 1:11-26
Module not found: Error: Can't resolve 'path' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\mime'

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: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
ERROR in ./src/database/node_modules/mime/mime.js 2:9-22
Module not found: Error: Can't resolve 'fs' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\mime'
ERROR in ./src/database/node_modules/native-duplexpair/index.js 3:15-39
Module not found: Error: Can't resolve 'stream' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\native-duplexpair'

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 ./src/database/node_modules/send/index.js 22:9-22
Module not found: Error: Can't resolve 'fs' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\send'
ERROR in ./src/database/node_modules/send/index.js 27:11-26
Module not found: Error: Can't resolve 'path' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\send'

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: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
ERROR in ./src/database/node_modules/send/index.js 29:13-30
Module not found: Error: Can't resolve 'stream' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\send'

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 ./src/database/node_modules/serve-static/index.js 18:14-37
Module not found: Error: Can't resolve 'path' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\serve-static'

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: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
ERROR in ./src/database/node_modules/tarn/dist/Pool.js 10:17-34
Module not found: Error: Can't resolve 'timers' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\tarn\dist'

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: { "timers": require.resolve("timers-browserify") }'
- install 'timers-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "timers": false }
ERROR in ./src/database/node_modules/tedious/lib/bulk-load.js 9:14-31
Module not found: Error: Can't resolve 'stream' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\tedious\lib'

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 ./src/database/node_modules/tedious/lib/connection.js 7:37-54
Module not found: Error: Can't resolve 'crypto' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\tedious\lib'

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: { "crypto": require.resolve("crypto-browserify") }'
- install 'crypto-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "crypto": false }
ERROR in ./src/database/node_modules/tedious/lib/connection.js 8:33-46
Module not found: Error: Can't resolve 'os' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\tedious\lib'

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 ./src/database/node_modules/tedious/lib/connection.js 10:34-48
Module not found: Error: Can't resolve 'net' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\tedious\lib'
ERROR in ./src/database/node_modules/tedious/lib/connection.js 11:34-48
Module not found: Error: Can't resolve 'dns' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\tedious\lib'
ERROR in ./src/database/node_modules/tedious/lib/connection.js 12:40-60
Module not found: Error: Can't resolve 'constants' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\tedious\lib'

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: { "constants": require.resolve("constants-browserify") }'
- install 'constants-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "constants": false }
ERROR in ./src/database/node_modules/tedious/lib/connection.js 13:14-31
Module not found: Error: Can't resolve 'stream' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\tedious\lib'

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 ./src/database/node_modules/tedious/lib/connector.js 9:34-48
Module not found: Error: Can't resolve 'net' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\tedious\lib'
ERROR in ./src/database/node_modules/tedious/lib/incoming-message-stream.js 8:14-31
Module not found: Error: Can't resolve 'stream' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\tedious\lib'

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 ./src/database/node_modules/tedious/lib/instance-lookup.js 8:34-48
Module not found: Error: Can't resolve 'dns' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\tedious\lib'
ERROR in ./src/database/node_modules/tedious/lib/message.js 7:14-31
Module not found: Error: Can't resolve 'stream' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\tedious\lib'

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 ./src/database/node_modules/tedious/lib/ntlm-payload.js 8:37-54
Module not found: Error: Can't resolve 'crypto' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\tedious\lib'

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: { "crypto": require.resolve("crypto-browserify") }'
- install 'crypto-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "crypto": false }
ERROR in ./src/database/node_modules/tedious/lib/outgoing-message-stream.js 8:14-31
Module not found: Error: Can't resolve 'stream' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\tedious\lib'

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 ./src/database/node_modules/tedious/lib/sender.js 8:36-52
Module not found: Error: Can't resolve 'dgram' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\tedious\lib'
ERROR in ./src/database/node_modules/tedious/lib/sender.js 9:34-48
Module not found: Error: Can't resolve 'net' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\tedious\lib'
ERROR in ./src/database/node_modules/tedious/lib/token/token-stream-parser.js 9:14-31
Module not found: Error: Can't resolve 'stream' in 'C:\Users\KPM63\kpm-sakinaka\src\database\node_modules\tedious\lib\token'

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: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\KPM63\kpm-sakinaka\node_modules\webpack\lib\NormalModule.js:918:25
at Hook.eval [as callAsync] (eval at create (C:\Users\KPM63\kpm-sakinaka\node_modules\tapable\lib\HookCodeFactory.js:33:10), :6:1)
at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (C:\Users\KPM63\kpm-sakinaka\node_modules\tapable\lib\Hook.js:18:14)
at Object.processResource (C:\Users\KPM63\kpm-sakinaka\node_modules\webpack\lib\NormalModule.js:915:8)
at processResource (C:\Users\KPM63\kpm-sakinaka\node_modules\loader-runner\lib\LoaderRunner.js:220:11)
at iteratePitchingLoaders (C:\Users\KPM63\kpm-sakinaka\node_modules\loader-runner\lib\LoaderRunner.js:171:10)
at runLoaders (C:\Users\KPM63\kpm-sakinaka\node_modules\loader-runner\lib\LoaderRunner.js:398:2)
at NormalModule._doBuild (C:\Users\KPM63\kpm-sakinaka\node_modules\webpack\lib\NormalModule.js:905:3)
at NormalModule.build (C:\Users\KPM63\kpm-sakinaka\node_modules\webpack\lib\NormalModule.js:1079:15)
at C:\Users\KPM63\kpm-sakinaka\node_modules\webpack\lib\Compilation.js:1374:12
at NormalModule.needBuild (C:\Users\KPM63\kpm-sakinaka\node_modules\webpack\lib\NormalModule.js:1408:26)
at Compilation._buildModule (C:\Users\KPM63\kpm-sakinaka\node_modules\webpack\lib\Compilation.js:1355:10)
at C:\Users\KPM63\kpm-sakinaka\node_modules\webpack\lib\util\AsyncQueue.js:305:10
at Hook.eval [as callAsync] (eval at create (C:\Users\KPM63\kpm-sakinaka\node_modules\tapable\lib\HookCodeFactory.js:33:10), :6:1)
at AsyncQueue._startProcessing (C:\Users\KPM63\kpm-sakinaka\node_modules\webpack\lib\util\AsyncQueue.js:295:26)
at AsyncQueue._ensureProcessing (C:\Users\KPM63\kpm-sakinaka\node_modules\webpack\lib\util\AsyncQueue.js:282:12)
at process.processImmediate (node:internal/timers:478:21)
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\KPM63\kpm-sakinaka\node_modules\webpack\lib\NormalModule.js:918:25
at Hook.eval [as callAsync] (eval at create (C:\Users\KPM63\kpm-sakinaka\node_modules\tapable\lib\HookCodeFactory.js:33:10), :6:1)
at Object.processResource (C:\Users\KPM63\kpm-sakinaka\node_modules\webpack\lib\NormalModule.js:915:8)
at processResource (C:\Users\KPM63\kpm-sakinaka\node_modules\loader-runner\lib\LoaderRunner.js:220:11)
at iteratePitchingLoaders (C:\Users\KPM63\kpm-sakinaka\node_modules\loader-runner\lib\LoaderRunner.js:171:10)
at runLoaders (C:\Users\KPM63\kpm-sakinaka\node_modules\loader-runner\lib\LoaderRunner.js:398:2)
at NormalModule._doBuild (C:\Users\KPM63\kpm-sakinaka\node_modules\webpack\lib\NormalModule.js:905:3)
at NormalModule.build (C:\Users\KPM63\kpm-sakinaka\node_modules\webpack\lib\NormalModule.js:1079:15)
at C:\Users\KPM63\kpm-sakinaka\node_modules\webpack\lib\Compilation.js:1374:12
at NormalModule.needBuild (C:\Users\KPM63\kpm-sakinaka\node_modules\webpack\lib\NormalModule.js:1408:26)
at Compilation._buildModule (C:\Users\KPM63\kpm-sakinaka\node_modules\webpack\lib\Compilation.js:1355:10)
at C:\Users\KPM63\kpm-sakinaka\node_modules\webpack\lib\util\AsyncQueue.js:305:10
at Hook.eval [as callAsync] (eval at create (C:\Users\KPM63\kpm-sakinaka\node_modules\tapable\lib\HookCodeFactory.js:33:10), :6:1)
at AsyncQueue._startProcessing (C:\Users\KPM63\kpm-sakinaka\node_modules\webpack\lib\util\AsyncQueue.js:295:26)
at AsyncQueue._ensureProcessing (C:\Users\KPM63\kpm-sakinaka\node_modules\webpack\lib\util\AsyncQueue.js:282:12)
at process.processImmediate (node:internal/timers:478:21)
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\KPM63\kpm-sakinaka\node_modules\webpack\lib\NormalModule.js:918:25
at Hook.eval [as callAsync] (eval at create (C:\Users\KPM63\kpm-sakinaka\node_modules\tapable\lib\HookCodeFactory.js:33:10), :6:1)
at Object.processResource (C:\Users\KPM63\kpm-sakinaka\node_modules\webpack\lib\NormalModule.js:915:8)
at processResource (C:\Users\KPM63\kpm-sakinaka\node_modules\loader-runner\lib\LoaderRunner.js:220:11)
at iteratePitchingLoaders (C:\Users\KPM63\kpm-sakinaka\node_modules\loader-runner\lib\LoaderRunner.js:171:10)
at runLoaders (C:\Users\KPM63\kpm-sakinaka\node_modules\loader-runner\lib\LoaderRunner.js:398:2)
at NormalModule._doBuild (C:\Users\KPM63\kpm-sakinaka\node_modules\webpack\lib\NormalModule.js:905:3)
at NormalModule.build (C:\Users\KPM63\kpm-sakinaka\node_modules\webpack\lib\NormalModule.js:1079:15)
at C:\Users\KPM63\kpm-sakinaka\node_modules\webpack\lib\Compilation.js:1374:12
at NormalModule.needBuild (C:\Users\KPM63\kpm-sakinaka\node_modules\webpack\lib\NormalModule.js:1408:26)
at Compilation._buildModule (C:\Users\KPM63\kpm-sakinaka\node_modules\webpack\lib\Compilation.js:1355:10)
at C:\Users\KPM63\kpm-sakinaka\node_modules\webpack\lib\util\AsyncQueue.js:305:10
at Hook.eval [as callAsync] (eval at create (C:\Users\KPM63\kpm-sakinaka\node_modules\tapable\lib\HookCodeFactory.js:33:10), :6:1)
at AsyncQueue._startProcessing (C:\Users\KPM63\kpm-sakinaka\node_modules\webpack\lib\util\AsyncQueue.js:295:26)
at AsyncQueue._ensureProcessing (C:\Users\KPM63\kpm-sakinaka\node_modules\webpack\lib\util\AsyncQueue.js:282:12)
at process.processImmediate (node:internal/timers:478:21)

Please help me out with this!