microsoft / microsoft/nodejstools
JavaScript Web and Express Web roles fail to package
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.8k
- Forks
- 355
- PR merge metrics
- No merged PRs in 30d
Description
Expected Behavior
Expected Package command to succeed.
Actual Behavior
Package command fails.
- NTVS Version: 1.5.20902.1
- Visual Studio Version: 16.8.0 Preview 4
Steps to Reproduce
- Create new "Azure Cloud Service" project and add either a JavaScript Web Role or a JavaScript Express Web Role
- Right click on the Azure Cloud Service project node and select "Package"
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 failure with an Azure Cloud Service project containing a JavaScript Web Role or JavaScript Express Web Role, then invoke Package from the Azure Cloud Service project node. Trace the packaging entry point to determine why the command fails; done means the Package command succeeds for both role types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, javascript
- Domain
- build-system, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100