webclient does not start
Maintainers usually reply within 2 days
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- nodejs
- Domain
- build-system, developer-experience, web-dev
Research direction
Start with the Web-Restore Cake task and the Node/npm engine requirements reported during npm restore. Inspect Computator.NET.WebClient/Hosting/DevelopmentAssets.cs around PrepareAsync and RunAsync, then verify the project’s pinned Node/npm versions and reproduce the startup path from Program.cs. Done means the frontend preparation completes successfully with a compatible Node/npm version and the webclient starts without the reported restore error.
Written by the indexing model from the issue text.
Description
C:/Projects/Computator.NET/Computator.NET.WebClient/bin/Release/net10.0/Computator.NET.WebClient.exe
Preparing the web interface through Cake Web-Build
Tool 'cake.tool' (version '6.3.0') was restored. Available commands: dotnet-cake
Restore was successful.
────────────────────────────────────────────────────────────────────────────────────────────────────
Setup
────────────────────────────────────────────────────────────────────────────────────────────────────
════════════════════════════════════════════════════════════════════════════════════════════════════
Web-Restore
════════════════════════════════════════════════════════════════════════════════════════════════════
npm error code EBADENGINE
npm error engine Unsupported engine
npm error engine Not compatible with your version of node/npm: [email protected]
npm error notsup Not compatible with your version of node/npm: [email protected]
npm error notsup Required: {"node":">=24.21.0 <25","npm":">=11.19.0 <12"}
npm error notsup Actual: {"node":"v24.11.1","npm":"11.7.0"}
npm error A complete log of this run can be found in: C:\Users\hyperbook\AppData\Local\npm-cache_logs\2026-10-24T00_32_10_945Z-debug-0.log
An error occurred when executing task 'Web-Restore'.
────────────────────────────────────────────────────────────────────────────────────────────────────
TearDown
────────────────────────────────────────────────────────────────────────────────────────────────────
Task Duration Status
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Setup 00:00:01.9441302 Succeeded
Web-Restore 00:00:04.9963393 Failed
Teardown 00:00:00.0043955 Succeeded
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Total: 00:00:06.9448650
Error: cmd.exe failed with exit code 1.
Unhandled exception. System.InvalidOperationException: Frontend preparation failed (exit 1). See the Cake output above; the pinned Node/npm and .NET SDK are required for source development.
at Computator.NET.WebClient.Hosting.DevelopmentAssets.RunAsync(String directory, CancellationToken cancellation, String[] arguments) in C:\Projects\Computator.NET\Computator.NET.WebClient\Hosting\DevelopmentAssets.cs:line 115
at Computator.NET.WebClient.Hosting.DevelopmentAssets.RunAsync(String directory, CancellationToken cancellation, String[] arguments) in C:\Projects\Computator.NET\Computator.NET.WebClient\Hosting\DevelopmentAssets.cs:line 120
at Computator.NET.WebClient.Hosting.DevelopmentAssets.PrepareAsync(WebApplicationBuilder builder) in C:\Projects\Computator.NET\Computator.NET.WebClient\Hosting\DevelopmentAssets.cs:line 32
at Computator.NET.WebClient.Hosting.DevelopmentAssets.PrepareAsync(WebApplicationBuilder builder) in C:\Projects\Computator.NET\Computator.NET.WebClient\Hosting\DevelopmentAssets.cs:line 36
at Computator.NET.WebClient.Program.Main(String[] args) in C:\Projects\Computator.NET\Computator.NET.WebClient\Program.cs:line 13
at Computator.NET.WebClient.Program.
Process finished with exit code -532,462,766.
- Dominant language
- C#
- Stars
- 249
- Forks
- 53
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 131
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PawelTroka/Computator.NET
-
Difficulty 1/5 Under an hour Newbie friendliness 1/100
PawelTroka/Computator.NET#297 ·
Maintainers usually reply within 2 days
-
complex chart is not being drawn at all in monoPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
PawelTroka/Computator.NET#295 ·
Maintainers usually reply within 2 days
-
mono autocomplete pretty much brokenPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
PawelTroka/Computator.NET#293 ·
Maintainers usually reply within 2 days
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
PawelTroka/Computator.NET#292 ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
PawelTroka/Computator.NET#224 ·
Maintainers usually reply within 2 days
All issues in PawelTroka/Computator.NET
Similar issues
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
dotnet/dotnet-api-docs#13210 ·
Maintainers usually reply within 1 day
-
aspnet-core/svc doc-enhancement mvc/subsvc Pri2
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
dotnet/AspNetCore.Docs#38016 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
HicServices/RDMP#2398 ·