[proposal] commonjs mods can only export default

[caridy]

based on this discussion: babel/babel#95 (comment)

[ericf]

Why can't CommonJS modules use only named exports?

[caridy]

@ericf check the discussion from the link, there is a lot of info there about why we should probably do that.

[ericf]

@caridy I read the whole post. But passed on the title of this issue and it's lack of description, I'm asking for some clarity, because I don't understand what you're proposing.

[caridy]

ah, ok. This pkg contains an npm module resolver that detects npm dependencies and creates a synthetic es6 module that contains named exports for any member of the module.exports object. This is used today to validate that in deed, those CJS modules are suppose to export what ES6 modules are trying to import. The proposal is to narrow that down to only support default import from CJS modules.

[ericf]

I thought this package only deals with resolving ES6 imports of other ES6 modules that are in other npm packages. Where does this package deal with looking at CommonJS modules? 😕

[ericf]

those CJS modules are suppose to export what ES6 modules are trying to import.

I don't follow this.

[ericf]

The proposal is to narrow that down to only support default import from CJS modules.

Where does this package import CJS modules today? I thought it only produces CJS modules via the transpiler.

[caridy]

this is the line that I want to remove: https://github.com/caridy/grunt-bundle-jsnext-lib/blob/master/lib/npm-resolver.js#L45

[caridy]

that obviously means we need to change all our pkgs.