[Bug]: Server is not starting in Windows 11

[diant]

Describe the bug

After checking out the project, I tried to run the 'npm run server:start' command but I'm receiving the following error:
Error: Only URLs with a scheme in: file and data are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:' at new NodeError (node:internal/errors:399:5) at throwIfUnsupportedURLScheme (node:internal/modules/esm/resolve:1059:11) at defaultResolve (node:internal/modules/esm/resolve:1135:3) at nextResolve (node:internal/modules/esm/loader:163:28) at ESMLoader.resolve (node:internal/modules/esm/loader:838:30) at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18) at ESMLoader.import (node:internal/modules/esm/loader:525:22) at importModuleDynamically (node:internal/modules/cjs/loader:1186:29) at importModuleDynamicallyWrapper (node:internal/vm/module:429:21) at importModuleDynamically (node:internal/vm:106:46)

Full Error here:
`PS C:\dev\sfeir-school-angular> npm run server:start

sfeir-school-angular@13.2.0 server:start
nx serve server-express --no-inspect

nx run server-express:serve --no-inspect

chunk (runtime: main) main.js (main) 14.4 KiB [entry] [rendered]
webpack compiled successfully (b6635680694a4153)
Error: Only URLs with a scheme in: file and data are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'
at new NodeError (node:internal/errors:399:5)
at throwIfUnsupportedURLScheme (node:internal/modules/esm/resolve:1059:11)
at defaultResolve (node:internal/modules/esm/resolve:1135:3)
at nextResolve (node:internal/modules/esm/loader:163:28)
at ESMLoader.resolve (node:internal/modules/esm/loader:838:30)
at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)
at ESMLoader.import (node:internal/modules/esm/loader:525:22)
at importModuleDynamically (node:internal/modules/cjs/loader:1186:29)
at importModuleDynamicallyWrapper (node:internal/vm/module:429:21)
at importModuleDynamically (node:internal/vm:106:46)`

Reproduction steps

1. Checkout the project
2. Go to the project root folder
3. run npm run server:start

Expected behavior

Server should run :)

Screenshots

No response

System information

• Windows Edition Windows 11 Pro
  Version 22H2
  Installed on ‎14/‎06/‎2023
  OS build 22621.1848
  Experience Windows Feature Experience Pack 1000.22642.1000.0

• Browser: Chrome (latest version)

• Editor: VSCode

Additional context

No response