scriby

The native implementation of Promise.prototype.finally in Chrome doesn't work quite right with this polyfill. When doing something like `Promise.reject('test').finally(() => {})` the polyfill will not emit an unhandledrejection.

``` test(`does not trigger event for recovered downstream 2 (${name})`, t => { t.plan(1); let count = 0; const reason = 'rejection'; const listener = (e) => { count++; }...

Add some example apps

2

Show an example Express application using asyncblock

It's nice that the library automatically looks up the DOM for the first scrollable parent, but I have a bit of a corner case where the automatic detection doesn't work....

URL path camelCase vs underscore vs dash etc.

9

It would be great if the standards document expressed a clear opinion on how multiple words should be concatenated in URL path segments. For example: https://api.contoso.com/v1.0/pullRequests https://api.contoso.com/v1.0/pull-requests https://api.contoso.com/v1.0/pull_requests https://api.contoso.com/v1.0/pullrequests

Included icons does not affect font file hash

7

It appears that the hash of the font file is taken prior to fontmin running, so it only depends on the original source file. This means that the font file...

jasmineNodeOpts

5

I see support for cucumberOpts and mochaOpts... but no jasmine options. Am I missing something or is that a miss?

Fix a bug with setting a field on an empty object under the now namespace Something like this: ``` javascript everyone.now.obj = {}; everyone.now.obj.x = 'test'; //error ```