taylorhakes/promise-polyfill

Issues

• Auto polyfill

  #46 opened 7 years ago
  2

• use with import

  #44 opened 8 years ago
  3

• How about publishing to CDNjs / jsDelivr

  #43 opened 8 years ago
  4

• is there a way to use this with plain angular project?

  #42 opened 8 years ago
  2

• how to use?

  #41 opened 8 years ago
  2

• Recommended deployment approach - override browser support or not?

  #40 opened 8 years ago
  2

• console.log does not print in promise.then in browser

  #39 opened 8 years ago
  1

• Strange additional import with webpack

  #38 opened 8 years ago
  2

• Polyfill Context

  #37 opened 8 years ago
  4

• Minified code IE8 error

  #34 opened 8 years ago
  3

• Is there a issue by promise-chaining?

  #32 opened 8 years ago
  4

• IE11: SCRIPT65535: Ungültiges aufrufendes Objekt.

  #31 opened 8 years ago
  2

• Something I don't understand about your code

  #30 opened 8 years ago
  3

• Use process.nextTick where available

  #28 opened 9 years ago
  6

• console is undefined

  #25 opened 9 years ago
  2

• Subclassing

  #24 opened 9 years ago
  7

• SCRIPT438: Object doesn't support property or method '_setImmedateFn'

  #22 opened 9 years ago
  3

• package.json main field and file name do not match

  #20 opened 9 years ago
  3

• Unable to register a global handler for all unhandled rejected promises

  #19 opened 9 years ago
  2

• resolve() with a promise as argument has issue

  #18 opened 9 years ago
  3

• ES6 Promise compatible

  #14 opened 9 years ago
  1

• prototype methods

  #13 opened 9 years ago
  2

• Shimming setImmediate via Promise.immediateFn won't work in non-CommonJS environments

  #12 opened 9 years ago
  3

• Different behavior between Chrome/Firefox implementation and polyfill

  #11 opened 9 years ago
  10

• Browser Compatibility

  #9 opened 10 years ago
  1

• global is not defined

  #8 opened 10 years ago
  5

• Where is unit test?

  #5 opened 10 years ago
  2

• Issue with browserify

  #4 opened 10 years ago
  7

• Promise.resolve does not behave according to newest spec

  #3 opened 10 years ago
  0