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

Avoid setting QUnit.module.exports = Pretender. #156

Closed
wants to merge 1 commit into from

Conversation

rwjblue
Copy link
Contributor

@rwjblue rwjblue commented May 5, 2016

When using QUnit along with Pretender, the UMD style that we were previously using would assign an .exports property to the QUnit.module method (which is present in QUnit 1.x as self.module also). This changes to check that we are actually in a node-like environment (where exports === module.exports) before setting module.exports.

When using `QUnit` along with `Pretender`, the UMD style that we were previously using would assign an `.exports` property to the `QUnit.module` method (which is present in QUnit 1.x as `self.module` also). This changes to check that we are actually in a node-like environment (where `exports === module.exports`) before setting `module.exports`.
@trek trek mentioned this pull request Oct 6, 2016
@Turbo87
Copy link

Turbo87 commented Dec 2, 2016

@rwjblue is this PR still relevant? from my recent journeys it seems that the current Pretender releases don't have any issues with QUnit running in parallel anymore

@rwjblue
Copy link
Contributor Author

rwjblue commented Dec 3, 2016

@Turbo87 - It is relevant when using QUnit 1.x, but not 2.x (since 2.x doesn't set module global).

@rwjblue rwjblue closed this Jan 3, 2017
@rwjblue rwjblue deleted the patch-1 branch January 3, 2017 21:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants