Fix for incorrect isparta import in gulpfile.babel.js #289
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Neglected to mention this regards the new gulpfile.babel.js |
jamesplease
added a commit
that referenced
this pull request
Dec 29, 2015
Fix for incorrect isparta import in gulpfile.babel.js
|
Thanks! I'll cut a release today. |
This was referenced Dec 29, 2015
Merged
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently coverage is broken in the generator and
gulp coveragefails with the following error:The cause of this is that there is no default export for isparta. This PR imports the entire module under an isparta variable so the property reference to the instrumenter works as expected.