-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Does not work in SystemJS and nodewebkit from 2.9.15 onwards #624
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
Comments
Nevermind, verified failure on 2.9.25 |
This does not reproduce when doing This is the scheduler, setting Update: this is because nw has a separate We can work around this by binding setImmedaite or adding a check for |
Wonderful, glad my ticket was thorough enough! Will use your workaround in the meantime. |
@NervosaX thanks for the detailed issue - can you please verify it worked for you? |
@benjamingr
Which is here:
It is complaining that global.setImmediate does not exist. There is global.setTimeout. I would say this is an incompatability with node webkit now. |
Could possible be related to #525 Version 2.9.25 and your fix above works, but 2.9.26 fails with the above issue. |
@benjamingr pls fix |
I'll look into it tomorrow, I think we can just explicitly detect node webkit and use |
@NervosaX does it work for you in 2.9.27? I added capability to run tests in nw and they pass. It also changed scheduler to be used in nw to MutationObserver since it's faster than setImmediate and not as buggy as nextTick. |
@petkaantonov Seems to be working as normal in 2.9.27, both in browser and through nw. Thanks heaps for the fix. |
Since upgrading from 2.9.14 to 2.9.15, bluebird throws an invalid invocation error when performing Promise.all() (possibly others, Promise.resolve() works fine). This is only an error when run through System JS and nwjs (nodewebkit). 2.9.15 seems to be when it adds the browser version of bluebird.
Loading it through nodewebkit with a direct CDN link seemed to work fine.
See this for reproduction steps: https://github.com/NervosaX/bluebird-nw-bug
The stack trace is:
The text was updated successfully, but these errors were encountered: