-
Notifications
You must be signed in to change notification settings - Fork 505
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
Inject react-dom in the shared scope #1320
Inject react-dom in the shared scope #1320
Conversation
Benchmark reportThe execution time (in milliseconds) are grouped by test file, test type and browser. Results table
❗ Test metadata have changed--- /dev/fd/63 2023-04-21 09:30:52.781476210 +0000
+++ /dev/fd/62 2023-04-21 09:30:52.781476210 +0000
@@ -4,51 +4,49 @@
"BENCHMARK_REFERENCE": "actual"
},
"browsers": {
- "chromium": "112.0.5615.29"
+ "chromium": "94.0.4595.0"
},
"systemInformation": {
"cpu": {
- "brand": "Xeon® Platinum 8171M",
+ "brand": "Xeon® E5-2673 v3",
"cache": {
"l1d": 65536,
"l1i": 65536,
- "l2": 2097152,
- "l3": 36700160
+ "l2": 524288,
+ "l3": 31457280
},
"cores": 2,
- "efficiencyCores": 0,
"family": "6",
- "flags": "fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology cpuid pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch invpcid_single pti fsgsbase bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx avx512f avx512dq rdseed adx smap clflushopt avx512cd avx512bw avx512vl xsaveopt xsavec xsaves md_clear",
+ "flags": "fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology cpuid pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm abm invpcid_single pti fsgsbase bmi1 avx2 smep bmi2 erms invpcid xsaveopt md_clear",
"governor": "",
- "manufacturer": "Intel",
- "model": "85",
- "performanceCores": 2,
+ "manufacturer": "Intel®",
+ "model": "63",
"physicalCores": 2,
"processors": 1,
"revision": "",
"socket": "",
- "speed": 2.6,
+ "speed": 2.4,
"speedMax": null,
"speedMin": null,
- "stepping": "4",
- "vendor": "Intel",
+ "stepping": "2",
+ "vendor": "GenuineIntel",
"virtualization": false,
"voltage": ""
},
"mem": {
- "total": 7281270784
+ "total": 7291699200
},
"osInfo": {
"arch": "x64",
"build": "",
- "codename": "Jammy Jellyfish",
+ "codename": "Focal Fossa",
"codepage": "UTF-8",
"distro": "Ubuntu",
- "kernel": "5.15.0-1035-azure",
+ "kernel": "5.8.0-1040-azure",
"logofile": "ubuntu",
"platform": "linux",
- "release": "22.04.2 LTS",
- "serial": "a6219d4d787c4becbd42a2cf1ee91d94",
+ "release": "20.04.3 LTS",
+ "serial": "cfc067bfcb844f35865e279a1b0e66c5",
"servicepack": "",
"uefi": false
} |
Thanks @martinRenou |
Why is this needed? What was the issue with ipyflex? |
That's due to the whole "shared package" logic in the webpack federated thingy https://github.com/trungleduc/ipyflex/blob/master/package.json#L99. I think react needs to be specified as shared, we don't want all packages to provide their own react in the page, do we? |
Multiple react version on the same page is no problem at all. And react is quite small:
The problem actually occurs when you get a wrong version of react and react-dom. Maybe a better strategy is |
References
Similar to voila-dashboards/voici#67
This fixes support for ipyflex