Skip to content
This repository has been archived by the owner on Aug 4, 2021. It is now read-only.

module.exports.property failure #112

Closed
Qard opened this issue Sep 18, 2016 · 1 comment
Closed

module.exports.property failure #112

Qard opened this issue Sep 18, 2016 · 1 comment

Comments

@Qard
Copy link

Qard commented Sep 18, 2016

It seems assigning an object to module.exports and then assigning a property on module.exports, rather than directly on that object will not attach it to
that object.

see: max-mapper/yo-yo#48 (comment)
Rich-Harris added a commit that referenced this issue Sep 18, 2016
@Rich-Harris
assign properties to default export (#112)
b45ecdc
Rich-Harris added a commit that referenced this issue Sep 18, 2016
@Rich-Harris
Merge branch 'master' into gh-112
289fa23
@Rich-Harris Rich-Harris mentioned this issue Sep 18, 2016
Merged
Rich-Harris added a commit that referenced this issue Sep 18, 2016
@Rich-Harris
Merge pull request #113 from rollup/gh-112
e24f1e8 
Add named exports to default, in optimised modules
@Rich-Harris
Copy link
Contributor

Oh, CommonJS. Always finding new and exciting ways to make life difficult... Thanks, this is fixed in 5.0.4

@Rich-Harris Rich-Harris mentioned this issue Sep 18, 2016
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Qard @Rich-Harris