Remove jasmine ruby gem and its requiring #385
Merged
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.
This was missed from the pull request that
replaced the jasmine ruby gem with the
jasmine-browser-runner:
#382
Note: this locks the
concurrent-ruby
gem to v1.3.4 due to changes in that version breaking theactivesupport
gem, and so middleman. This has been fixed in theactivesupport
code but not included on the v7.0 release track yet, from what I can tell, so we either wait for them to do that and middleman's gemspec should allow it to be picked up, or wait for middleman to change their gemspec semver range to include a higher release that does include it.