New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NativePromise.resolve not a function? #1192

Closed
jdelStrother opened this Issue Aug 9, 2016 · 3 comments

Comments

Projects
None yet
2 participants
@jdelStrother

jdelStrother commented Aug 9, 2016

  1. What version of bluebird is the issue happening on?
    3.3.5

  2. What platform and version? (For example Node.js 0.12 or Google Chrome 32)
    Linux Chrome 52 (allegedly)

  3. Did this issue happen with earlier version of bluebird?
    Unsure.

I have a number of error reports in my js reporter that claim to be coming from Linux Chrome 52, where requiring bluebird immediately throws an exception on calling NativePromise.resolve() (https://github.com/petkaantonov/bluebird/blob/master/src/schedule.js#L22). I can't reproduce this on my own version of Chrome 52 on Ubuntu, but wondered if anyone was aware of an environment where util.getNativePromise() would return a value, yet that value wouldn't have a resolve function.

@jdelStrother

This comment has been minimized.

Show comment
Hide comment
@jdelStrother

jdelStrother Aug 24, 2016

@petkaantonov awesome, thanks. Were you ever able to actually reproduce the problem?

jdelStrother commented Aug 24, 2016

@petkaantonov awesome, thanks. Were you ever able to actually reproduce the problem?

@petkaantonov

This comment has been minimized.

Show comment
Hide comment
@petkaantonov

petkaantonov Aug 24, 2016

Owner

no unless you mean doing something like delete Promise.resolve before loading bluebird

Owner

petkaantonov commented Aug 24, 2016

no unless you mean doing something like delete Promise.resolve before loading bluebird

@petkaantonov

This comment has been minimized.

Show comment
Hide comment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment