setImmediate() is a non-standard function #11
Comments
Eh, I figured that thing would be a thing by now (and I thought it was seeing how nodejs has it which I thought meant chrome did as well), but it looks like Chrome and Firefox don't like it for various "reasons" (very longs issue threads...). It is a standard, just an unofficial one which looks like will it never make it pass the editor's draft phase. That being said, I'm going to make it so |
I am using react, but I don't use the polyfill, I guess this is why I got that error. :) |
I am not 100% sure how you are not using the polyfill since it is included with react via react's dependencies. Maybe treeshaking is removing it? |
I've been looking into React's code, and React doc website https://facebook.github.io/react/docs/hello-world.html, and I think React doesn't include
So, you can find setImmediate in the global scope? ...mmm ... weird :) |
I have never used react with UMD imports and script tags like that, it appears they have a special build which limits the things they import from fbjs probably to help minimize the size. https://github.com/facebook/react/blob/2fa38ac1cce658ce799a162e65fcf782187c8802/scripts/rollup/modules.js#L188-L196 |
Yes ... :) I am still using so, if we cannot guarantee |
Hi...got an Reference Error today, and found this is because setImmedaite() got called in componentWillReceiveProps(). can you fix it, I really like react-block-ui :)
The text was updated successfully, but these errors were encountered: