Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

intellisense does not work when using module.exports.fnName #4943

Closed
SamVerschueren opened this issue Apr 5, 2016 · 4 comments
Closed

intellisense does not work when using module.exports.fnName #4943

SamVerschueren opened this issue Apr 5, 2016 · 4 comments

Comments

@SamVerschueren
Copy link
Contributor

  • VSCode Version: 0.10.14 (insiders) and below
  • OS Version: Mac OS X 10.11.3

Steps to Reproduce:

  1. Create a file called cfx.js with the following content
'use strict';
module.exports.generateCanvas = function (fileOrUrl) {
    console.log(fileOrUrl);
};
  1. Create a file index.js
'use strict';
var cfx = require('./file1');
  1. When you type cfx. in index.js, it will not suggest generateCanvas. If you change cfx.js to exports.generateCanvas instead of module.exports.generateCanvas, it works.

This seems to be a bug because both notations are equivalent.

@egamma
Copy link
Member

egamma commented Apr 5, 2016

This issue was moved to microsoft/TypeScript#7824

@egamma egamma closed this as completed Apr 5, 2016
@SamVerschueren
Copy link
Contributor Author

Thanks @egamma

@danielo515
Copy link

Does that mean that is not a problem in VSCode but on typescript itself?

@SamVerschueren
Copy link
Contributor Author

I believe it's the TypeScript language server that deals with this so I think it is.

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants