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
Add direct module.exports #62
Comments
This looks like more to be a problem with VS Code 🤔 |
I think OP's issue still has merit. There is a masking behaviour when using For example: // plugin.js
module.exports = 'hey';
exports.extra = 'another hey';
// main.js
const hey = require('./plugin');
hey === 'hey'; // => true
hey.extra === 'another hey'; // => false In this example we've lost the |
I believe this is done so as not to conflict with the modules transform - otherwise order would matter. |
Instead of exporting
module.exports = exports.default;
is it possible to add an option to exportmodule.exports = myDefaultVariableName
? Because the VS Code does not understand the first option to infer types but works fine with the second one. Thanks.The text was updated successfully, but these errors were encountered: