Igor Savin

Update dependencies (vitest 4 and friends)

1

Blocked for now, as WebStorm still doesn't support vitest 4 properly.

Switch to a beta version of drizzle

1

Checking the migration part for 1.0.0

Get rid of fn.call and fn.apply usage

1

Ideally get away with it altogether, worst-case scenario - use Proxy or Reflect.apply (both are faster)

Refactor tests

1

1. We should consider retiring chai.should() in favor of expect(..). (Why? Because chai.should() monkey-patches various Javascript objects, which can occasionally lead to some surprising results); 2. Se should consider eliminating...

Add diagnostics_channel hooks

1

Consider using https://github.com/simon-id/diagnostics_channel-polyfill#readme polyfill for older Node versions.

Implement job heartbeat

7

fixes #436 fixes #579

Concurrency management

5

Readme mentions "Queue storage policies to support a variety of rate limiting, debouncing, and concurrency use cases", but I couldn't find any details on supported concurrency management options in the...

More modern testing framework?..

5

Mocha is pretty clunky to work with, and current setup doesn't work well with IDEs. Have you considered switching to something more modern, like vitest or node:test?

### Is your feature request related to a problem? Please describe It is frequently desireable to skip certain endpoints from instrumentation (e. g. metrics and healthchecks). It is not currently...