Remove now unnecessary tweaking of global
Summary: public When we were debugging in the main window JS context in Chrome, the global environment had to be tweaked so that DOM features wouldn’t be detected. Since we switched to debugging within a web worker, we don’t need to do this tweaks any more. Reviewed By: bestander Differential Revision: D2850239 fb-gh-sync-id: 886f2f7ac5c579c3fd4a424d5341bc6bc0432c0d
This commit is contained in:
parent
4362e98170
commit
2902701566
|
@ -1,30 +0,0 @@
|
|||
/* eslint strict: 0 */
|
||||
|
||||
// TODO: Remove document polyfill now that chrome debugging is in a web worker.
|
||||
|
||||
// The browser defines Text and Image globals by default. If you forget to
|
||||
// require them, then the error message is very confusing.
|
||||
function getInvalidGlobalUseError(name) {
|
||||
return new Error(
|
||||
'You are trying to render the global ' + name + ' variable as a ' +
|
||||
'React element. You probably forgot to require ' + name + '.'
|
||||
);
|
||||
}
|
||||
global.Text = {
|
||||
get defaultProps() {
|
||||
throw getInvalidGlobalUseError('Text');
|
||||
}
|
||||
};
|
||||
global.Image = {
|
||||
get defaultProps() {
|
||||
throw getInvalidGlobalUseError('Image');
|
||||
}
|
||||
};
|
||||
// Force `ExecutionEnvironment.canUseDOM` to be false.
|
||||
if (global.document) {
|
||||
global.document.createElement = null;
|
||||
}
|
||||
|
||||
// There is no DOM so MutationObserver doesn't make sense. It is used
|
||||
// as feature detection in Bluebird Promise implementation
|
||||
global.MutationObserver = undefined;
|
|
@ -79,11 +79,6 @@ function getPackagerServer(args, config) {
|
|||
assetRoots: args.assetRoots,
|
||||
assetExts: ['png', 'jpg', 'jpeg', 'bmp', 'gif', 'webp'],
|
||||
resetCache: args.resetCache || args['reset-cache'],
|
||||
polyfillModuleNames: [
|
||||
require.resolve(
|
||||
'../../Libraries/JavaScriptAppEngine/polyfills/document.js'
|
||||
),
|
||||
],
|
||||
verbose: args.verbose,
|
||||
});
|
||||
}
|
||||
|
|
Loading…
Reference in New Issue