|
@@ -1,6 +1,16 @@
|
1
|
|
-// FIXME: remove once react-native-webrtc and react-native-prompt imports
|
2
|
|
-// PropTypes from the 'prop-types' lib instead of 'react'.
|
3
|
|
-import './features/base/react/prop-types-polyfill.js';
|
|
1
|
+// FIXME The bundler-related (and the browser-related) polyfills were born at
|
|
2
|
+// the very early days of prototyping the execution of lib-jitsi-meet on
|
|
3
|
+// react-native. Today, the feature base/lib-jitsi-meet should not be
|
|
4
|
+// responsible for such polyfills because it is not the only feature relying on
|
|
5
|
+// them. Additionally, the polyfills are usually necessary earlier than the
|
|
6
|
+// execution of base/lib-jitsi-meet (which is understandable given that the
|
|
7
|
+// polyfills are globals). The remaining problem to be solved here is where to
|
|
8
|
+// collect the polyfills' files.
|
|
9
|
+import './features/base/lib-jitsi-meet/native/polyfills-bundler';
|
|
10
|
+
|
|
11
|
+// FIXME: Remove once react-native-webrtc and react-native-prompt import
|
|
12
|
+// PropTypes from 'prop-types' instead of 'react'.
|
|
13
|
+import './features/base/react/prop-types-polyfill';
|
4
|
14
|
|
5
|
15
|
import PropTypes from 'prop-types';
|
6
|
16
|
import React, { Component } from 'react';
|