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

Fix karma-browserify prebundle #469

Merged
merged 2 commits into from
Dec 12, 2014
Merged

Fix karma-browserify prebundle #469

merged 2 commits into from
Dec 12, 2014

Conversation

aron
Copy link
Contributor

@aron aron commented Dec 11, 2014

We now call the bundle.require('./src/annotator', {expose: 'annotator'}) each time the bundle is reset. This fixed the bundling issue and introduced a second problem, that require('./src/annotator') fails after the expose alias has been set. So to fix this I've just ensured all tests require('annotator').

@tilgovi
Copy link
Member

tilgovi commented Dec 11, 2014

LGTM at a glance but not to travis

@aron
Copy link
Contributor Author

aron commented Dec 11, 2014

I think it was just Travis being kranky.

As described in the GitHub issue. We now have to include "annotator"
explicitly as the "expose" parameter seems to break doing a relative
include for the same module.
@nickstenning
Copy link
Member

LGTM. It's unfortunate that we have to do require('annotator') but this is apparently another bug in one of watchify, browserify, or karma-browserify (it's not clear which): nikku/karma-browserify#63.

nickstenning added a commit that referenced this pull request Dec 12, 2014
@nickstenning nickstenning merged commit 1fcbe9c into master Dec 12, 2014
@nickstenning nickstenning deleted the karma-prebundle branch December 12, 2014 10:41
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.

3 participants