Add direct module.exports

[zavr-1]

Instead of exporting module.exports = exports.default; is it possible to add an option to export module.exports = myDefaultVariableName? Because the VS Code does not understand the first option to infer types but works fine with the second one. Thanks.

[yvele]

This looks like more to be a problem with VS Code 🤔

[gwillz]

I think OP's issue still has merit. There is a masking behaviour when using module.exports and exports. It's best to stick to one form per file.

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 .extra property, because the module.export has a sort of priority. If we were to only use the exports.extra statement, we would be able to access 'another hey'.

[ljharb]

I believe this is done so as not to conflict with the modules transform - otherwise order would matter.