microsoft / microsoft/vscode-generator-code
Waiting for preLaunchTask 'build'...
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.6k
- Forks
- 262
- Avg merge
- 15d 22h
- Merged PRs (30d)
- 1
Description
If I choose 'start debugging (run extension) in the newly generated extension, extension host does not actually start and the whole thing is in some "hang state". In a while "Waiting for preLaunchTask 'build'..." message appears.
Appeared that default build task depends on two watch tasks, and they, eventually never finish.
Quick googling revealed a problem, but the solution from that post did not help.
Changing preLaunchTask to a non-watch task (i.e.: npm: compile) helps, but increases startup time.
Also, it was mentioned earlier: https://github.com/microsoft/vscode-generator-code/issues/311
Please update the generator to address this issue
OS: MacOS 15.4
VSCode: 1.99.0
generator-code@1.11.9
? What type of extension do you want to create? New Extension (TypeScript)
? What's the name of your extension? example-test-es
? What's the identifier of your extension? example-test-es
? What's the description of your extension?
? Initialize a git repository? No
? Which bundler to use? esbuild
? Which package manager to use? npm
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Inspect the generated extension's default build task, preLaunchTask, and the two watch tasks described in the report. Compare them with the non-watch npm: compile task and determine how the generated debugging configuration should avoid waiting indefinitely. Done means a newly generated TypeScript extension starts debugging without the reported hang.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100