microsoft / microsoft/nodejstools
Up-to-date builds are not reported to VS.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.8k
- Forks
- 355
- PR merge metrics
- No merged PRs in 30d
Description
Expected Behavior
nodejstools reports up-to-date build status to VS.
Actual Behavior
nodejstools does not report build status to VS:
Steps to Reproduce
- Create a new nodejs console app in VS.
- Add the
--incrementalflag to thebuildscript entry inpackage.json. - Run build.
- Run build again.
Both times there will be a build succeeded message and no up to date message:
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
While we pick up TS errors from build failures in the error window, we don't currently have a way to report whether or not a build ran or not due to passing the incremental flag.
Converted from https://developercommunity.visualstudio.com/t/Up-to-date-IDE-build-skipping-feature-is/1410083
Contributor guide
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
Reproduce the two-build sequence in a Node.js console app with --incremental in package.json, then trace how nodejstools reports build results to Visual Studio. Done means the first build reports success and the second reports one up-to-date build instead of another succeeded build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, nodejs
- Domain
- build-system, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100