-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Yes, that's pretty much what I'm saying. The exception, however, is that it could possibly run its code after initialization. Just like the above theoretical example of how the React object was defined previously and then useId() was added to it after the JS lifecycle (via Promise.resolve().then(...)), one could imagine a uiLib object with uiLib.Button being injected after React v16 and v18-polyfills have run. Or better yet, React.useId = self.crypto.randomUUID so the React scope is now available even to the v16 code (even though it's unused). (Again, big assumption that this is how libs "polyfill" their code, which is not how React.useId is actually implemented.) Gist being that if a lib did this, then there wouldn't be any issues; likewise, splitting ui-lib out to its own repo/package means it has to (or at least is expected to) apply said polyfills since the parent consumer is expected not to transpile node_modules.
Great to see this being discussed, just wanting to mention that I wrote syncpack to address this problem, hopefully it's useful to some of you https://github.com/JamieMason/syncpack