Config:
- Win8.1 w/ latest updates
- VS2013 Ult Update 3 RC
- NTVS build 20714.00
Repro:
- Create a blank JS web application
- Install Express through the Install npm manager dialog
- open package.json file in VS editor
- install another npm package, ie. mongodb, through the npm manager dialog
- VS prompts that package.json has been modified outside of the editor, if I wanted to reload, chose YES
- The new package is added to the dependency list in package.json.
- leave package.json file open, and try to install another npm module, ie. cookie-parser
Actual Result:
- You are no longer prompted that package.json has been modified, and
- package.json is not been updated with the new module.
- The subsequent installation of the module presented the same behavior
Until you close and reopen package.json, you won't see the newly added npm modules in the dependency list. Meaning, you have to close and reopen package.json to see the correct dependency list.
- Win8.1 w/ latest updates
- VS2013 Ult Update 3 RC
- NTVS build 20714.00
Repro:
- Create a blank JS web application
- Install Express through the Install npm manager dialog
- open package.json file in VS editor
- install another npm package, ie. mongodb, through the npm manager dialog
- VS prompts that package.json has been modified outside of the editor, if I wanted to reload, chose YES
- The new package is added to the dependency list in package.json.
- leave package.json file open, and try to install another npm module, ie. cookie-parser
Actual Result:
- You are no longer prompted that package.json has been modified, and
- package.json is not been updated with the new module.
- The subsequent installation of the module presented the same behavior
Until you close and reopen package.json, you won't see the newly added npm modules in the dependency list. Meaning, you have to close and reopen package.json to see the correct dependency list.