backburner.js icon indicating copy to clipboard operation
backburner.js copied to clipboard

A rewrite of the Ember.js run loop as a generic microlibrary

Results 36 backburner.js issues
Sort by recently updated
recently updated
newest added

I think they have been deprecated enough to remove them, and since they are not used in ember for long time

Kicking off the idea/convo of including an API within Backburner for optimally batching work within a rAF scheduler for reads/writes. Addons obviously exist to leverage this, however it's so fundamental...

enhancement

Hang tight on review of this PR. Im going to squash the declarations files and expose a `index.d.ts`. Spiking this now. TBH there more than likely is an easier way...

I'm wondering how fast if can be, using https://github.com/AssemblyScript/assemblyscript

This PR introduces async stack traces to Backburner so it's easier to debug the runloop by allowing the developer to step back through the asynchronous stack frame. Before / After...

I _believe_ we should be able to use ember-cli-browserstack (Ember recently did the same migration). We need to test in: * Edge * IE11 * Safari * FireFox * Chrome

https://github.com/BackburnerJS/backburner.js/blob/master/lib/backburner/queue.ts#L139-L180 rather then doing [splicing](https://github.com/BackburnerJS/backburner.js/blob/master/lib/backburner/queue.ts#L156) lets just [null out always](https://github.com/BackburnerJS/backburner.js/blob/master/lib/backburner/queue.ts#L177) @bekzod thoughts?

Previously, cancelling a job would `splice` it from the queue. This was problematic because it affects the index of all later jobs in the queue. The `targetQueues` map of jobs...

https://developer.chrome.com/blog/devtools-modern-web-debugging/#linked-stack-traces This enables the Chrome developer tools to link the stack traces of the original event scheduling and the eventual execution on the runloop. This is available in Chrome 106...