debug notice in When running in Meteor Production mode

[sahanDissanayake]

if you open https://kadira.io/ and see the console there is a console.debug
this should not appear on production mode

[arunoda]

console.debug is something inside the browser. I don't think it's related to React in anyway.

[sahanDissanayake]

Well it is,

"production" !== n.env.NODE_ENV) {
                    var w = e("./ExecutionEnvironment");
                    if (w.canUseDOM && window.top === window.self) {
                        navigator.userAgent.indexOf("Chrome") > -1 && "undefined" == typeof __REACT_DEVTOOLS_GLOBAL_HOOK__ && console.debug("Download the React DevTools for a better development experience: https://fb.me/react-devtools");
                        for (var O = [Array.isArray, Array.prototype.every, Array.prototype.forEach, Array.prototype.indexOf, Array.prototype.map, Date.now, Function.prototype.bind, Object.keys, String.prototype.split, String.prototype.trim, Object.create, Object.freeze], T = 0; T < O.length; T++)
                            if (!O[T]) {
                                console.error("One or more ES5 shim/shams expected by React are not available: https://fb.me/react-warning-polyfills");
                                break
                            }
                    }
                }

this is because react does not know the `NODE_ENV`` that's its on..

[sahanDissanayake]

https://kadira.io/b1feef36dbe9e5bc6b138dcbb8b15f488384b67c.js?meteor_js_resource=true

line 51223

[arunoda]

Okay.This is not related to console.debug. Something like react being added with dev mode. I assume this is something with the browserify setup.

I'll check.

[sahanDissanayake]

👍

[sahanDissanayake]

this is now fixed with the new react runtime update to 0.14.4

[sahanDissanayake]

now getting this error
https://forums.meteor.com/t/mupx-archiving-failed-enoent/15281

[markshust]

This may be to the fact that I was running react-runtime 0.14.3, but react-layout was requiring 0.14.4. Pushing up this fix.