microsoft / microsoft/nodejstools
New TypeScript Node project always says "Project out of date"
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.8k
- Forks
- 355
- PR merge metrics
- No merged PRs in 30d
Description
steps to repro:
create new blank node app (typescript)
run project (1st time it says proj is out of date, subsequent times it builds ok)
now set js out dir in project settings to something valid
now the project will never run without saying it is out of date, even beyond a vs restart! that is, until i clear the setting..
this problem only occurred after i upgrades to npm 3 (from 2) and it occurs with 1.1 rc2 and some other dev build from august
i'm using:
- windows 7 x64 pro
- npm 3.3.2
- visual studio ultimate 2013 update 5
- NTVS 1.1 RC2
- Resharper 9.2
note: make sure visual studio is set to "prompt to build" when project is out of date (settings -> search for "build and run")
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
Start by reproducing the issue with a blank TypeScript Node app in Visual Studio, using the listed npm 3.3.2 and NTVS 1.1 RC2 setup. Compare the initial run and the behavior after setting a valid JavaScript output directory; done when the project no longer remains perpetually out of date after that setting is changed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- build-system, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100