naugtur/blocked-at

Issues

• hey, you. Post stacktrace examples

  #5 opened 7 years ago by naugtur
  28

• License value in package.json doesn't match LICENSE

  #37 opened 7 months ago by FElliger
  1

• blocked-at is unusable on express web servers - spikes CPU to 100%

  #36 opened 10 months ago by powersjcb
  6

• Use in Express middleware

  #35 opened 2 years ago by FeelHippo
  0

• asyncHooksRegEx doesn't match the correct traces

  #34 opened 2 years ago by hmeerlo
  1

• Import triggers false positive

  #31 opened 4 years ago by LJNeon
  2

• getting OOM errors since using this

  #7 opened 7 years ago by yocontra
  6

• Doesn't report garbage collector

  #26 opened 5 years ago by logidelic
  2

• Additional load caused by library

  #22 opened 5 years ago by riston
  4

• Reports fs.exists() to be blocking with Node V8.x

  #17 opened 7 years ago by gjegadesh
  2

• Stack trace is always undefined

  #19 opened 6 years ago by jeetkr
  0

• async hooks deprecated :(

  #12 opened 7 years ago by yocontra
  3

• Version 10 of node.js has been released

  #14 opened 7 years ago by greenkeeper
  0

• failing test: Expected test/index.js:17 in stack trace

  #10 opened 7 years ago by andrewsensus
  2

• Look for potential false-positives

  #1 opened 7 years ago by naugtur
  5

• Hangs application after first block

  #6 opened 7 years ago by cryptiklemur
  2

• TypeError: Cannot read property 'includes' of undefined

  #3 opened 7 years ago by anik3tra0
  5

• TypeError: Cannot set property 't0' of undefined

  #2 opened 7 years ago by amanthegreatone
  9