-
Notifications
You must be signed in to change notification settings - Fork 13.1k
Closed
Labels
BugA bug in TypeScriptA bug in TypeScriptFixedA PR has been merged for this issueA PR has been merged for this issue
Milestone
Description
OS Version: macOS
TypeScript Version: typescript@^2.0.6-insiders.20161014 using vscode 1.7 insiders
Note: "typescript.experimentalAutomaticTypeAcquisition": true must be in your vscode user settings.
Steps to Reproduce
-
- clear
~/Library/Application Support/Microsoft/TypeScript/node_modules/@types
- clear
-
- start vscode on an workspace with the following two files:
package.json
- start vscode on an workspace with the following two files:
{
"name": "test",
"version": "0.0.1",
"dependencies": {
"express" : "4.14.0"
},
"engines" : {
"node" : "6.7.0",
"npm" : "3.10.x"
}
}test.js
var fs = require('fs');
fs.-
- open
test.jsin editor
- open
-
- append to the file:
var calendar = require('node-calendar');
calendar.-
- invoke inteliisense; no proposals
-
- open
package.jsonin the editor
- open
-
- add the following dependency
"node-calendar" : "0.1.4"-
- go back to
test.js
- go back to
-
- place caret behind
calendar.and invoke intellisense using Cmd+Space
- place caret behind
Expected behavior:
Intellisense proposals for the node-calendar module are presented
Actual behavior:
No node-calendar specific proposals are shown. ~/Library/Application Support/Microsoft/TypeScript/node_modules/@types remains unchanged.
-
- restart vscode
-
- repeat steps 8. and 9.
-> Intellisense proposals for the node-calendar module are presented
Note: When first adding the dependency for node-calendar in package.json and then adding the require in test.js auto acquisition and intellisense work as expected.
Metadata
Metadata
Assignees
Labels
BugA bug in TypeScriptA bug in TypeScriptFixedA PR has been merged for this issueA PR has been merged for this issue