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

module.exports.property failure #112

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

Comments

Projects
None yet
2 participants
@Qard
Copy link

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: maxogden/yo-yo#48 (comment)

Rich-Harris added a commit that referenced this issue Sep 18, 2016

Rich-Harris added a commit that referenced this issue Sep 18, 2016

Merge pull request #113 from rollup/gh-112
Add named exports to default, in optimised modules
@Rich-Harris

This comment has been minimized.

Copy link
Contributor

commented Sep 18, 2016

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.