Tom Spencer

I've been using 2.0.0 with my own branch of grunt-jasmine-node. No issues found so far after a few days of heavy use.

It would be helpful if the 2.0 branch could update the base Jasmine version (2.0.3 at present). I came across [this issue](https://github.com/pivotal/jasmine/issues/500) today, which was [fixed in v2.0.1](https://github.com/pivotal/jasmine/blob/master/release_notes/2.0.1.md).

Jasmine now supports a node runner natively, I'd suggest using this instead. http://jasmine.github.io/2.2/node.html

@aleclarson yes it is pretty sparse. Check out https://github.com/jasmine/jasmine-npm for a bit more info.

Sure, but wasn’t the point of moving to GitLab so that anything host-specific (issues, pull requests etc) are _not_ with GitHub? 🙂

Yes, I can see the offending line: https://github.com/isaacs/github-flavored-markdown/blob/master/scripts/showdown.js#L193 Perhaps it would be easier to submit a patch to the markdown parser project to only add the anchor tag if the...

> We actually ended up adding `nohoist: ['**']` to our react-native yarn workspace because it was easier than figuring out which needed to be where. I came to the same...

Yes, there is. Here's the repo: https://github.com/studiozeffa/threadsforslack-app

I can confirm that this is still an issue.

If you don't need any edges, can you use a `View` instead? ``` js const MyComponent = ({ needsSafeArea }) => { if (needsSafeArea) { return ( {/* My cool...