Starting the Aspire apphost from a configured script on a project with 18ish ...
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
Starting the Aspire apphost from a configured script on a project with 18ish projects (40% node, 60% dotnet). I often find that aspire crashes and I have to run it a second time. I'm running aspire --isolated which is what a lot of team members are also doing.
---
| Field | Value |
| --- | --- |
| App version | 1.1.14 |
| OS | Windows 10.0.26200 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Week 15 |
Contributor guide
Research direction
Start by reproducing the configured-script launch with `aspire --isolated` on the reported mixed Node/.NET project setup, using the listed App version and Windows environment. Capture the crash details and compare the first launch with the second; done means the intermittent failure is isolated to a reproducible cause or the missing diagnostic information is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- desktop, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100